Tenet documentation

Minecraft 1.21.1Fabric + NeoForgeTenet 0.2.0

Tenet is a questing engine for Minecraft 1.21.1, on Fabric and NeoForge. A pack author describes a questQuestOne objective with a title, an icon, a position on the canvas, and the tasks that complete it. The unit a player sees and ticks off. line in JSON, Tenet draws it on a pannable canvasCanvasThe pannable, zoomable surface quests are drawn on. A quest's x/y are its position on it, in canvas pixels., and the server decides what counts as done — the client renders what it is told and nothing more, so no player can complete a quest by editing their own game.

What it needs#

Tenet ships no questlines of its own. It is an engine, and installing it does not put somebody else's content in your config; the worked questline lives in the repository under tools/quests/, as authoring material for a pack's first chapter.

Where to start#

For addon mods#

Quests name their types by id, and the set is open: a mod registers its own task, reward and condition types with TaskTypes.register, RewardTypes.register and ConditionTypes.register, each pairing an id with the codec that reads it. A tenet:custom task or reward needs no new type at all — it names a handler id, and the handler is registered by a mod or a script (see KubeJS scripting). The lifecycle — quests starting and completing, tasks satisfied, rewards handed over, stages granted and taken, canvas presses — is published as TenetEvents for both. An economy mod pays tenet:currency rewards by setting a CurrencyReward.CurrencyProvider with CurrencyReward.CurrencyProviders.setActive.

From files to a running questline#

/tenet reload

The book, briefly#

A player opens the quest book from the Quest Book item or the B key. It is a pannable, zoomable canvas of nodes: a quest's x/y is its place, its shape, size, rotation and icon are all authored, and the lines between nodes are its dependencies. From a quest's card a player submits tasks, claims rewardRewardWhat a quest gives on completion: items, experience, a command, or a loot crate. Separate from tasks, and evaluated only once.See also Tasks, and picks between a choice reward's entries. A player in a party sees the roster there too, and the counts the party's mode combines.

An operator gets a band of five controls under the title row — Author, Assets, ✎ Edit, Advanced and Preview — and the header itself carries no authoring control. Author latches the author's dock, which is where the Book and Chapter tabs live; Assets opens the pack's own files; Edit latches edit mode and nothing else; and Advanced says how much of the editor to show. Preview shows the player's view: the panel shrinks to the reader's card at the reader's size, hidden chapters and quests are hidden again, editing is paused, and quest cards show what a player would see — while edit mode stays on underneath, so leaving the preview resumes exactly where it was left. The way back out is the lit Preview pill floating over the canvas's top-right corner, since the reader's card has no author band to press. With Advanced off — the default — every menu carries the essentials: a quest's shape, size, placement, what it needs and what it gives, the text on a task and a reward, a chapter's name and quest list, and the book's own name and icon. With it on, every field, section and menu the editor has is drawn as well, which is where the reward tables, the visibility and progression rules, a chapter's line styles, the conditions and the theme editor live. That is the in-game editor, and it writes the same files these pages describe: the server re-checks the permission and validates before anything lands on disk, so no quest file is written by the client — the player's own look and text size live in files the client owns.

Removing something, and getting it back#

Every control that takes something away asks twice. The quest card's Delete, the node and dependency menus, the chapter and group menus, an entry's ×, the table browser's ×, the Assets panel's × and the Delete key all arm on the first press and act on the second, and the ones that remove a whole chapter or group say what goes with it — Really delete? (70 quests, 3 dependent) — before they do. Nothing is erased when they act: a quest file is renamed to <name>.json.deleted, a chapter's or a group's whole folder becomes <name>.deleted, and a reward table becomes <name>.json.deleted. The loader skips that suffix everywhere, so a pack with removed content in it still loads.

Ctrl+Z takes it back, and the restore is one history step per chapter — the same key as any other edit. A table delete is the exception: it is not on that trail, and the pair below is how it comes back. The history is the server's, though, so it does not survive a restart, and /tenet reload drops it on purpose; after sixty further edits in that chapter the step has fallen off the end. The copy on disk survives all three, which is what makes the pair below the way back:

Neither is offered in the book, because a tombstone is skipped by every walk the editor draws from: the tree genuinely does not know it is there, and a panel that listed things the tree cannot see would be a second opinion about the pack. Both take permission level 2, like reload.