SP Loot Manager: Custom Mob Drops for Minecraft

SP Loot Manager gives you full control over mob and animal death drops for Minecraft, with a server-authoritative editor and one global config.!

SP Loot Manager

Every survival world eventually runs into the same problem: the loot table says one thing, and your design for the world says another. Maybe cows should drop emeralds on rare occasions. Maybe zombies should stop dropping iron ingots entirely. Maybe you want a specific boss to always leave behind a custom reward. SP Loot Manager is a Fabric mod for Minecraft that turns those ideas into a clean, server-authoritative GUI, letting you configure monster and animal death drops by entity type without writing a single line of JSON by hand.

What SP Loot Manager Does

The mod adds a standalone editor for death loot. You search for an entity ID, open its settings, and decide exactly what happens when that mob dies. The catalog includes registered mob entities: monsters, passive animals, water mobs, and golems. Modded mobs and items appear too, as long as they are registered on the server. The interface borrows the dark panels, gold borders, and paginated lists of the SP Shop family, but SP Shop and SP Coins are not required. This is a self-contained tool.

Open the editor with /lootedit or /sploot. You will need gamemaster command permission, which usually means OP level 2 on a dedicated server or enabled cheats in singleplayer.

How to Install SP Loot Manager for Minecraft

If you are wondering how to install the mod, the process is familiar to anyone who has set up Fabric mods before. SP Loot Manager is built for Fabric and supports modern Minecraft releases; check the mod page for the exact version list before you download SP Loot Manager, since the build must match your game version and Fabric loader.

  • Install the Fabric loader for your Minecraft version.
  • Place the Fabric API and the SP Loot Manager JAR in your mods folder.
  • Launch the game once so the config directory is generated.
  • Join a world, grant yourself permission, and run /lootedit.

If you would rather skip the manual file shuffling, the foxygame.net launcher handles the setup for you: its add-on catalog includes SP Loot Manager, and the launcher keeps it updated and matched to your installed Minecraft version automatically.

Editing Vanilla Drops

The real power lives in the vanilla item editor. Toggle Vanilla drops ON to keep normal death loot and layer your custom rows on top, or OFF to suppress the normal loot table, special death loot, and dropped equipment for that entity type. From there, Edit vanilla items shows every item pulled from the loaded loot tables.

Keep Chance and Quantity Overrides

Select an item and you can remove it, lower its Keep chance percentage, or replace the vanilla quantity with your own minimum and maximum range. Keep chance is a multiplier on Minecraft's successful drops: 100% preserves the original chance, 50% keeps half the successful cases, and 0% suppresses the item entirely. A vanilla 20% drop with Keep chance at 50% becomes roughly 10% overall. Minecraft's own conditions still run first, so the editor never pretends a complex loot table has one unconditional percentage. The keep decision rolls once per item ID per death, even when several stacks are emitted, and item components such as names and enchantments are retained from the first matching vanilla stack.

Custom Rows and Other Items

Use Add item for an independent custom row: enter a registered item ID or pick one with Choose item, then set minimum quantity, maximum quantity, and drop chance. Chances can be fractional, so 37.5% is perfectly valid, and each row rolls independently once per death. Quantities are chosen uniformly from the inclusive range, and oversized results split into legal stacks. Duplicate rows are allowed. The Other item button covers equipment, special drops, and transformed items that do not appear automatically.

One Global Configuration

Settings live in config/sp-loot-manager.json inside the game or server installation directory. That single file applies to every existing and future world and every dimension on that installation, surviving restarts and world changes. On multiplayer, the server's configuration is authoritative; client-side settings never override it. Upgrading from 1.0.x is handled automatically: the first opened world's legacy file is validated, upgraded, and copied into the global location while the original is preserved.

Saving, Limits, and Recovery

Nothing activates until you click Save global. The server validates the complete draft, writes it through a temporary file with an atomic replacement, and keeps the previous configuration as a backup. Stale saves are rejected, invalid IDs and nonfinite chances are refused, and a corrupt global file simply disables the mod's overrides rather than silently falling back to another world's settings. Limits are generous but firm: 512 entity rules, 64 custom rows and 64 vanilla-item overrides per entity, quantities from 0 to 4096, chances from 0 to 100%, and a 240 KB configuration cap.

Final Thoughts

SP Loot Manager fills a gap that vanilla datapacks handle clumsily: fast, visual, per-entity control over what mobs leave behind. Whether you are tuning a survival economy or building a custom adventure map, the combination of keep-chance multipliers, quantity overrides, and independent custom rows gives you precise authority over every death. Download SP Loot Manager, open the editor, and make your world's loot behave the way you always wanted.