Full On Randomizer

Full On Randomizer

Randomize block drops, entity drops, crafting, and smelting with one persistent, server-authoritative seed.

Full On Randomizer turns ordinary Minecraft progression into controlled chaos. Four gameplay systems can be randomized independently, while all of them use the same persistent global seed and the same underlying randomizer architecture.

You can enable everything for complete chaos, or enable only the systems you want.

Core Systems

🧱 Block Drops

Breaking eligible blocks can produce a randomized item instead of the normal drop.

• Mappings are persistent and deterministic.
• The same block continues producing the same randomized output until the mappings are changed.
• Vanilla and modded blocks are supported.
• Silk Touch is respected: with Silk Touch, the original block is returned normally instead of using the randomized drop.
• Explosion-based block destruction is supported where the game exposes the appropriate drop path.
• Entity-caused block destruction is also handled where supported.

💀 Entity / Mob Drops

Living entity drops can be replaced with randomized item drops.

• Entity eligibility is discovered dynamically from the game's registry rather than using a hardcoded mob list.
• Vanilla and modded living entities are supported.
• Players are excluded.
• Original drop quantities are preserved.
• Experience is not randomized or removed.
• Each entity type keeps one persistent mapping until the mappings are changed.
• Modded entities can participate automatically when they are registered normally.

🛠️ Crafting

Crafting recipe outputs can be randomized.

Supported systems include:

• 2×2 crafting
• 3×3 crafting
• Shaped recipes
• Shapeless recipes
• Vanilla recipes
• Modded recipes
• Manual crafting
• Shift-click crafting
• Recipe-book crafting

The randomized result remains stable until the mappings are shuffled, reshuffled, or otherwise reset.

🔥 Smelting / Furnaces

Smelting outputs can also be randomized.

Supported blocks include:

• Furnace
• Blast Furnace
• Smoker

The system is designed to work with normal furnace operation as well as automated setups such as hoppers, while preserving normal input, fuel, cooking, stacking, output-capacity, and experience behavior.

One Global Seed. Persistent Mappings.

Full On Randomizer uses one global seed shared by all four systems.

The seed and generated mappings are stored in the world's save data, so they persist through:

• leaving and reopening the world
• Minecraft restarts
• server restarts
• world reloads

Mappings do not randomly change every time a block is broken, an entity dies, a recipe is used, or an item is smelted.

A mapping stays stable until you deliberately change the randomizer state through the available commands or Dashboard controls.

Admin Dashboard

Press Left Alt by default to open the Full On Randomizer Dashboard.

The key can be changed through:
Options → Controls → Key Binds → Miscellaneous

The Dashboard provides:

Main Dashboard — View:

• Current global seed
• Overall randomizer status
• Block Drops status and mapping count
• Entity Drops status and mapping count
• Crafting status and mapping count
• Smelting status and mapping count

Independent System Toggles

Block Drops, Entity Drops, Crafting, and Smelting can each be enabled or disabled independently.

You can therefore run combinations such as:

• Blocks only
• Crafting + Smelting
• Entities + Blocks
• All four systems
• Or leave selected systems disabled

Global Controls

The Dashboard provides controls corresponding to the main randomizer commands, including:
Enable, Disable, Enable All, Disable All, Shuffle, Shuffle All, Shuffle Blocks, Reshuffle, Seed, Reset.

Actions that change mappings or other important randomizer state use confirmation screens.

Mapping Inspector

The Mapping Inspector lets you inspect the current randomized result for a specific block, entity, crafting recipe, or smelting recipe.

The Inspector is read-only. Simply inspecting a mapping does not:

• create a missing mapping
• repair a mapping
• shuffle anything
• change the seed
• modify the world
• change SavedData

Important: Use Registry IDs

The Inspector expects the object's registry ID, not its displayed name.

Registry IDs use this format: namespace:id

Vanilla example — for the vanilla diamond item, use: minecraft:diamond

Modded example — use that mod's own namespace, e.g. pointblank:gunmetal

Do not enter minecraft:gunmetal, and do not enter only Gunmetal.

The same namespace:id format applies to blocks, entities, recipes, and other registry-based entries.

Forward Lookup

You can inspect:

• Block → randomized item
• Entity → randomized item
• Crafting recipe → randomized result
• Smelting recipe → randomized result

Use the actual registry ID for the object you want to inspect.

Reverse Lookup — "What Produces This?"

Search for an item and see which current mappings produce it. For example, minecraft:diamond can show blocks, entities, crafting recipes, and smelting recipes that currently map to diamond. For a modded item, use its real registry ID, such as pointblank:gunmetal.

This is especially useful when you want to answer questions like "What can currently give me diamonds?" or "What currently produces this modded item?"

Reverse lookup is also read-only and does not generate or modify mappings.

Commands

/randomizer status

/randomizer enable
/randomizer disable

/randomizer shuffle
/randomizer shuffle all
/randomizer shuffle blocks
/randomizer reshuffle

/randomizer seed
/randomizer seed <number>

/randomizer reset
/randomizer blocks

/randomizer debug block <block_id>
/randomizer debug item <item_id>
/randomizer debug entity <entity_id>
/randomizer debug recipe <recipe_id>
/randomizer debug smelting <recipe_id>

/randomizer debug item-source <item_id>
/randomizer debug item-recipe <item_id>
/randomizer debug item-smelting <item_id>

/randomizer status is public and read-only. Everything else requires server-operator permission. IDs use the same namespace:id format described above.

Server Security

Administrative controls are validated on the server. Access is based on server operator permission, not game mode.

• Survival operators can use the Dashboard and commands.
• Creative operators can use them.
• Adventure operators can use them.
• Spectator operators can use them.
• Non-operators cannot bypass the restriction by changing game mode.

/randomizer status remains available to everyone because it is read-only. The same permission model applies to Dashboard actions.

Vanilla + Modded Compatibility

Full On Randomizer dynamically works with the game's registries instead of relying on a fixed hardcoded list. This allows it to work with vanilla and modded blocks, entities, items, and recipes alike.

Registry-based systems also allow the mod to adapt to different modpacks without requiring a separate hardcoded configuration for every mod.

Invalid, unavailable, or removed IDs are handled safely rather than being allowed to crash the game.

Important Note About Recipe Viewers

Mods such as JEI and other recipe-viewing tools read the game's recipe data directly. Because Full On Randomizer changes the result you actually receive at runtime, a recipe viewer may still display the original recipe result while Full On Randomizer gives you the currently randomized result.

For the actual randomized result, use the Mapping Inspector.

Requirements

• Minecraft Java Edition 1.21.11
• NeoForge 21.11.45
• Java 21

Current Status

Alpha — v0.4.0-alpha

All four core randomization systems and the Admin Dashboard are implemented and functional.

Full On Randomizer is designed for players who want deterministic randomization rather than completely unpredictable rerolls: once a mapping exists, it stays consistent until you intentionally change the randomizer state.

Bug reports, compatibility reports, and feedback are welcome.