Using TDEconomy
Mod version shipped with FlammiCraft: 2.64.0
Prepared 2.64.0 requires matching protocol 62 client/server builds for the expanded quest API and larger catalog transfers. Tasks, personal series and Daily pools remain editable in game. See quest administration. The API is disabled by default; builds and source checks are not runtime acceptance.
For database storage on multiple backends, see cluster operation in 2.56.0, including account permissions, confirmed shop payments, queued quest progress and recovery checks.
TDEconomy manages money, accounts, shops, orders and quests. Amounts support two decimal places. The server owns balances, permissions and transactions. Install compatible server and client builds. This guide describes current sources rather than claiming acceptance on a running server.
Version 2.45.0 uses protocol 60; the previously deployed 2.39.0 release uses protocol 58. To upgrade, manually install matching 2.44.0 client/server builds and fully restart both sides. Supported shop records and drafts migrate step by step on a copy to schema 10, retaining storage mode for existing shops. The economy SavedData root schema is unchanged. Pack metadata supports Minecraft 1.21.1's resource and data formats. Builds and tests do not replace manual acceptance.
Requirements and upgrade (2.45.0)
FTB Quests and FTB Library integration is removed. Native quests remain available. Existing FTB quest files are preserved. Notifications display “TDEconomy” while preserving source IDs and archive/preference keys. MariaDB connections use TDLibrary 0.62.0 or newer.
Flammentaler and Funken
One Flammentaler equals 100 Funken. Enter 4.89 or 4,89 for four Flammentaler and 89 Funken in account, shop, order and quest amount fields. The English display reads 4.89 Flammentaler. Existing prices and rewards open with a comma in German editors. The former currency symbol and position settings no longer control the display. Existing whole amounts retain their value. A whole TOML amount such as 200 still means 200.00. Use quoted decimals, such as "0.01", for fractional settings.
Install matching client and server versions. Back up the stopped world, effective server configuration and local audit spool before testing a copy. Check existing balances, saved shop drafts, open orders and earned quest claims after two starts. Restoring the backup discards world activity after it was taken.
If an old order or shop price exceeds the supported range in Funken, the log identifies the record and price field. The original data is preserved. Use the log to check the world copy before reopening it.
Shops after removing a mod
If a saved offer references a missing item, a mob type required by its item filter or, for a mob shop, a missing datapack mob template (2.52.0), TDEconomy backs up the offer before removing it from the market. When the shop's chunk loads normally, TDEconomy backs up its sign data, deactivates the shop and removes its active index entry. The sign, its owner and attached storage remain in place. Select an available item in the shop editor and activate the shop again.
The server log gives the backup paths. The world's tdeconomy-shop-backups/ directory contains compressed NBT files for the original offer (-offer-) and the original sign data with its location (-sign-). A restart reuses existing backups when their contents match.
Start with accounts
The current main tab and administration subtab have TDLibrary's gold selection outline, requiring TDLibrary 0.48.0 or newer.
- Open the dashboard with
/money./tdeconomyexposes the same command tree. - Inspect your personal account and available funds. Reserved money can remain in the balance while being unavailable for other payments.
- Create a group account through the interface when you need a shared treasury. Required contract items and limits come from server settings.
- Grant members the specific rights they need; ownership, withdrawals, shop use and read access are separate decisions.
- Review the recipient, paying account and amount before confirming a transfer. Do not resubmit while its result is pending.
TDGroupe player groups and economy business accounts are separate systems. Linking them does not bypass action permissions. Archived accounts retain their data; accounts with balances or attached shops are not disposable records.
See accounts and player groups for the compact link view, approvals, and editing direct or linked group permissions.
Operators can change the group-owner limit in Create's in-game TDEconomy > server > Group Accounts settings. See group creation limits for value meanings, saving and manual acceptance steps.
Clear an account balance
- As an economy administrator, enable Admin mode and open Administration.
- Select the account under Players, Groups or System accounts.
- Choose Clear account, review its name and entire balance, then confirm.
This permanently destroys the money and sets the balance to zero. The account, members and shop links remain. Archiving is separate and still requires no money or shops. Archived accounts and source, sink or infinite system accounts cannot be cleared. Pending requests disable the button. If the balance changes, review and confirm the refreshed amount again. Release order reservations through normal completion or cancellation first; any reserved funds reject the entire clearing operation. The server rechecks permissions and state and audits the money decision.
After manually installing TDEconomy 2.44.0 and TDLibrary 0.48.0 or newer, fully restart client and server. Manually check the gold selections, confirmation and cancellation, successful clearing and rejection for reservations, changed balances or revoked admin mode. Automated tests and builds do not replace runtime acceptance. This change requires no new data migration.
Purchase counters
For a receiving chest emptied by an import bus, open Count mode: Storage in the sign editor and select Count mode: Purchased items. Set a total item target and inspect the current count. The counter survives normal saves, restarts and deactivation/reactivation. A confirmed reset starts another round only after saving in the sign editor. See the counter guide for initial counts, limits and manual acceptance.
Set up and use a shop
Shop owner, money account and storage mode are independent. An infinite system account does not make its attached storage infinite.
- Craft and place a shop board. Placement opens its initial editor.
- Set the traded item, quantity per trade, price, owner, account and storage mode. Provide stock or receiving capacity for a normal finite item shop.
- Save, then deliberately activate the shop. A saved inactive board does not trade.
- Check a complete trade from the customer's perspective, including direction, batch size, price and payment account.
- Use sneak-right-click to edit, and deactivate or change the shop through its supported editor.
Owners and storage-authorized players use normal right-click for attached storage and Alt-right-click to trade. Customers without storage access trade with normal right-click. Inactive boards open their editor only with sneak-right-click and never trade. The former standalone /shop root is no longer an operating entry point.
Group members and the group owner can sell goods to their group's buy shops, including shops paid by a system account. Money direction, available funds, item quantity and finite storage capacity still apply. Editing system-funded shops remains operator-only. See group-shop sales for retained trade restrictions and manual acceptance checks.
Missing stock, insufficient money, full destinations or changed terms must reject a transaction. If an outcome is unclear, refresh balances, stock and history before retrying; do not manufacture a second payment as a repair.
Identify shop goods with Jade
With optional Jade 15.10.6 or newer on the client, look at a shop board to see the actual item icon, name, Item mod and full Item ID, plus the batch price, quantity limits, stock and ownership. Free receiving capacity is hidden; storage-full warnings and purchase-counter progress remain visible. Buying and selling are phrased from your perspective as the customer. Both custom sign lines and the existing board/editor text size remain unchanged. See the Jade reference for controls, availability limits and manual acceptance. The integration needs no server-side Jade installation and does not change saved formats.
Find offers and review trade
Open /money market, narrow the item search and inspect buying/selling direction and availability. Check the actual shop again when you arrive; a market listing cannot guarantee unchanged stock.
Market boards and pillars open the same overview. Market daily statistics use UTC calendar days, unlike the Daily Quest boundary. Optional transaction history and audit storage help investigation but do not own balances.
Orders and quests
The order guide covers clipboards, posting, acceptance, delivery and collection. Saving a draft does not publish it. /money orders lists public requests, /money orders mine lists your involvement and /money orders previous opens older agreements.
The quest guide explains Daily and series signs. /money quests, /money daily and /quests are read-only journals. Acceptance, hand-in, focus changes and reward collection require the corresponding sign.
Administration and troubleshooting
Economy administration requires an actual OP-list entry or the singleplayer world owner. LAN guests do not inherit this access. Privileged operations may additionally require session admin mode: use /money adminmode on for the task, then off.
| Symptom | Check |
|---|---|
| Payment fails despite the displayed balance | Reservations, paying account, account mode and current permissions. |
| A board opens storage instead of trading | Storage-authorized players trade using Alt-right-click. |
| The quest journal cannot accept a task | Use the matching loaded sign within reach. |
| A request remains pending or reports overload | Wait for its outcome and refresh; do not submit duplicate payments. |
| History or the database is unavailable | Investigate economy state separately from audit storage. Do not clear SavedData or logs. |
Store the economy in the database (2.52.0)
In database mode, TDClaim sale signs can transfer a price from the buyer's personal account to a player, group or finite system account. Each payment commits with its unique receipt. TDClaim uses that receipt to finish a confirmed sale after a restart. Back up and restore the Minecraft world and the economy database together.
From 2.52.0 the shared economy can live in MariaDB instead of the world. This
works for a single dedicated server and for a cluster of backends sharing one
database. From 2.54.0 TDEconomy has no database setting of its own; the switch
in tdlibrary-database.toml decides:
[database] enabled = false(default) and in single-player worlds: everything stays in the world as before, without full transaction history.[database] enabled = trueon a dedicated server: balances, system and group accounts, daily payout totals, the shop index, market offers, quests and group invitations live in the database. Since 2.58.0, it also stores stock and order notifications, account notification preferences, first-join records and shop presets. The database also stores market statistics, trade quotas, order state and title entitlements. Shop signs, order crates and inventory recovery stay in the owning backend's world.- In the server-root
cluster-node.toml,idnames the server andowned_dimensionslists its dimensions. Empty means "every loaded dimension", the right setting for a single server. TDEconomy can distinguish separate worlds with the same dimension ID. World names and the market - Several backends also need the TDLibrary cluster: in
tdlibrary-database.tomlset[cluster] enabled = true. A single server needs no TDLibrary cluster. - The connection and
migration_conflictscome from[database]intdlibrary-database.toml; tables use thetdeconemy_prefix and are created on first start. The full transaction history lives intdeconomy_audit. All servers need the samestarting_funds.
On the first start in database mode the server backs up
data/tdeconomy_data.dat to tdeconomy-migration-backups/, validates the data,
transfers it in one transaction with a read-back check and rewrites the world
file without the moved parts. If entries differ from values already in the
database, the start stops (migration_conflicts = "REFUSE") or keeps the
database values ("KEEP_DATABASE"). A world without economy data joins without
a migration. A migrated world no longer starts in world mode.
While the database is unreachable the server refuses payments, purchases and quest actions as temporarily unavailable. Changes already made are written once the database returns. After a crash the server reverses bookings made since the last world save so money and goods stay consistent. If such a reversal needs an account another server currently holds, the starting server waits briefly for it. A quest action while another server holds the quest data reports that quest data is being saved; try again a moment later.
In a cluster:
- The dashboard lists players of every backend as online. Transfers and group invitations reach them on any backend; the invited player gets the chat hint where they are playing and can accept the invitation after changing backend.
- Transfer, shop and order notifications appear right away on the backend the recipient is playing on. Offline players find them in the TDLibrary inbox.
- The daily task selection, its Discord webhook and the daily quest board offer
run on one backend only, chosen by the TDLibrary cluster;
/tdlibrary clustershows which tasks this backend leads.
Group invitations from versions before 2.52.0 are imported once from
data/tdeconomy_group_invitations.dat; the file is kept as
tdeconomy_group_invitations.dat.imported. If it cannot be read, the server
does not start and the file stays unchanged.
A change the database refuses repeatedly while it is reachable is set aside in
tdeconomy-cluster-quarantine/ in the world folder and logged as an error, so
it cannot block later changes. Check that folder after such a message.
Commands for operators or the console:
/money cluster checkverifies without database access that the economy converts to the database format and back without loss. Chat shows the number of problems; the server log lists each one./money cluster test(world mode on a dedicated server only) runs the complete migration against the configured database in one transaction, compares and rolls back. Missing tables, the cluster record (which fixesstarting_funds) and this server's backend record remain. Use a test database no server is using./money cluster statusshows the storage mode, database state, waiting changes, leases, backends and bookings that could not be reversed./money cluster exportwrites the complete economy in world format totdeconomy-export/.
Testing on a single dedicated server with existing shops: copy the world, enter
a test database, run check and test in world mode, then stop, set
[database] enabled = true and start. Check accounts, groups, shops, the market and
quests, buy and pay, then restart (no second migration). Without shop data,
start a fresh world in database mode.
Back to world mode: /money cluster export, stop the server, replace
data/tdeconomy_data.dat with the export and set [database] enabled = false
(this applies to every TD mod on the server). A
database containing tables of the trial import of earlier development builds
(tdeconemy_ledger_schema) is refused; use a fresh test database. Never delete
tdeconemy_audit. The detailed reference and
docs/cluster-ledger.md in the source describe the procedure in more depth.
Back up the world and economy state together before upgrades. The current mod ID is tdeconomy; avoid maintaining conflicting legacy configuration names. See the detailed reference for additional settings, data rules and administrative workflows.