-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
Not in the reviewed repository. The current source targets Minecraft 1.21.1 on NeoForge 21.1.x.
No. Scholar 1.2.4+ is optional and improves visual presentation. Biblio remains readable without it.
No. Biblio converts cited public-domain editions into Minecraft written books. Long works are divided rather than summarized or abridged.
Minecraft written books have a 100-page limit. Biblio follows natural divisions and creates sequential parts when a division exceeds that limit.
Within a selected work, enabled physical volumes are selected uniformly. The tag-driven integration API first selects a work uniformly, so works with many volumes do not dominate works with one volume.
They are the same Biblio quality. Commands use common; library is accepted as an alias.
Yes. Damaged variants apply condition-specific loss or obscuring to their text. The other qualities represent complete readable copies.
Any signed quality appears about once every 56.82 book rolls under the generated weights. A signed First Edition is exactly 1 in 2,500 per book roll.
Use /biblio as an operator. Right-click a shelf to toggle the entire catalog section beneath it, or navigate to an individual physical volume.
No. Minecraft does not reroll loot already generated for a container. Use new structures or unopened/un-generated containers.
Yes, in Biblio builds that include the tag-driven integration API. The mod can ship a sidecar JSON under data/<namespace>/biblio/loot_integrations/. Biblio reads it when present; without Biblio, the structure mod's normal loot remains unchanged.
The verified API uses a sidecar integration JSON rather than a custom entry inside the normal loot table. This keeps compatibility optional and avoids putting Biblio-specific entry types in the structure mod's primary loot data.
No. It is a loot table ID such as yourmod:chests/sunken_library. A structure may use several target loot tables.
In a compatible generated Biblio build, inspect data/biblio/work_tags.json inside the JAR.
Yes. Put the same sidecar JSON in a normal datapack. This is useful for compatibility patches and pack-specific balance.
No. Installing both can load Biblio data twice. Use the mod JAR by itself unless you are deliberately performing legacy compatibility testing.
Home · Full Catalog · Troubleshooting · Support · License
Documentation verified from repository source; snapshot prepared 2026-08-18.