Come chat with us and we will get back to you as soon as possible!
Contact SupportHolyHosting
Holy Team

Progression in Minecraft usually depends on tracking down the right materials in the right places. Diamonds come from deep underground, ancient debris waits in the Nether, and early survival often starts with the familiar tree punching ritual. Randomizer changes that entire routine by making breakable blocks drop shuffled items instead.
The Randomizer plugin is a Spigot addon that gives every block a random drop after the loot table is shuffled. Grass might hand over diamonds, dirt might produce bedrock, and flowers might become the most valuable thing in your world for five minutes. It is chaotic, but in the useful party-game sense rather than the server-is-on-fire sense.
Server owners can reshuffle drops whenever they want, creating a fresh challenge for friends or an event world. This guide explains how to download, install, use, and configure Randomizer on a Minecraft server.

Randomizer must be installed on a server type that supports plugins, such as Spigot or Paper. Once you have the .jar file, upload it to the plugins folder through your server file manager or FTP access.



After the restart, the server should create the Randomizer plugin folder and its configuration files.

Join the server, enter your world, and run /randomizer shuffle in chat. This command creates a new set of randomized drops. If the command does not work, confirm that your account has operator permissions.
Once the shuffle is active, break blocks to test the results. Plains biomes are great for the first check because they have grass, dirt, flowers, and other quick blocks to sample. Every breakable block can drop a random item, so results can range from basic survival supplies to materials that normally cannot appear in survival mode.
If the first shuffle leaves everyone stuck with useless drops, run /randomizer shuffle again. A bad starting roll can make wood, food, or tools hard to find, and nobody wants an entire civilization built on three poppies and regret.
Randomizer can occasionally drop items that survival players normally cannot obtain. Some are mostly harmless, while others can cause balance or moderation problems.

Examples include structure blocks, barriers, spawn eggs, and other special materials. A structure block is mainly useful in creative workflows, while barriers are invisible blocks that can easily become annoying in the wrong hands. Wither spawn eggs are a more obvious problem if players are allowed to keep and use them.
You can edit the plugin configuration to remove specific drops from the pool. Keep in mind that running /randomizer shuffle afterward may overwrite or re-enable parts of the setup, so check the config again after major changes.
Early Randomizer gameplay can feel strange because the first few drops may not help at all. The best approach is to gather blocks that are easy to break, then place and break them repeatedly to move through more drop results.
Good starter blocks include:
This gives players more chances to uncover food, tools, wood, ores, or other progression items. The strategy stays useful later too, especially when a specific block starts dropping something valuable.

Randomizer commands are mainly used to shuffle item drops, toggle the plugin, and check whether random drops are active. These commands require operator access by default.
For public servers, it is better to assign permissions through a permission plugin such as LuckPerms instead of giving every staff member full operator access. That keeps command access controlled while still allowing moderators or event managers to reshuffle drops when needed.
The configuration file lets you set or restrict drops more permanently than a quick in-game shuffle. This is helpful when you want to block specific materials, such as bedrock, barriers, or dangerous spawn eggs.



Be careful with /randomizer shuffle after editing the file. The command can replace the current drop setup, so use it only when you actually want a new randomized pool.
Run /randomizer shuffle at least once after installing the plugin. Randomizer needs a generated shuffle before blocks start dropping randomized items. After the command runs, break several different blocks to confirm the results.
If nothing changes, verify that the plugin loaded during startup. Check the plugins folder for the Randomizer .jar file, then restart the server again.
Randomizer requires a plugin-compatible server type, such as Spigot or Paper. It will not work on a vanilla server jar. Also confirm that your Minecraft version is supported by the plugin, commonly listed as 1.13.2 through 1.19 and newer depending on the plugin release.
If server profiles are enabled, make sure the file was uploaded to the plugins folder for the correct profile. Uploading to the wrong profile is a classic way to install a plugin perfectly and still have nothing happen.
If your blocked items return after using /randomizer shuffle, the shuffle command likely regenerated the drop setup. Reapply your config edits, save the file, restart the server, and avoid reshuffling unless you are ready to update the restrictions again.
Come chat with us and we will get back to you as soon as possible!
Contact SupportMake every block, mob, and tool in Minecraft look like Lego pieces. This guide walks through downloading, installing, and running Brickcraft on both client and server.
Learn how to install Litematica for Minecraft, load schematic files, position blueprints, and use the material list for survival builds.
Set up Valhelsia Enhanced Vanilla for Minecraft, install the client profile, configure your server, and learn the early skills, items, and fixes that help the pack run smoothly.