Support

Support and Bug Reports

Start with Troubleshooting and the FAQ. Many apparent loot problems are caused by testing an already-generated chest, using an incompatible loader, or disabling every eligible volume in Biblio's settings.

Information to include

When reporting a problem through the public bibliowiki repository's Issues tab, include:

• Biblio version,
• Minecraft version,
• NeoForge version,
• Scholar version if installed,
• singleplayer or dedicated-server environment,
• a concise description of what happened,
• exact reproduction steps,
• the relevant client or server log, and
• any loot-integration JSON involved.

Do not include access tokens, private server credentials, personal information, or the contents of a private repository.

Integration reports

For structure or modpack compatibility problems, also include:

• the exact target loot table ID,
• the sidecar file's resource path,
• the requested tags and work IDs,
• whether /reload reported an error or zero-match warning, and
• whether the target container was unopened before testing.

Review the Data-Driven Loot Integration API and Work-Level Tags before filing the report.