SP Loot Manager

Open /lootedit or /sploot. The editor requires Minecraft's gamemaster command permission (normally OP level 2 on a dedicated server, or enabled cheats in singleplayer).

1. Search for an entity ID and open its settings. The catalog includes registered Mob entities, including monsters, passive animals, water mobs, and golems. Modded mobs and items are included when registered on the server.
2. Toggle Vanilla drops: ON/OFF. ON adds your custom rows to normal death loot; OFF suppresses the normal death loot table, special death loot, and dropped equipment for that entity type.
3. Use Edit vanilla items to view items from the loaded loot tables. Select an item to remove it, reduce its Keep chance %, or switch from Vanilla quantity to your own min/max range. Restore vanilla removes that item's override. Other item... lets you select equipment, special drops, or transformed items that are not listed automatically.
4. Use Add item for an independent custom row. Enter a registered item ID or select one with Choose item, then set Min quantity, Max quantity, and Drop chance %. Open an existing custom row to edit or remove it.
5. Click Apply to update the draft, return to the main screen, then click Save global. The server validates and persists the complete draft before activating it. A success message confirms the global save.

Reset entity removes its rule and restores normal Minecraft behavior. Reload asks before discarding the draft and fetching the current server settings. Closing a changed draft also asks for confirmation. Changes in forms remain local until Save global succeeds.

Keep chance is a multiplier on Minecraft's successful drops. 100% preserves the original chance; 50% keeps half the successful cases; 0% or Remove drop suppresses that item. For example, a vanilla 20% drop with Keep chance 50% becomes approximately 10% overall. Minecraft's conditions still run first: the editor does not pretend that complex loot tables have one unconditional percentage.

The keep decision is rolled once per item ID per death, even when Minecraft emits several stacks. Vanilla quantity retains the rolled amounts. Custom range replaces the total quantity of that item for that death, only if vanilla actually produced it. Looting and other vanilla conditions still affect whether the original drop occurs; the replacement quantity uses your configured range. Item components such as names and enchantments are retained from the first matching vanilla stack. The result splits into legal stack sizes.

For an absolute per-death chance, remove the vanilla item and add a custom row for the same ID. Custom rows are independent of vanilla-item filters.

The catalog follows nested loot tables and item tags and lists common cooked variants separately. It refreshes after successful datapack reloads; reopen or Reload the editor to see the new catalog. Code-generated equipment, special drops, and arbitrary modded transformations may need Other item.... Filters match the final item ID: raw beef and cooked beef are separate settings. They also apply to equipment emitted through the normal death-drop path.

Each custom row rolls independently once per death. The chance can be fractional (for example, 37.5); 0% never drops and 100% always rolls successfully. Quantity is uniformly selected from the inclusive min/max range. A result of zero creates no item. Quantities larger than the item's stack size split into legal stacks. Duplicate custom rows are allowed and roll independently.

• Permissions are checked on every request, including after OP is revoked.
• Editing sessions carry a token and revision. A stale save is rejected and retains the draft; use Reload to review the current server settings before editing again.
• Invalid item/entity IDs, air items, nonfinite chances, invalid ranges, and excessive configuration sizes are rejected.
• Limits: 512 entity rules, 64 custom rows and 64 vanilla-item overrides per entity, 0–4096 quantity, 0–100% chance, 240 KB configuration. Compressed network packets also have strict size limits.
• Saves use a temporary file and an atomic replacement; the previous configuration becomes sp-loot-manager.json.bak. A failed save does not activate the draft.
• A corrupt, unsupported, or unloadable global configuration disables this mod's drop overrides for the running server and preserves the original file; it never silently falls back to a different world's settings. Vanilla drops continue; inspect the server log, fix or restore the backup while the server is stopped, then restart. Invalid legacy data is also preserved and does not create a new global file.
• Manual file edits are loaded on server startup. GUI Reload fetches the live server configuration; it does not reread a manually edited file.