MAKER · JAVA

Custom slime loot, no coding

Describe the loot ("make slimes drop diamonds") and the engine writes a real entity loot table that replaces the vanilla slime drops — a normal Java datapack you drop into any world. No mods, no coding, and it can't generate a broken file: every item id is validated before it's written.

WHAT YOU ACTUALLY GET — REAL OUTPUT FOR “MAKE SLIMES DROP DIAMONDS

Slimes Diamonds · Java datapack · 4 files

It does this: killing slimes now drops diamond.

README.txt
data/minecraft/loot_table/entities/slime.json
pack.mcmeta
… 1 more

Start it: /reload

How it works

  1. 1Describe it: "make slimes drop iron ingots" — you can list several items in one sentence.
  2. 2Download the datapack zip and drop it into your world's datapacks folder.
  3. 3Run /reload — from then on every slime you kill uses your loot table.

Questions people ask

Does this replace the normal slime drops?

Yes — the datapack overrides the vanilla loot table at data/minecraft/loot_table/entities/slime.json, so your items replace the default drops. Remove the datapack to get vanilla behavior back.

Which versions does it support?

You pick the target Minecraft version and the pack is generated with the right pack_format. The version list updates itself when Mojang ships a new release.

Does it work on servers?

Yes — drop the same zip into the server world's datapacks folder and /reload. It's a plain datapack, so Paper, Spigot, Purpur and vanilla all load it.

Why it never breaks

No language model writes these files. Deterministic engines parse your description into validated parameters and emit game files that are correct by construction — then CI boots real Paper and Bedrock servers weekly to prove packs still load on current Minecraft. Read the full story on the comparison page or in the docs.