CurseForge · Minecraft mod
FreshLoot
Is a player not entitled to his loot? Now, every player gets his own loot when opening a chest. Destroying a chest to prevent others from looting it is shameful.
Quick answer
Which FreshLoot release should I use?
freshloot-2.0.0+26.3-forge.jar targets 1.21.4 with Forge. The project page does not say whether this file belongs on the client, dedicated server, or both. No extra mods listed for this file.
Where it goes
Is FreshLoot required on the client, server, or both?
The project page does not say whether this file belongs on the client, dedicated server, or both.
The source does not explicitly classify this release as client-only or server-only.
What else does freshloot-2.0.0+26.3-forge.jar need?
freshloot-2.0.0+26.3-forge.jar. Change the file and its required mods may change too.
This file does not list any required mods. Do not add a library just because a different file uses it.
This file does not list any required or optional mods.
Before you install it
Add FreshLoot without breaking your instance.
Built for freshloot-2.0.0+26.3-forge.jar. Pick another file and the loader, install side or required mods may change.
- 01
Stick to this file
Use freshloot-2.0.0+26.3-forge.jar. It targets 1.21.4 with Forge; another release may have different loader, side or dependency requirements.
- 02
Bring the mods it needs
This file does not list any required mods. Do not add a library just because a different file uses it.
- 03
Put it on the correct side
The project page does not say whether this file belongs on the client, dedicated server, or both.
- 04
Pick the file you checked
Use the “Get this file” button beside freshloot-2.0.0+26.3-forge.jar. It opens that exact file at the source.
About this project
What does FreshLoot add?
Make looting structures and dungeons more "fair" on your SMP server.
A chest or barrel with a loot table gives out an independent loot roll to each player, once per player and per position.
The problem this solves
By default, a loot chest (in a dungeon, a structure, an ancient city, a boat, etc.) generates its contents once, on first open. The first player to open it picks from the pool; everyone after that only finds whatever is left; if anything is left.
On a multiplayer server, that just rewards whoever gets there fastest. This might not be very fair; your server, your rules.
With FreshLoot, every player who opens the chest for the first time gets their own roll, as if he was alone in front of a brand-new chest. Once a player has looted it, he can't pull a second roll from that position.
Mechanics
- Opening: when a player opens a chest or barrel carrying a loot table, the mod checks whether he already has looted this position. If he has, the open is denied (no GUI ever shows up). If not, loot is generated normally for him.
- One chest at a time: if a player has a chest open, no other player can open it at the same time. He has to wait for the first one to close his GUI.
- Rotation: when the GUI closes, the chest is destroyed and immediately replaced with a new one, carrying the same loot table, ready for the next player. This same mechanism is what lets the mod work without depending on in-memory state that could get lost: the new chest carries its loot table directly in its own data, exactly like a vanilla chest that's never been opened.
- Breaking instead of opening is griefing: breaking a chest that still has an unclaimed loot table (whether it's brand-new, freshly put back into rotation, or currently open by someone, including the breaker themselves) sends a public message to the server and empties the loot before the block drops. The chest then gives out nothing: not to the player who broke it, not to anyone after them, since the position itself is destroyed (unless currently open by someone, in case the content is dropped).
- Persistence: the record of "which player has already looted which position" survives a server restart. Everything else (who currently has a chest open, etc.) is deliberately non-persistent state. It only makes sense while the server is running.
- Spectator mode: entirely ignored. A spectator can look inside any chest, including one currently open by a player, without triggering any of the rules above.
Known limitations
- Double chests aren't handled. A double chest (two single chests joined together) is left to full-vanilla behavior. The mod doesn't touch it at all, even if it carries a loot table.
- Only chests and barrels. Any other loot-table-carrying container (shulker box holder, modded barrel, etc.) follows standard vanilla behavior.
- Rotation breaks and replaces the block. The refresh mechanism relies on physically destroying the chest and recreating it identically. It's invisible in-game, but it means a chest "in rotation" literally changes block identity on every cycle. A third-party mod that tracks block entities by reference might not be happy about that.
Wishlist
- Double chest support.
- Support for other loot-table-carrying containers (maybe)
- External configuration, instead of hardcoded constants (e.g. being able to disable the grief message, edit its text, or even its behavior).
- Translation of the grief message (currently English-only, not localized).
Issues
If you find a bug, want a feature added or want to contribute, please open an issue or make a PR on GitHub.
Project description from CurseForge.
Pick your setup
FreshLoot by Minecraft version and loader
Choose the version and loader you play, then open the matching release.
1.21.4
3 loader buildsCheck the dependencies, then try the file in a copied instance before changing a world you care about.
Recent files
FreshLoot versions and loaders
freshloot-2.0.0+26.3-forge.jar
freshloot-2.0.0-26.3-forge.jar
12 Nov 2026
freshloot-2.0.0+26.3-neoforge.jar
freshloot-2.0.0-26.3-neoforge.jar
12 Nov 2026
freshloot-1.4.7.jar
1 Oct 2026
freshloot-2.0.0+26.3.jar
1 Oct 2026
Looking for an older file? The official CurseForge project page is in Resources.