Tasks

Minecraft 1.21.1Fabric + NeoForgeTenet 0.2.0

A quest's tasks array is what it asks for. Every task must be satisfied unless it is marked optional — and if they are all optional, any single one of them satisfies the quest, because a quest where nothing at all is required would complete itself the instant it unlocked.

Every task object carries its type and that type's fields, flat at the same level:

{ "type": "tenet:item", "item": "minecraft:oak_log", "count": 8 }

A field that belongs to another type is accepted and ignored: the validator checks a task against every type's fields at once, so what it reports is a field no type declares — a typo like titl rather than a field belonging to the type next door. What each type actually reads is what the codec decides, and the list of what this build has — with every field each type takes — is also one command away:

/tenet types

Every task has these#

What a player has to do, and what just happens#

A task that takes nothing completes itself the moment its count is met: gather eight logs and the quest ticks over. A task that takes something waits for the player to press Submit, because the press is the consent to take it — an item task with consumeItems, an xp task, and a fluid task. A checkmark is nothing but the button.

Task ids are namespaced, so the built-ins live under tenet: and a mod's own type is its own id. The types below are the seventeen this build ships.

tenet:advancement#

tenet:biome#

tenet:checkmark#

The simplest way to say "read the sign", "talk to the NPC", "make the choice" — anything the game cannot see.

tenet:custom#

The handler answers how far along the player is, and the engine treats that answer exactly as it treats a stat's or a kill count's. Nothing outside a handler can advance a task, so a custom task is a measured task or it is nothing.

A tenet:custom task whose handler is not registered is not an error: the quest still loads and the validator warns that this build has nothing registered for the id — which is what a pack shipping a handler mod as an optional dependency wants to see.

tenet:dimension#

tenet:energy#

Hand over energy stored in carried items — batteries, capacitors, charged tools — read through the loader's energy access, which is also what a submit drains. FTB Quests fills this task by piping energy into a task screen block; Tenet has no such block, so this is the carried-container path. Fabric has no energy library to read through, so this task reads zero there until a TR-Energy integration ships.

tenet:fluid#

Carried in the buckets the player holds — a submit empties them and hands the empties back — and in anything else that holds fluid: tanks, capsules and canisters count through the loader's fluid access, which is also what a submit drains. FTB Quests fills this task at a task screen block; Tenet has no such block, so this is the carried-container path.

tenet:item#

components is how a task asks for a renamed sword rather than a plain one: a text component's value is a string holding JSON, as the codec writes it, and the editor writes that form when you pick a renamed item:

{
  "type": "tenet:item",
  "item": "minecraft:diamond_sword",
  "components": { "minecraft:custom_name": "\"Tempered Blade\"" }
}

An item this build does not have keeps its id and the quest still loads: the row draws a placeholder and says the item is missing, so a removed mod can come back.

tenet:item_tag#

A sibling of tenet:item rather than a field on it, so a tag where an id is expected is an error here as it is everywhere else.

tenet:filter#

FTB Quests has no tag field of its own: tags — and the mod, and, or and not combinators — arrive through filter stacks, an ftbfiltersystem:smart_filter item carrying the expression in its ftbfiltersystem:filter component. The migration tool passes that string through verbatim, so a converted pack reads the same vocabulary it was written in:

{
  "type": "tenet:filter",
  "filter": "or(item(minecraft:coal)item_tag(minecraft:coals))",
  "count": 4
}

A juxtaposition of forms at the top level reads as an implicit and, the same reading FTB's own parser gives it. Any function a "hand in N" task cannot answer (component, durability and friends) is refused with its name in the message, and the migration tool reports such tasks as manual work rather than emitting them. An item() id whose mod is not installed warns like any other missing item: the id is kept and the quest still loads.

tenet:kill#

With neither entity nor entityTypeTag, any mob counts.

tenet:location#

tenet:observation#

tenet:stage#

The read half of the same feature whose write half is a stage reward, a command, or a script: a pack grants a stage somewhere and asks about it here. Nothing is required of the id — a stage exists by being granted — so a typo shows up as a task that never completes rather than as a file that will not load.

tenet:stat#

tenet:structure#

The in-game editor's list of structures is the connected server's own, because a structure is worldgen data a client is never sent: a modded or datapack structure appears in the list once you have joined, and one added by a datapack reload arrives on the next join. The box also takes a typed id, so a structure the list has not offered yet is still settable.

tenet:xp#

Manual only, deliberately: experience is not something the engine should take the moment a player happens to be carrying enough — the Submit press is the consent, and the press takes it.