Getting Started
Installing
Section titled “Installing”To use Loot Table Modifier, you first gotta have it installed (I am so damn good at writing useful documentation, no need to thank me 👍)
When developing a plain datapack, all you need to do is download it from modrinth and put it in your mods folder.
You may also want to show the Requires
badge in your readme, see below for an example and here for more info.
Mod developers
Section titled “Mod developers”Mods can depend on Loot Table Modifier like this:
repositories { // ...rest of repositories block maven { name = "OffsetMods538" url = "https://maven.offsetmonkey538.top/releases" content { includeGroup "top.offsetmonkey538.loottablemodifer" } }}
dependencies { // ...rest of dependencies block
implementation "top.offsetmonkey538.loottablemodifier:loot-table-modifier:VERSION_HERE"}
Make sure to replace VERSION_HERE
with the actual version you want to use!
See my maven page here for all available versions and their javadocs.
Also add this to your fabric.mod.json
file:
{ "depends": {
"loot-table-modifier": ">=2.0.0 <3.0.0" }}
Development Mode
Section titled “Development Mode”Development mode enables additional logging and the ability to export modified loot tables.
Dev mode will automatically be enabled when Minecraft is launched from an IDE or can be enabled by setting the JVM property lootTableModifierDev
to true
.
That can be done with Prism Launcher by going to Settings
, selecting Java
and then adding -DlootTableModifierDev=true
into JVM arguments
.
Mod developers who, for some weird reason, don’t want their logs to be spammed with random unnecessary stuff can set the property to false
to override the IDE check.
Modified loot tables can then be exported using the command /loot-table-modifier debug export
.
Next Up
Section titled “Next Up”Take a look at how loot modifiers work here and then take a look at the examples.