Loot Integrations Mod FAQ

Launch the game once so the mod generates its config files, then open the config folder and look for the Loot Integrations files. Edit those files to point at the loot tables you want to inject and where you want them to go, then reload or restart the game.

Everything is done through the mod's config files rather than in-game menus. You specify a source loot table and a list of target loot tables, and the mod merges the source loot into those targets.

The source is the loot table whose items you want to spread around, usually a vanilla chest table or a custom one you made. The targets are the modded dungeon chest tables you want those items to appear in.

Yes, a single source loot table can be listed against multiple target loot tables. This is the main point of the mod, since it lets one set of items show up across many different structure mods' chests.

Each entry has an amount or weight value that determines how much of the source loot gets merged in. Raising it adds more items per chest, lowering it makes the injection more subtle.

Yes, you can create a custom loot table containing those items and then use it as a source. This is the standard workaround for mods that add gear but no dungeon loot of their own.

The most common causes are a typo in a loot table ID, editing the wrong config file, or not reloading the game after saving. Double-check the exact table names and make sure the target tables are the ones the dungeon actually uses.

Config changes are usually picked up on a world reload or game restart rather than instantly. If nothing changes after saving, restart and test a fresh chest.

It generally works alongside other loot mods because it only merges tables rather than replacing them. Conflicts can still happen if two mods write to the same target table, so test after adding new loot mods.

The impact is minimal because it only modifies loot table results when a chest is generated or opened. Large numbers of injected entries or very heavy source tables can add a small cost, but it's not a worldgen-heavy mod.

Open the mod's config folder and look at the shipped loot table files for the structure mods you have installed. Each file maps a vanilla or modded loot table into the chests of a specific dungeon, so you can edit those entries directly or copy one as a template for a new dungeon.

It injects loot from one loot table into the chests of dungeons that use their own custom loot tables. This means modded gear that normally only spawns in vanilla chests can also appear in structure mod chests, and vice versa.

Find the config file for that dungeon and add an entry pointing at the vanilla loot table you want, along with an amount value. The mod then rolls that table and merges the results into the dungeon's chest loot.

Since Immersive Armors doesn't ship its own loot table, you create a loot table that contains those armor pieces and then reference it from the dungeon config. The mod treats it like any other loot table, so the armor can then appear in whichever dungeons you list.

It controls how many times the referenced loot table is rolled when the chest is generated, which scales how much of that loot shows up. Higher amounts mean more entries from that table, so keep it modest if you don't want dungeons flooded.

The most common causes are a typo in the loot table ID, editing the wrong dungeon's config file, or the dungeon using a loot table the mod doesn't hook into. Double-check the exact resource location and make sure the config file matches the structure you're testing.

Loot is generated when a chest is first placed, so already-generated chests won't change. New chunks and newly generated structures will use your updated config, so test in fresh terrain rather than an existing dungeon.

It works alongside mods that add their loot through vanilla loot tables, since it just references those tables. Mods that completely replace chest generation or use their own non-standard loot system may not be hookable, so check whether their chests use loot tables at all.

The mod only runs when a chest is generated, so the impact is minimal during normal play. Very large amount values or a huge number of entries per dungeon can slow world generation slightly, so keep configs reasonable.

Start with small amount values and only add a few loot tables per dungeon, then playtest to see how generous the chests feel. If a dungeon becomes too rewarding, lower the amount or remove the least fitting entries rather than adding more.