Troubleshooting

Troubleshooting

Biblio does not load

Check all of the following:

• Minecraft is Java Edition 1.21.1.
• The loader is NeoForge 21.1.211 or newer within the 21.1 line.
• Java 21 is being used.
• The downloaded file is a Biblio NeoForge JAR, not GitHub's source ZIP or the legacy datapack.
• Server and clients have matching Biblio versions.

The reviewed repository does not provide a Fabric or classic Forge build.

No books appear in chests

• Test a newly generated structure or a container whose loot has never been generated.
• Open /biblio and confirm at least one relevant catalog branch or volume is enabled.
• Check the server log for datapack or loot-table errors.
• If another mod replaces a vanilla loot table unusually, test without that mod to identify the conflict.
• Run /biblio selftest as an operator.

Books appear twice

Remove the legacy Biblio datapack if the Biblio mod JAR is installed. Also search all datapacks and mods for multiple integration rules targeting the same loot table. Tagged integration rules are additive.

A settings change seems to do nothing

Close the settings menu so changes are saved, then test a fresh/unopened container. Existing generated loot is not rewritten.

/biblio says I lack permission

The command tree requires permission level 2. Enable cheats in singleplayer or ask a server administrator to grant operator permission.

The collection command overwrote blocks

This is expected behavior: the collection places a barrel wall two blocks south of the executing player and replaces the necessary blocks. Restore from a backup if needed, then run it again in a prepared open area.

A long work gave only one volume

That is normal. A work-level loot roll chooses one physical volume. Use the catalog to identify all volumes, use /biblio give for specific entries, or run /biblio collection for a complete physical collection.

A tagged integration adds no books

1. Confirm the installed Biblio release includes the tag-driven integration API.
2. Confirm the file path is data/<namespace>/biblio/loot_integrations/<name>.json.
3. Confirm target is the exact loot table ID, not the structure ID or a filesystem path.
4. Run /reload and read the server log.
5. Inspect data/biblio/work_tags.json inside the Biblio JAR and verify the requested tags or work IDs exist.
6. Check that filters are not contradictory.
7. Check chance; a value below 1.0 is intentionally intermittent.
8. Check Biblio's chest settings for disabled candidates.
9. Test an unopened container.

Biblio logs a warning when a valid integration currently matches no works and an error when a file cannot be parsed.

A tagged integration adds too many books

• Reduce rolls or chance.
• Look for multiple files targeting the same loot table.
• Remember that every rule in every loaded namespace is evaluated independently.
• Avoid targeting both a parent loot table and an internal subtable when one roll can invoke both.

Scholar visuals are missing

Scholar is optional. Confirm version 1.2.4 or newer is installed on the relevant client and server. Biblio books remain readable without it.

Still stuck? Follow Support and Bug Reports and include the Biblio version, Minecraft/NeoForge versions, relevant logs, reproduction steps, and the integration JSON if applicable.