Daily quests and personal quest series
Mod version shipped with FlammiCraft: 2.64.0
Administration API in 2.56.0
With bind = "0.0.0.0", the API listens on all IPv4 interfaces and accepts any
source IP permitted by the host network. Every request still requires the
private key. The default remains 127.0.0.1; tools use the actual server address.
The API manages tasks, complete personal series, Daily pools and board flags in one reviewed atomic batch. Series support fixed/random positions, time limits and follow-up series. Active or restorable runs lock structural edits; retained runs also prevent deletion of their series. Player progress, earned claims and the frozen Daily cycle remain intact.
Large catalogs use revision-bound API pages and bounded ordered packets for the in-game editor. The editor opens only after complete assembly, with a logical response limit of 4,194,304 characters and reserved player-state headroom. Use matching protocol 62 builds; no storage migration is needed. See the API guide for fields, limits and manual acceptance. Source checks and builds do not enable or install a production API.
Daily quest board and personal quest series
Administrators can prepare issue-based task batches outside the game with the optional
private quest API and Python review/apply tool. The API is disabled
by default and uses database.quest_api in the excluded private
config/tdeconomy-database.toml. The private file is not synchronized to clients.
Before upgrading, preserve any effective world serverconfig/tdeconomy-database.toml
in the global config directory, retaining existing values and resolving conflicts
locally. Never put its keys into a distributable common config; see the
private configuration setup.
Imports create normal editable tasks, check live items/accounts and reject stale
catalog revisions. The in-game editor also provides confirmed task deletion, retaining
accepted terms and earned rewards. Series references must be removed first; deleting
a pooled task disables new Daily accepts until complete pools are enabled again.
A Daily Quest Sign (tdeconomy:daily_sign) always opens the Daily board with Daily offers and the player's Daily progress, hand-in and reward collection. An unbound Quest Series Sign (tdeconomy:quest_sign) opens personal series, their hand-in and series reward collection. Every operation checks the actual sign type on the server; changing a request cannot turn one sign into the other. Action focus remains a shared choice between the player's active Daily and series action tasks.
Both signs must remain loaded in the player's dimension and within eight blocks of the living player. Operators can mine either sign in Survival and receive one reusable sign item. Replacing it creates an unbound board; quest progress and earned rewards remain in economy SavedData. Existing block protection still applies, and signs retain explosion resistance and piston protection. Previously bound ordinary quest signs retain their existing screen and binding while placed. A Daily sign linked to a delivery series earlier now opens the Daily board; the stored link is ignored. The two registry IDs remain unchanged. /quests, /money daily and /tdeconomy daily open a read-only journal showing accepted tasks, missing materials, action progress, remaining time, action focus and open rewards. Acceptance, hand-in, collection and focus changes require a sign.
Reading the board
The top left shows where you are, for example Daily quests » Administration » New task. The remaining time runs at the top right. A task's colour shows its difficulty: bronze for easy, silver for medium, gold for hard.
On an accepted task, every goal has a mark in front of it: red means still missing, green means done. Below the goals there is exactly one main button: Collect reward, otherwise Hand in, otherwise Show items. When it is disabled, the reason is shown beside it, for example that goals marked red are missing or that action goals count automatically. Accepting and cancelling ask first and state the consequences. A quest series shows which task of the series is running.
When the board is not set up yet, players only see a short notice. Operators see the exact cause.
Daily cycle and series rules
Each quest day, from 06:00 Europe/Berlin until the next 06:00, every player sees the same three global offers: bronze easy, silver medium and gold hard. The day length follows the Berlin clock, including the 23-hour and 25-hour daylight-saving boundaries. A player accepts one of the three offers for that quest day. Progress and rewards remain personal. Cancel, failure, death, reconnecting, collecting the reward or using another sign does not open a second choice.
Each cycle contains exactly 60 tasks per difficulty, or 180 tasks in total, shuffled into three global decks. Today's three tasks stay in the remaining pools until the quest day ends. At the next 06:00, all three leave their pools regardless of whether anyone accepted them. No task repeats within that 60-day cycle. After 60 quest days, all three decks restart with a fresh shuffle. Offers survive reconnects and restarts. The cycle follows Berlin calendar quest days during downtime and while closed; returning selects only the current day without replaying past days.
Enabling Daily quests requires exactly 60 distinct valid tasks in each of the three difficulty pools. For example, 60 easy, 59 medium and 60 hard tasks cannot activate the system. Duplicates, missing tasks, wrong difficulties and finale tasks do not meet this requirement. An enabled catalog cannot be changed into an invalid pool configuration. The running cycle stores frozen task terms; valid catalog edits prepare the next cycle. Closed catalogs may be edited, but publication checks all three pools again. An accepted task still finishes under its original terms, and an earned reward stays collectible.
Player-prepared brewing batches retain their player and original quest attempt on the brewing stand through chunk unloads and server restarts. Matching bottle and ingredient data are checked before credit, changed or machine-only inputs do not acquire that attribution, and finishing consumes it once. A later accepted quest cannot receive credit from an older preparation.
A personal series is separate. One player has at most one active series run, which can proceed beside a daily quest. Each position is a fixed task or a draw from its theme and difficulty. A finale appears only on a position marked as the finale. Work time starts at accept and uses the position duration, otherwise the difficulty duration, otherwise the series default, such as 24 or 48 hours. The next task in a run can be accepted only after the previous one is complete and at least 24 hours after its accept. Once it is unlocked, the player has 24 hours to accept it. Missing that window, missing the work deadline or cancelling ends the current run and the next attempt starts at task 1. Completed earlier series, earned rewards and open claims remain, and the failed reservation is released once. The first accept of a series, a newly unlocked follow-up and an allowed new run have no starting window.
After a series, the editor chooses exactly one outcome: end the path, continue into one other series without accepting it automatically, or allow a manual new run. A series cannot point at itself, and a cycle such as A to B and back to A is rejected. The 24-hour gap between accepts also applies across a follow-up series. An active run protects its series structure, durations and ending against edits; its title may still change. Task definitions and item filters accepted earlier remain frozen.
Tasks may require a full hand-in, a show check that leaves the items in place, server-confirmed actions, or actions plus a hand-in. Action progress and item counts are separate. The same action advances only the Daily or series action task selected as the focus. The first active action task sets that focus; accepting a second active action task asks for a choice at the sign. Material-only tasks do not require an action focus. Later focus changes preserve both counts. Delivery, showing, cancellation and reward collection use the sign's own task type independently of action focus. A pure action task stores its reward claim when the last required action happens in time. Hand-in and show tasks must be completed at the matching sign before the deadline. The operator pool editor opens with the tasks already in that pool selected. Collection is a later all-or-nothing step: short inventory space leaves the whole claim open, with no drop and no partial payout. An open reward of the other type does not block collection at this sign.
Item requirements can compare the default item, a full template or listed variants. The editor can ignore individual data fields, nested fields and whole groups, or ignore all item data. Ignored data is skipped during the check only. The handed-in stack is consumed as it is. Filters are checked on the server and frozen at accept.
Rewards may be money, items or both, including fixed templates and one stored random roll. Card details show random candidates, quantities, weights and the repeat rule, along with actual template names and common item details such as enchantments. Registry-backed components such as enchanted-book enchantments are retained. Every possible reward result must fit into an empty 36-slot main inventory, including stack merging and the configured repeat rule. A finite paying account reserves the money at accept. Insufficient funds reject the accept. Cancel or failure releases that reservation once. Success keeps it with the claim until collection.
An operator correction requires a reason and stores the operator and time. Extending a deadline or acceptance window can also restore the latest automatically expired step after an outage. It retains progress and earlier earned claims and reacquires released finite funds before restoring an active task; insufficient funds leave the failed state unchanged. A successful replacement run discards that old recovery state. An explicit reset ends the current run. Neither correction pays a reward again.
Closing the board blocks new daily and series accepts while retaining completion and reward collection. Reopening the board does not require Daily activation; valid personal series remain usable when Daily pools are incomplete. Operator catalog edits are rejected before saving if the complete editor response would exceed the transport limit. Ordinary players receive offer and progress data without the operator catalog.
Deadlines continue while players are offline. The server expires overdue attempts and releases their unearned reservations without waiting for login. History cleanup retains the current global cycle, every outstanding reward and all pending inventory-recovery references. Completion and collection recovery store all 41 inventory slots, including armor and offhand. A legacy 36-slot board image requires its matching saved player marker; without that marker recovery stops rather than combining new main-inventory contents with old equipment. A later order or quest transaction supersedes older inventory recovery images together with its durable save, so an old image cannot undo a newer delivery or collection after a crash. Pure action completion saves its claim atomically; intermediate action counters use normal SavedData saving.
Creating tasks and series
As an operator, choose Edit at the sign. The list shows tasks with their difficulty and the notes in pool, not in pool or finale; the search field filters as you type. On Daily signs the top line shows how many of the 60 places in each pool are filled.
+ New task opens a single form. Required fields have a mark on the right: red is missing, green is done. Optional fields stay uncoloured. The bottom line states how many required fields are still open and which one comes first. Save stays disabled until every required field is done. The question mark beside a field explains it; keyboard focus shows the same text.
- Enter a title and, optionally, a description. The counter shows the remaining characters.
- Choose the difficulty.
- Add goals: + Deliver takes items away on completion, + Show only checks them, + Action counts deeds such as mining or defeating. For an item, choose the item and amount first, then whether a normal item is enough, whether it must match a sample item or whether its data does not matter. Every goal row has an amount field, Change and ×.
- Set the reward: money, fixed items, a random reward or a combination. As soon as an amount of money is entered, the account choice appears as a required field. Add random reward opens the list; each entry shows its chance, followed by the number of draws and whether the same item may come more than once.
- More options holds the theme for quest series and the finale switch. A finale task never enters the Daily pool; on Daily signs the form warns about this.
Wide windows show a preview of the quest slip on the right; narrow windows open it with Preview. Duplicate creates a copy. Leaving with unsaved changes asks first.
+ New series opens the series form: title, time per task (24 or 48 hours), an optional time per difficulty, what happens after the last task, and the task list. + Fixed task picks a task from the catalogue, + Random task adds a place with a difficulty and an optional theme; the row states how many tasks match. Arrows change the order and × removes a place.
When players are running a series, the list says so beside its name. The form explains the lock: until those runs end only the title can change, while tasks, times and the ending stay locked. Players see the reason on a locked series, for example that another series is already running, that it unlocks only after the series before it, or when the next start is possible.
Editing existing conditions
As an operator, choose Edit at the matching sign, open the task and choose Change on a goal row. The condition does not have to be removed first. Each field shows its current value in the selection details, with long values available in the tooltip.
- Actions expose type, target, dimension and quantity. Changing the type asks for a matching target and retains the quantity and dimension.
- Material conditions expose the item or item tag, quantity, delivery/show mode, data comparison and template. Replace data template captures a selected sample's data and selects template comparison. The separate Ignore all item data setting is retained.
- Edit data filters lists fields from the stored template and default item. Choose a sample for filter fields adds the actual fields of another sample without replacing the template. Selected filters remain visible even if their fields are absent from the sample. Toggle individual fields or groups and choose Done with filters. When Ignore all item data is enabled, individual filters take effect again after that switch is disabled.
- For item tags, Edit allowed item variants selects individual members. Allow all current members of this item tag explicitly removes that restriction. An empty individual selection does not silently allow every member.
Cancelling a selection dialog discards that dialog's new selection. Applied field changes remain in the task draft until Save persists the task on the server. Task identity, other conditions and untouched settings remain intact. Existing daily offers and previously accepted terms remain frozen.
Honey and honeycomb goals
Choose Harvest honey bottles or Harvest honeycomb as separate action types. Select the hive block or a matching block tag and an optional dimension. A glass bottle advances only the bottle goal; a tool supporting shears harvesting advances only the honeycomb goal. One successful harvest counts once, even when it produces three honeycomb items. Cancelled interactions and machine-only harvesting do not count.
The existing Harvest honey or honeycomb type remains available and accepts either tool. Existing definitions, accepted tasks, progress and claims are preserved. These quest fixes in 2.39.0 retain economy SavedData schema 22 and board schema 5. Matching protocol-60 client/server builds are required.
Delivery series removed
Since 2.56.0 the separate Daily delivery series no longer exist. A Daily sign always opens the Daily board, even when it was linked to a delivery series earlier. Stored delivery series, runs, receipts and corrections remain unchanged in the economy data but are no longer offered. Use quest series on a Quest Series Sign for multi-step paths.
Cluster progress (2.56.0)
Action progress in database mode is queued with a unique event ID, original attempt and event timestamp. The current quest writer applies it to the latest shared state and acknowledges it in the same commit. Duplicate events count once; events from a replaced attempt do not credit the new attempt. A saved queue survives an outage or sender restart. Progress can appear after a short synchronization delay. During a database outage, queued progress and reward collection remain separate; collection still requires a usable economy. See cluster recovery and manual acceptance.
Offer storage and manual acceptance
Since 2.56.0, unordered quest sets and maps use stable storage ordering. Identical data from another backend no longer requests repeated writes solely because its Java process enumerates collections differently. Pending quest changes are queued for publication before handing off the quest write lease, and expired local leases can be requested again. Rejected board saves keep the task or series draft open. If another server is saving quest data, wait briefly and choose Save again in the retained draft. The editor returns to the administration list only after a confirmed save. Do not reset quest files or lease tables.
Since 2.63.0, choosing Save in the task editor allows up to eight seconds for the cluster to hand off the write lease. When the lease becomes available, the server checks the original catalog revision again and saves if it still matches. The draft stays open if the wait times out or the catalog changes.
Manually install matching 2.56.0 builds on all backends and clients and restart them fully. Automated checks use only a local test database. Manual cluster acceptance remains pending: save a task on backend A, verify it on B and C, save an edit on B and reopen it on A. Also check that a rejected save retains the draft for retry.
The server durably saves each new daily offer and its cycle before displaying it. A failed write does not release the new offer. The board shows a red storage error; retry, and have an operator check world storage and the server log if the error persists. Do not reset quest files. Completing and collecting existing tasks remain separate from generating a new offer.
Source checks and automated tests do not establish in-game acceptance. After manually installing matching builds and fully restarting both sides, check:
- Open an offer, reconnect and restart the server normally; the cards must remain the same. Automated tests inject write failures through a fake writer; do not lock or corrupt production world files to reproduce that failure.
- Try both specific harvest goals and a combined goal at the same hive. Each tool must advance its specific goal and the combined goal only.
- Open an existing material condition with nested mod data. Change one filter, then its quantity and save. The template, other filters, hand-in mode and variants must remain intact. Cancel a filter dialog and check that its changes were discarded.
- Edit an existing action's target and dimension. An already accepted task must retain its old terms. Future accepts use the changed definition; Daily offers adopt it in the next cycle.
- Create a new task: check the red and green marks on required fields, the disabled Save, the account field appearing only after an amount of money, the preview in wide and narrow windows, and keyboard use with Tab, Enter and Escape.
- Open a Daily sign that was linked to a delivery series earlier; it must show the Daily board.