Users Troubleshooting

Troubleshooting

This page is about loot. Worldgen problems have their own page: Worldgen Info → Troubleshooting.

Nothing shows up in the viewer

1. Check that the mod is installed on both the client and the server.
2. The client asks the server for the data while the recipe viewer loads, at game/world start — not when a category is opened. On a large pack that transfer takes a moment.
3. Check the server log at startup — the scan happens there, and failures are logged there.
4. Check the client log for Starting data registration.... If the transfer fails, the client retries up to three times (30 s each) and then logs that the viewer integration will be empty or incomplete.

The game will not start, or tooltips show keys like aci.util.tag

Advanced Core Info (ACI) is missing or is the wrong version for your Minecraft version and loader. It is a required library — see Getting Started. A refusal to launch names aci in the loader's error screen; a partially loaded setup shows untranslated aci.util.* keys in the loot tree instead of readable text.

A category is missing

• It may be hided in config/ali/ali_common.json. On a server, a hidden category is never sent to clients.
• It may be swallowed by an earlier category: assignment stops at the first matching category. See Loot Categories.

A block shows no loot

Blocks that only drop themselves are hidden on purpose (hideDefaultBlockLoot). Set it to false in the configuration if you want them listed anyway.

A mob's loot is missing or shown on the wrong mob

ALI derives the owning entity from the loot table's ID. A table whose ID follows no convention can end up unattributed or attributed to a different entity — declare it explicitly with entityLootTables in the configuration. The server log points this out too, together with how much time the fallback resolution cost.

A table that another loot table pulls in by reference is not treated as a mob's own table, so it is shown as part of the referencing table instead of being attributed to some entity.

A drop is missing entirely

• If the game hardcodes the drop, it has no loot table to scan. Add it with Fake Loot.
• If another mod injects it in a way ALI cannot see, that mod needs a plugin.

A tooltip shows unformatted data under "Auto-detected"

ALI does not recognise that condition or effect, so it shows its raw data instead of dropping it. Nothing is broken — a readable description has to come from the mod that added it (developer docs).

If the mod ships no such support, ALI Compat may already cover it — check whether the mod is on its list for your Minecraft version.

The same raw data also appears when support for it exists but fails — from the mod itself or from ALI Compat, typically after the mod was updated. Only that one entry, condition, effect or trade is affected; the rest of the loot table or trader is still shown. The server log names it with showing it as unsupported; please report it, with the log, to whoever ships that support.

A count or chance shows ?

? is a value ALI cannot work out ahead of time. With a mod's type in brackets — ? (somemod:custom_count) — it comes from that mod: either ALI does not know how to compute that mod's value, or the support for it (from the mod itself or from ALI Compat) failed. Only that one value is affected; the rest of the loot table is still shown, and the server log names what failed. Please report the latter, with the log.

The game crashes while ALI scans an entity

Add the entity's ID to disabledEntities in the configuration; it is then skipped during the scan. Please also report it, with the crash log — see "Reporting a bug" below.

Server startup is slow / a lot of memory is used

The whole loot tree is built once at server start and kept in memory. On very large packs this is noticeable. Ways to reduce it:

• hide categories you do not need — hidden categories are neither built nor transferred,
• keep logMoreStatistics off (it is a debugging aid only).

I changed the config and nothing happened

The config file is read while the mod starts. Restart the game or the server. Datapack content (including fake loot) is picked up by /reload.

My config file was reset

That happens when the config format version changes with a mod update. The old file is kept next to it as a timestamped backup such as ali_common.json.2026-10-06_14-30-05.bak; re-apply your changes onto the newly generated file. See Configuration.

Reporting a bug

Include the Minecraft version, loader, recipe viewer, ALI version, the log, and — if it concerns a specific drop — which block/entity/table it is about: https://github.com/yanny7/AdvancedLootInfo/issues

For questions that are not bug reports, there is also a Discord.