Work Level Tags

Work-Level Tags

Work-level tags let a datapack or structure mod request themes such as ocean literature, Gothic fiction, mythology, science, or a particular author without listing every Biblio book.

These are Biblio metadata identifiers, not Minecraft item tags. Do not prefix them with #.

Availability

Work tags belong to the tag-driven loot integration feature. Use them only with a Biblio build whose release notes include tagged loot integrations. The repository's public default branch did not yet contain this feature at the documentation snapshot; the verified implementation was on agent/work-tags-loot-integrations.

Tag format

Tags are resource locations:

biblio:ocean
biblio:science_fiction
biblio:author/charles_darwin
biblio:catalog/nonfiction/science

Inside an integration file, a short tag automatically uses the biblio namespace:

"ocean"

is equivalent to:

"biblio:ocean"

Explicitly namespaced tags, such as yourmod:scholarly, are accepted, but they match only if Biblio work metadata actually contains that exact tag.

How tags are generated

Every work receives baseline tags from existing catalog and location metadata:

• biome/location groups such as ocean, jungle, mountain, village, and deep_dark
• catalog paths such as biblio:catalog/literature/science_fiction
• useful short collection and genre/form tags
• author tags under biblio:author/...
• culture and tradition tags where available
• biblio:traditional for traditional works

A curated semantic layer adds concepts that cannot be inferred reliably, including examples such as:

maritime, whaling, gothic, horror, science_fiction,
epic_poetry, romance, tragedy, 19th_century

For example, Moby-Dick is curated with tags including adventure, american, fiction, maritime, ocean, whaling, and 19th_century.

Tags and physical volumes

Tags belong to the real-world work. Every physical volume and every quality/signed variant inherits the same work tags. This prevents one volume of a long novel from being treated as a different subject from another volume.

Tag-driven loot selects a matching work uniformly first, then an enabled physical volume from that work. A 150-volume work is therefore not automatically 150 times more likely than a one-volume work.

Discovering available tags and work IDs

The generated build contains a machine-readable index at:

data/biblio/work_tags.json

Open the Biblio JAR as a ZIP and inspect this file when authoring a precise integration. Each entry contains the exact work ID, title, author, and tags for that build.

Because catalog tags are generated, an integration can automatically include future works that receive matching tags. Use exact works filters only for intentional exceptions.