Lootr (Forge & NeoForge)

Description

Lootr is also available for Fabric!
As of 1.20.4, Lootr will only be available for Fabric and NeoForge.
Lootr is required on both servers and clients.
For 1.12.2, MixinBooter is required.

What does it do? Each container that has a loot table (supporting chests, trapped chests, barrels, shulkers and minecarts) creates a unique inventory for each player who opens it! These containers also have a distinct appearance, and their colour changes from gold to blue if a player has already opened the container.

How does this help? There's no longer a race to be the first to discover structures, and you will never open a loot chest and find someone's left-over trash. Most importantly, it encourages players to explore existing structures, rather than generating new chunks, thus reducing world size!

What versions is it available for? It's available for all recent releases since 1.16.5 and is actively developed for these. Thanks to embeddedt, it is now also available for 1.12.2!

Frequently Asked Questions

Q. How do I get support?
A. You can check out my Discord (linked below) or alternatively create an issue on our GitHub, which can be found by clicking on "Issues" above.

Q. What versions does Lootr support?
A. Currently, Lootr for Forge supports the following versions: 1.12.2, 1.16.5, 1.17 (not actively developed), 1.18/1.18.1, 1.18.2, 1.19/1.19.1/1.19.2, 1.19.3 and 1.19.4. Please check the "All Files" page if you cannot find a download for the version of Minecraft you are playing. Support for Forge 1.20.1 is forthcoming.

Q. Is there a server-only version? Can I connect without installing it on the client?
A. No, Lootr is currently required on both the client and the server. If are willing to help design a server-only version, please reach out on Discord (link found below). There are several plug-in solutions inspired by Lootr (and some that pre-date it): LootIn is a Spigot plugin for Minecraft 1.16 through 1.20.

Q. How does Lootr generate loot?
A. Lootr copies the Vanilla method that unpacks a loot table and fills a container from it. Please note that this is a direct copy of the Vanilla code (modified to function with Lootr's systems). This means that mods which directly modify the Vanilla method using Mixins, etc, will not affect Lootr. As far as I am aware, there are no mods that currently do this.

Q. How do I change what loot is generated with Lootr? How do I include loot from other mods in Lootr containers?
A. This is beyond the scope of the Lootr mod, which simply changes the containers. In all other respects, loot is generated in exactly the same way as Vanilla chests generate it. Modifying loot tables is generally done via data packs, although various mods exist for various versions of Minecraft which do this. I recommend asking in your favourite modded Minecraft Discord or forum!

Q. What about dungeon mods? How do I prevent players from going in and looting everything after it has already been cleared?
A. There are a number of options that help with this:

• Specific loot tables can be blacklisted, which means that those chests will never be converted. You can also specify simply all loot tables of a certain mod. Likewise, specific dimensions can be blacklisted.
• Alternatively, you can specify for certain containers (or all containers), determined by their loot table, to "decay". This means that a configurable time after they are first opened, the next time someone attempts to open the container, the block will be destroyed. There also exists the opposite, a system whereby chests will "refresh" (or re-generate their contents) after the configured period of time has elapsed.

Q. Does Lootr support Luck?
A. Yes. As noted above, Lootr uses an exact copy of the Vanilla method for generating loot, which means that a player's luck is applied.However, by default, the only Vanilla loot tables which support Luck are those used in Fishing. Any other mod-supplied or mod-edited loot table, or any data pack which includes modifiers for luck, are supported by default.

Q. How do I prevent players from simply breaking containers?
A. By default, players who attempt to break a container will be given a warning message and a reminder that all containers are available per-player. Players can still break these containers by doing so while sneaking, unless this option is disabled in the configuration.

Q. I don't like the visual appearance of the containers. How can I change this?
A. There is a client-side option that forces containers to use the default Vanilla skin. However, this does mean there is no visual change to indicate if a container has been opened before.

Q. Can I add Lootr to a pre-existing world and have containers be converted?
A. Yes! With one disclaimer: loot containers which were already opened will not be converted. The generation of loot in Minecraft, by default, removes the associated loot table, and there is no way for Lootr to find this information. Please note: this option is only partially-functional in 1.12.2; chests that generate their contents during world generation cannot be retroactively converted.

Q. The container from <random mod> isn't converting!
A. If the container contains items (or always contains the same items), it is possible that the mod is manually generating loot for it. In this case, there is no way for Lootr to determine a loot table and convert chests. I recommend asking the author of the mod to consider switching to a loot table instead to maintain compatibility! If the container is empty, it is possible that it is merely included for the aesthetic. Otherwise, if you believe there's an issue with conversion, please open an issue on our GitHub tracker or post on Discord. Additional methods for converting containers exist for 1.12.2.

Please note that the "axe chest" in the Vanilla Woodland Mansion does not have an associated loot table and is never converted.

Q. I no longer want Lootr. What happens if I remove it?
A. Unfortunately, removing the mod will also remove all Lootr containers. There is currently no way to undo the conversion process. This means that every Lootr converted container will be removed from your world.

Q. I want to create a "starter" chest with some items in it for everyone in my world, how do I go about this? How do I create my own Lootr container?
A. Lootr also contains "custom" inventories which use the same visual appearance as a chest. Simply create a Vanilla chest, fill it with the items you want available and then, while standing on it, execute the /lootr custom command (this requires operator privileges). 

Q. What else does the /lootr command do?
A. For a full explanation of the command, please check out the Lootr Command page on our GitHub Wiki.

Q. How do I use Lootr in a mod pack, or how do I natively use Lootr in my Mod?
A. For a full explanation of Lootr's features for mod packs, as well as the Lootr API, please check out the Lootr for Developers page on our GitHub Wiki.

Q. What do all the configuration options mean?
A. For a full explanation of Lootr's configuration, please check out the Lootr Configuration page on our GitHub Wiki.

Q. Is there a video I can watch?
A. There sure is! Vallen from Mischief of Mice has graciously created this bit-by-bit video that covers the rough basics of Lootr, although this is from an earlier version of the mod and does not cover all recent additions:

Patreon & Discord

You can support me on Patreon!
All support for this mod is available on my Discord. You can also keep up with what I'm doing and get notifications streams! For all other support, please click on "Issues" at the top of this page.

What means Verified?

• Compatibility: The mod should be compatible with the latest version of Minecraft and be clearly labeled with its supported versions.
• Functionality: The mod should work as advertised and not cause any game-breaking bugs or crashes.
• Security: The mod should not contain any malicious code or attempts to steal personal information.
• Performance: The mod should not cause a significant decrease in the game's performance, such as by causing lag or reducing frame rates.
• Originality: The mod should be original and not a copy of someone else's work.
• Up-to-date: The mod should be regularly updated to fix bugs, improve performance, and maintain compatibility with the latest version of Minecraft.
• Support: The mod should have an active developer who provides support and troubleshooting assistance to users.
• License: The mod should be released under a clear and open source license that allows others to use, modify, and redistribute the code.
• Documentation: The mod should come with clear and detailed documentation on how to install and use it.

How to Install