Tenet

The modern questing engine for Fabric and NeoForge.

Build quest lines in a modern in-game editor, or describe them in JSON. Tenet draws them in a quest book, and the server decides what counts as done. It ships no quests of its own: it is an engine, not content.

Why Tenet

• An editor that does everything. The whole format in game: quests, tasks, rewards, conditions, chapters, reward tables, themes, with bulk-select and batch edits, undo per chapter, and deletes that come back.
• And plain files underneath. The editor writes the same JSON these docs describe: version-controlled, diffable, pack-friendly, with schema and validation, KubeJS scripting, per-language files, and open registries for addon mods.
• The server decides what counts. Progress is tracked server-side, so players can’t cheat quests complete by editing their own files.
• Broken files fail loudly and locally. The validator reports path and line and skips the file. One broken quest never takes the server down.
• Parties share progress. Built on Armature teams with ONE_MEMBER, POOLED, or OWNER_ONLY counting, server-authoritative throughout.

Playing

Install Tenet and Armature together, on client and server. The loader will name Armature if it is missing.

Open the book with the Quest Book item or the B key, and pin quests from the HUD. Details live in the manual:

• The quest book and HUD – canvas, claims, parties
• Commands – every /tenet command
• HUD – pinning quests and notices

Making quests

Most players never touch a file: press B and build quests in the in-game editor, with undo per chapter.

Underneath, it is all JSON: config/tenet/quests/, one folder per group, one file per quest, /tenet reload to apply. Everything a pack needs for version control:

• Manual front door
• Folder format
• Quest fields
• Tasks · Rewards · Conditions
• Validation · Languages · KubeJS · FTB mapping

Links

• Manual · Source · Issues