Rewards

Minecraft 1.21.1Fabric + NeoForgeTenet 0.2.0

Rewards are what a quest gives when it completes. They are separate from taskTaskOne thing a quest asks for — items, a kill count, a dimension reached. A quest has several; all of them must be done unless minRequired says otherwise.See also Rewards, evaluated once, and by default they wait for the player to claim them — the claim button on a finished quest's card, or the Rewards menu, which groups the whole book by chapter and collects at three levels: a Claim on one reward's row, Claim Chapter on a chapter's banner, and Claim all in the footer for everything the server is holding. Three toggles decide what the menu is showing — Ready to claim, Choices pending and Claimed — and the footer's sweep follows whichever is active, so a view of choices claims choices and a view of what you have already collected offers no sweep at all.

Each row reads across four columns: what the quest is, how far along it is, what it gives, and the button that takes it. A quest's rewards are listed in the details column whether or not its row is folded open, so a chapter can be read at a glance and unfolded only where something needs deciding.

{ "type": "tenet:item", "item": "minecraft:diamond", "count": 4 }

Every reward has these#

auto decides the moment the reward changes hands:

Turning it on for a whole chapter#

The fifty dirt-and-wood quests at the start of a pack should not be fifty clicks, and they should not be fifty settings either. A chapter turns auto-claim on once:

{ "id": "first_steps", "autoClaim": "enabled", "quests": [ ... ] }

and a quest that wants to differ says so for itself:

{ "id": "the_boss", "autoClaim": "disabled" }

The ladder, most specific first: a reward's own auto → the quest's autoClaim → the chapter's autoClaim → the pack's defaultAutoClaim in index.json → off. default at any level means "ask the level below".

Two things a mode can never override:

• A choice reward is never auto-granted. Its payout is the player's pick, so it stays outstanding and is offered the moment the quest is claimed — whatever auto says. A file that sets an automatic auto on a tenet:choice gets a warning saying so, because the setting would otherwise read as supported.
• A held team gets nothing. /tenet rewards block outranks every automatic mode; unblocking is the one moment it is released.

no_toast and invisible are the same silence under two names: both grant without a toast and both suppress the completion notice for that quest, so a chapter of starter quests does not announce itself fifty times. The words are borrowed from FTB Quests, which is why there are two of them.

While anything is still waiting, the player sees it in two places: a small badge on the quest's node with the number of rewards, and a count beside the chapter's row in the sidebar — The Shop (3) — which is where the eye goes first.

An operator can hold every automatic payout at once with /tenet rewards block, whatever individual rewards say, and release it with /tenet rewards unblock. The switch is stored in the team's progress rather than in a save, so it is a server-side decision and not up to the player being paid.

The types#

Simple rewards#

tenet:item#

tenet:command#

The escape hatch every pack reaches for, and the one reward whose reach is the whole server — so it runs through the server's own dispatcher with the player as the source.

The placeholders are FTB Quests' own, kept whole so a pack moved from it does not have to learn a second vocabulary for the same sentence:

An unknown brace-word is left as written rather than blanked: a command that says {player} to an operator reading the log is a one-second fix, and a command that silently loses the word is a mystery.

{
  "type": "tenet:command",
  "command": "say {p} finished {quest}",
  "permissionLevel": 2
}

Table rewards#

Four types share one shape: tenet:random, tenet:loot, tenet:all_table and tenet:choice. The type is the mode; a file cannot turn a random into a choice by adding a field.

Both are optional and the reward rolls one table or the other, never both; a reward carrying neither rolls nothing. The type is still the mode — a file cannot turn a random into a choice by adding a field.

random, loot and all_table resolve the moment the reward is granted. choice cannot — the player picks — so the claim marks nothing until it is answered, which also means a crash between the offer and the pick loses nothing.

Writing a table#

A table is a list of entries, each an ordinary reward with a weight:

{
  "lootSize": 2,
  "emptyWeight": 10,
  "entries": [
    { "weight": 0, "reward": { "type": "tenet:item", "item": "minecraft:bread", "count": 4 } },
    { "weight": 3, "reward": { "type": "tenet:item", "item": "minecraft:iron_ingot", "count": 8 } },
    { "weight": 1, "reward": { "type": "tenet:xp", "amount": 30 } }
  ]
}

An absent icon is not a blank row: the editor draws the first entry that has an item, so a table of ore drops shows an ore rather than the chest every table reward type carries. A table of experience or commands — entries with no item of their own — falls back to that entry's type icon, and an empty table to paper.

A weight is how much of the table's probability space an entry takes; its chance is its weight over the total. A weight of zero means always granted — once per roll call — which is how a table says "and everyone also gets this", so the guaranteed entry lands even when the fashionable one misses.

A table that does not resolve — a typo in table, or a file that failed validation — logs a warning once and grants nothing. That is an author's mistake, not a crash.

Editing a table in game#

Nothing above has to be typed. A tenet:random, tenet:loot, tenet:all_table or tenet:choice reward's Table field is a card: it shows the table's icon, its name and its entry count, and it opens two panels.

The browser (Click to select or create a table) lists every table the pack has, searchable by name or id, with Edit, Copy and × on each row and one button that makes one. × sets the file aside, and refuses while any reward or table still names it — the refusal lists the referrers, so the author can go and look:

• New table — a file under reward_tables/, with the name you give it.
• None — clears the field, so the reward rolls no table.

A table written inside a reward — the format's own inline shape — still reads and still rolls, but the panels no longer make one: a table lives in a file under reward_tables/ and nowhere else, so there is one way to make one and one place to look. A reward holding an inline table shows it as what it is, without an edit path into it.

The editor (the Edit chip) is the table itself:

Filling a container from a table is a command rather than a button, because it needs the crosshair and a screen captures the mouse: /tenet table export <id>. Reading one is a button above — the panel's Import... › From target chest row — and /tenet table import <id> is the same read for a player who is walking around. See commands.