myLoot

Description

Description

myLoot replaces world-generated loot containers such as loot chests and barrels with a special myLoot container variant that has instanced loot per player.  This means each player can loot whatever they want out of any loot chest and other players will still have access to the original loot - providing a better looting experience!

No more logging onto a multiplayer server to find chunks within a 5000 block radius have already been looted by your friends.  Loot for all

myLoot is useful in singleplayer servers as well - you can visually see which loot chests you have already opened so you don't end up getting lost and re-looting areas

Features

All replacement works in modded structures as well as vanilla (dungeons, villages, strongholds, dimensions, etc.)

• Replaces loot chests (works for double chests!)
• Replaces loot barrels
• Replaces chest Minecarts
• Replaces Shulker Boxes
• myLoot containers will change in appearance to the player if they have opened it.  This is client-side so other players will still see the unopened textures if they have not opened it.
• myLoot containers will warn the player that breaking it can affect other players.  A player can still break myLoot containers by holding Sneak while breaking.  Note: breaking a myLoot container by default will only drop the instanced loot of the player who broke it (plus the loot container item).  This can be changed via the "dropBehavior" config to instead drop ALL players' loot
• This should work with modded items in the myLoot containers as well and with modded loot containers
• myLoot Chest is craftable with a regular Minecraft chest surrounded by enchanted apples (see images above)
• myLoot Chest can be combined into a double chest
• myLoot Chest Minecart is craftable with a myLoot chest and minecart
• myLoot Shulker Box when broken will drop a special myLoot Shulker Box Item that persists instanced inventories, so players can still access their instanced loot from the shulker box when it is placed back down.  Essentially, it's a portable instanced shulker box!

Dependencies

This mod requires:

• SpoornPacks - https://www.curseforge.com/minecraft/mc-mods/spoornpacks
• Fabric API - https://www.curseforge.com/minecraft/mc-mods/fabric-api 

FAQ

1. How does inserters/extractors such as hoppers/pipes affect the myLoot containers?

Modifying a myLoot container's inventory before player opening - such as using hoppers to add/remove items - should not affect the player's instanced inventory.  The original rolled loot will persist so any player opening a myLoot container for the first time will still get the original loot.

Also, myLoot containers essentially have an invisible inventory that contains the original non-player instanced inventory.  Modifying that inventory via inserters/extractors such as hoppers/pipes will work, but when a player breaks the myLoot container, only additions to the original rolled loot will drop (plus the player's instanced inventory who broke the myLoot container if applicable).  This is to prevent mass duplication of loot (however duplication of the original loot one time is still possible... I haven't yet found a way to prevent this without being invasive i.e. I don't want to break any code, vanilla or modded, that has logic around a loot container's inventory so I can't just delete the original invisible inventory).

Credits

The mechanics of myLoot containers changing appearance when opened by a player, and the stylish glowing texture design are heavily inspired by the Forge Lootr mod - but everything else was originally made from scratch.  myLoot is not a direct port of Lootr, and features will be different.  An official port of Lootr to Fabric is in the works.  Please see https://github.com/spoorn/myLoot/issues/1

Need a Server?

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