Generates datapacks for (Java) Minecraft that randomize the loot tables, resulting in randomly different (but consistent) drops from objects, chests, entities, and gameplay elements such as fishing. Chaotic fun!
Features •
How It Works •
Getting Started •
Creating and using RLT datapacks •
Configuration
Release History •
License •
Contribute •
Connect •
Support RLT
- User-selectable random seed
- Automatic updating of loot tables to correct impossible drop conditions and certain other issues
- Some customization of loot table selection and handling
- Forensics files generated in datapack that list loot table assignments for convenient post-game analysis
- Easy to use: No modding required; simply add the datapack to the save game's datapacks folder
- A brand new gameplay experience every time
- Google Sheets loot table tracker available to help players keep track of drop chains during game play
Memetics' Random Loot Tables (RLT) loads copies of the default (Java) Minecraft loot tables. Based on a user-provided or system-determined random seed, it randomly redistributes the loot tables' contents, modified based on the RLT configuration settings, which allows it to avoid problematic drop assignments that would prevent game progression or make progression overly difficult and frustrating.
Then the tables are revised to correct impossible-to-meet conditions checks that would prevent drops, such as the "killed by player" condition applied to a non-mob, and to correct certain other issues. The resulting table set is written to a Minecraft datapack .zip file, which then can be added to the datapack folder of a new or existing Minecraft world.
click to expand
To install Memetics' Random Loot Tables (RLT) on Windows, extract the .zip file contents to a folder on your PC. RLT can be run directly from the source code using Python IDLE (available for free at https://www.python.org/) or using the RLT.exe file included with the release. For RLT to work, however, the Minecraft "loot_tables" folder first must be added to the RLT folder.
RLT needs to have access to a copy of the Minecraft "loot_tables" folder, with all of its files and sub-folders and their files. RLT will not run without a copy of the loot_tables folder being added to the RLT folder.
The loot_tables folder must be extracted from the current (Java) Minecraft game installation (or more accurately, from the version of the game corresponding with this version of RLT) and copied to the RLT application folder.
To extract the "loot_tables" folder from your Minecraft installation:
- In Windows File Explorer, navigate to the current Minecraft installation folder, which in Windows is normally found in %AppData%/.minecraft/versions/[version]/[version].jar/data/minecraft/loot_tables. (For the current (0.15.4-beta) RLT build, the [version] folder is named "1.19.3".)
If you are unsure how to locate the loot_tables folder, start by pasting this into the location bar in Windows File Explorer:
%AppData%/.minecraft/versions/
Then in the "versions" folder, open the folder named with the current Minecraft version: for instance, the folder named 1.19.3. (The folder is created when you first launch that version of the game; so if the folder does not exist, open the Minecraft launcher and start that version of the game, so the Minecraft launcher will download all of the files necessary to run that version of the game.)
-
**Note**: If you are unable to locate the Minecraft root installation folder, Minecraft may be installed in a different location on your system. Wherever it is located, navigate to the root ".minecraft" folder where the game is installed, open the "versions" folder, and then locate the folder for the current version of the game.
-
In the [version] folder, open the compressed [version].jar file using a file compression utility such as 7Zip. (For instance, in the folder called 1.19.3, the file will be called 1.19.3.jar.)
-
In the compressed .jar file, open the "data" folder, and then open the "minecraft" folder.
-
In the "minecraft" folder, extract the "loot_tables" folder, copying it into the RLT folder.
-
Once the loot_tables folder and its contents have been extracted into the RLT folder, the RLT application should be able to run.
click to expand
When you run the RLT application, it will prompt you for a seed to use for randomizing the loot tables. If you use the same seed and the same set of loot tables and config files, the application will generate the same (identical) datapack each time. If you do not enter a seed, RLT will use a system-generated random seed. Every time RLT is launched, the system-generated seed is determined at random, resulting in a different datapack each time. (So if you want to produce the same datapack each time, manually enter the same seed each time.)
Once RLT generates a new datapack, it writes the datapack as a .zip file to the "RLT datapacks" folder in the RLT folder. If you provided a seed, the file name will include the seed.
Copy the RLT datapack .zip file to the "datapacks" folder located in the savegame folder for a new or existing Minecraft world, and the loot drops will be randomized.
If you want to create a new world in which the loot tables start randomized (this works in Minecraft version 1.17 and later):
- On the Singleplayer* menu, click "Create New World."
- In the "Create New World" form, click "Data Packs."
- In the "Select Data Packs" form, click "Open Pack Folder." The datapacks folder for the new world will open in a new File Explorer window. (The files for the new world are located in a temporary folder until world creation is finalized.)
- Copy the newly generated RLT datapack from the "RLT datapacks" folder into the new world's "datapacks" folder. (Once the file is added to the folder, you can close the File Explorer window showing the new world's "datapacks" folder.)
- Switch back to Minecraft: The datapack should now appear in the "Available" list.
- Click the RLT datapack icon to move the datapack to the "Selected" list, and then click "Done."
- Update any other world creation settings as desired.
- Finally, click "Create New World" to finish world creation and launch your new RLT world!
The process is simliar for Mulitplayer worlds. However, if you are running the standalone Minecraft server, you may have to launch the server to let it create the new world for the first time (so that the world savegame folder and its "datapacks" folder will be created), stop the server, add the RLT datapack to the world's datapacks folder, and then restart the server.
- If the world is currently open in Minecraft, exit the world (or stop the server).
- In File Explorer, navigate to the savegame folder for the world. (By default, this folder is located in %AppData%/.minecraft/saves/. However, you can also open the world save folder from within Minecraft: On the Singleplayer menu, select the world, click Edit, and then click "Open World Folder.")
- In the world's savegame folder (which should be named the same as the world name), open the datapacks folder.
- Copy the RLT datapack .zip file into the datapacks folder.
- Resume playing the world. The loot drops will now be randomzied.
click to expand
The lists in the configuration files are used primarily to prevent loot table assignments that block game progress, such as assigning blaze rods to drop from an End chest when blaze rods are needed to gain access to the End in the first place. The config lists also allow the exclusion of certain loot tables from random assignments, such as table assignments that would make the game too frustrating to play. For instance, if blaze rods only dropped from certain infested blocks, it might take a frustratingly long time of random digging before locating those blocks in the hope that blaze rods could be obtained from them.
The bottlenecks.config file holds the list of loot tables for loot that is needed for progression. By default, it contains blaze.json and enderman.json, since ender pearls and blaze powder are needed to help locate strongholds and activate the End portals to allow passage to the End. Technically, Ender pearls also can be obtained through Piglin bartering (as of Minecraft 1.16), so Ender pearls most likely could still be found even if Enderman drops are not available, but if both of those bottlenecks get assigned to drop from objects or entities exclusive to the End, game progression to the End still will be highly unlikely if not impossible. (For a more cautious configuration, piglin_bartering.json could also be added to the bottlenecks.config list.)
The blockers.config file holds the list of loot tables to which RLT will avoid assigning the drops from tables listed in bottlenecks.config. This way, the important bottlenecks drops will not be overly difficult if not impossible to find. Probably nobody wants to dig around all over the world at random to try to locate an infested diorite vein in the hope that maybe it will drop an Ender pearl or two, and no one wants the starting bonus chest to be the only place where one can find a blaze rod. We might still want the blocker tables' drops to be assigned elsewhere, but we don't want those to be the only droppers of important resources. So the blockers tables are withheld from the assignment pool until the bottlenecks tables have been assigned to non-blockers from the general (non-blocker, non-excluded) unassigned tables list; then the blockers are added to the general assignment list for random assignment with the rest of the pool.
The exclusions.config file holds the list of loot tables that will not be altered; the tables in this list will remain unrandomized. This list contains:
- Showstoppers: Things that won't drop anything, preventing potentially important resources from dropping, either because they're not implemented in the game (as with certain entities like Giant and Zombie Horse) or because the Minecraft code prevents them programmatically from producing drops;
- Not yet implemented: Tables for objects and entities that are planned for a future release of Minecraft but that have not been implemented in the current release of the game (and therefore will never drop any loot assigned to be dropped from them); and
- Killjoys (a.k.a. frustrators): Tables which, if included in the randomized loot (either as droppers or to have their loot dropped by something else), would make the game significantly less fun. The items on this list are less problematic for game progression and are more a matter of taste.
To prevent assignments that block game progression, such as blaze rods being assigned to drop from chests or entities only found in the End, the default blockers and bottlenecks lists generally should be kept as they are, although piglin_bartering.json could be added to bottlenecks.config to help ensure the availability of ender pearls.
At the very least, keep blaze.json and either enderman.json or piglin_bartering.json in the bottlenecks.config list, and keep very rare or hard-to-find droppers (such as spawn_bonus_chest.json and the infested blocks) in the blockers.config list.
The default "Showstoppers" and "Not yet implemented" lists in exclusions.config should also be kept as-is.
However, the "Killjoys" list (in exclusions.config) can be modified as desired. Additional loot tables may be added to the killjoys list if you want to reduce the frustration of having to hunt for days on end to find certain hard-to-find loot drops, or if there are certain things that you simply want to have retain their normal drops.
-
Memetics finds it tedious to have 17 varieties of candle dropping as part of the randomized loot set, not to mention having candles of the same color dropping from two different sources (if candle cakes were left in), and he thinks that candle cakes are just silly to begin with, so those loot tables are included on his default Killjoys list. Memetics also (currently) likes to have shulker_box.json on the list and therefore unrandomized, so that at least one type of shulker box is available as a reusable shulker box for gameplay. But YMMV, so adjust the Killjoys list as you see fit.
Feel free to experiment, though! The config lists may be modified or even removed entirely, and RLT will still generate the datapacks - and you still might get lucky with what items get dropped from where - but ultimately, you will have to be the judge of the results of such experiments.
For the release history, see the version tags in the RLT GitHub repository. RLT releases follow semantic versioning.
-
Note: The RLT code is provided as-is and is not actively supported, though Memetics plans to update the code from time to time, as time permits.
Distributed under the GNU GPL 3.0 license. See the LICENSE file for more information.
If you are a developer interested in contributing to the project, please contact Memetics on the Mining after Dark Discord server.
Join the discussion of RLT on the Mining after Dark Discord server. You can also report issues with installing or running Memetics' RLT on the RLT GitHub repository.
If you like this project, please consider dropping by the Mining after Dark Discord server to say thanks!
Or you could buy Memetics a decent meal:
I hope you enjoy using RLT and playing Minecraft with random loot tables! :D
-Memetics
