Zum Hauptinhalt springen

Accounts, shops and recovery reference

Mit FlammiCraft ausgelieferte Mod-Version: 2.64.0

Diese Detailseite ist derzeit auf Englisch verfügbar.

Handbook overview

Group creation limits

With Create installed, open its settings menu, select TDEconomy, then server and Group Accounts. As an operator with permission level 2 or higher, unlock server editing, change Max Owned Group Accounts, and apply the change with Create's save control. The server checks the updated limit on the next creation attempt; changing this value does not require another world/server restart.

The default is 1 active owned account per player. 2 allows an admin-shop group plus one other owned group; 5 allows five total. 0 prevents new group creation and does not mean unlimited. An admin-shop group counts like any other owned group. Max Group Memberships is separate and counts direct memberships in other players' groups, not ownership. Each successful creation still consumes the configured contract items. Raising or lowering the limit does not remove existing groups, move balances or change shop links; a player at or above the new limit cannot create another group. Archived groups do not count.

Gameplay settings remain in tdeconomy-server.toml, at server.Server.group_accounts.max_owned_group_accounts. Create selects that configuration for both its server menu and incoming save requests. The separate config/tdeconomy-database.toml is private and uses NeoForge's unsynchronized COMMON loader type with its explicit filename. It no longer replaces gameplay settings in that server menu, and its secrets are not sent to connecting clients. Before upgrading, preserve an effective old world serverconfig/tdeconomy-database.toml in the global config directory. Retain existing history, database and webhook values; resolve conflicting files locally without exposing secrets. API settings belong in database.quest_api in this excluded file, never in tdeconomy-common.toml. The quest API guide describes the upgrade and key rotation. No database operation or live configuration change is performed by a source build.

Install matching updated client/server builds and fully restart both sides once to load the menu fix. Source and regression checks cover config selection and increasing the owner limit after one group already exists. Runtime acceptance remains manual: apply a higher limit in Create, create another group through the dashboard, and check that the original group and its shops remain usable. Reopen the settings after a later server restart to verify that the chosen value persists.

Identify shop goods with Jade

Install optional Jade 15.10.6 or newer on the client and look at a shop board. Enable Jade's overlay and the TDEconomy Shop goods and trade terms entry if they have been disabled. No keypress, editor access, advanced tooltips or server-side Jade installation is needed for these lines. TDEconomy still requires matching compatible client/server builds. Jade is a separate optional mod and is not bundled into TDEconomy.

An active item shop shows the traded item as its icon, its item name, an explicit Item mod label and the complete Item ID, even when advanced tooltips are disabled. Jade's ordinary block footer may still say TDEconomy; Item mod is the origin of the goods, not the mod that owns the shop board. If no mod name can be resolved, the item's namespace identifies its origin.

The offer uses the customer's perspective: Sell 32 items for 9 Flammentaler means the shop buys those items from you; Buy 32 items for 9 Flammentaler means you buy from the shop. The displayed price is for that batch, including variable-quantity shops. Their extra quantity line states the configured range or storage-dependent limit; larger selections cost a corresponding multiple of the base price. Finite selling shops show stock. Free receiving capacity is hidden for buying shops; purchase counters and warnings when less than one batch is available remain visible. Infinite storage is labelled explicitly. The tooltip also identifies the owner or owning group. Mob shops show their template ID and purchase price instead of inventing an item ID. Inactive boards show no active trade offer.

The integration reads only the public shop display already synchronized to the client, including the displayed market price. It does not query account balances, expose storage inventories, add server requests or change transaction permission checks. Availability is a display snapshot; the server rechecks the actual trade. Both custom text lines remain fully available, and the board/editor layout and font sizes are unchanged. There is no new saved format or data migration.

Source tests cover equal item names with different mod labels and IDs, German and English customer directions, hidden free receiving capacity, quantity ranges, infinite storage, inactive boards, mob templates and preservation of both custom lines. After manually installing matching TDEconomy builds and restarting both sides, check two identically named items from different mods with Jade enabled. Verify the item icon, mod and full ID, then check both trade directions, stock changes, storage-full warnings, hidden free receiving capacity and variable quantities. Fill both custom lines completely and inspect the board and editor at normal and small GUI scales. Also start a client without Jade and verify that ordinary shop interaction still works. Automated checks and a successful build are not in-game acceptance.

Selling to your group's shop

Group members and the group owner can sell items to a group-owned buy shop, including one funded by a system account. Trading does not require shop editing or storage permission. Use Alt-right-click if normal right-click opens the attached storage; otherwise use normal right-click. The selected receiving account still requires deposit access, and system-account mode, available funds, item quantity and finite storage capacity are checked before payment. Editing a system-funded shop remains operator-only.

Members with storage extraction access can take goods out and sell them again; source and infinite accounts can pay repeatedly without spending a reserve. Review storage permissions when choosing this ownership and funding setup.

The existing restrictions on buying from your group's system-funded sell shops and trading with your personally owned system-funded shops remain in place. This sale fix changes no stored formats and requires no account or shop migration.

Source regression tests reproduce the former rejection and check sales by both a member and the group owner with finite, source and infinite system accounts, including exact payment, item movement and both storage modes. After manually installing matching builds and fully restarting client and server, sell a known quantity as each player and verify the receiving balance and shop stock. Repeat with a full finite storage and an underfunded finite account; rejection must leave items and balances unchanged. Automated tests are not in-game acceptance.

Permission error messages

An error names the requirement that failed for the current board and action. It does not list every role that might manage some other board.

Message or situation Meaning and next step
Another player's board Ask that board's owner to make the change. Access to its payment account does not make you its owner.
No access to the owning group Ask the group account owner for access. Direct membership and effective linked player-group access are both considered.
Missing group editor access At least one of Edit group shops, Deactivate group shops, or View account and shop history opens the editor. Only the granted actions are available. Storage permission alone does not open it.
Missing editing, deactivation, history or storage right Ask the group account owner for that specific permission. None of these permissions automatically grants another.
Group account ownership required Transferring ownership, dismantling group boards or changing an unconfigured group board's frame requires the group account owner. Ordinary member shop rights do not grant those actions.
Locked, mob, infinite-storage or server-owned shop Management requires an economy administrator with active admin mode, even for the personal or group owner.
System-funded shop Editing, deactivation and editor statistics require administrator bypass. System funding alone does not remove ordinary storage access.
Linked account access The existing payment account must still be usable by the actor. Selecting a new group account additionally requires Link the group account to shops.
Admin mode is off A recognized administrator can run /money adminmode on, repeat the action, then turn it off with /money adminmode off. Ordinary group members do not need admin mode for their granted actions.
Shop creation level The error gives the configured Minecraft permission level for creating or activating an inactive shop. Ask a server operator to check that setting.
Ownership target unavailable Reopen the editor and select a currently eligible player or active accessible group. This is separate from permission over the current owner.

Group invitations, member removal and renaming name their individual required permission. Group ownership transfer and archival remain owner actions. Quest-board material changes require an operator or the singleplayer world owner; they do not use group-shop permissions or require admin mode. Notice boards also use placer/operator rights, independently of group-shop rights. Their save replies separate ownership, spectator mode, world/claim protection, an unavailable board, stale content and invalid formatting. Market pillar replies separate ownership, admin mode, world protection and unavailable targets. An order box with an invalid assignment reports that state before ownership; ordinary group boxes require the assigned group account owner for dismantling. Existing contents and active orders can still prevent dismantling after ownership is accepted.

The history window separately reports a disabled backend, missing history rights, an unresolved shop index identity, or a history-service failure. A permission failure is not evidence of database failure. Invalid shop claims and unreadable shop markers likewise keep their identity/data error instead of blaming the user.

Player-group link errors distinguish the business-account owner from the player-group owner. Requests and role-permission changes require the account owner. Either current owner can approve their own side or unlink the connection. The player-group management view requires that player group's owner. Member shop permissions do not replace these ownership requirements.

Rejected direct-member permission saves identify a stale revision, unavailable account, invalid selection, removed member, fixed owner profile, missing permission management rights, self-escalation or an attempt to grant permission management without account ownership. A stale revision is not an authorization failure. Rejected changes remain a draft while the selected account and member remain available in the view.

Install matching 2.44.0 / protocol 60 client/server builds manually and fully restart both sides. These message changes add no saved format or migration and do not enable history or change permissions. Source tests cover the shop denial matrix, independent action grants and history/notice response round trips; in-game acceptance remains manual. Check a personal foreign board, a group member with one right at a time, an account whose access was revoked, each protected shop mode, and an administrator with admin mode off and on. Revoke permissions while an editor is open. Check market/notice targets outside reach and under world protection, an invalid order-box assignment, and history with a disabled backend versus missing permission and an unavailable service. Check German and English at small GUI sizes. Use a test world; do not damage production data to create an invalid-state test.

Admin-mode sessions and button feedback

Admin mode belongs to the current network connection. Every login starts with it off, including reconnects after a lost connection. Elevation cannot transfer to another connection with the same player UUID when logout cleanup is missed. Login and server startup clear previous state; logout and shutdown also clear it. Order authorization uses the actor's current online connection. Menu changes within the same connection do not disable admin mode; use the button or /money adminmode off to end it deliberately.

The dashboard's admin-mode button text is green while enabled and white while disabled, following the server-confirmed snapshot. TDEconomy buttons no longer use the additional white hover frame. Pressed feedback, gold selected-tab outlines, gold keyboard focus and Tab/Shift-Tab/Enter/Space operation remain.

Source regression tests cover reconnecting without logout cleanup, rejecting the old connection after reactivation, late cleanup of an old connection, lifecycle resets, button text colors and independent hover/selection/pressed states. Manually install matching 2.44.0 / protocol 60 client/server builds and restart both. Enable admin mode and check green text, log out normally, reconnect and verify that it is off. In a test environment, repeat with connection loss, wait for the server to detect disconnection, then reconnect and check again. Within one connection, check menu changes, respawn, dimension changes and explicit disable/enable. Verify the frame change with mouse and keyboard at normal and small GUI sizes. Actual connection loss and rendered feedback remain manual acceptance steps. No saved format, account balance or shop data changes.

Individual group permissions

In the dashboard, select a group and choose Permissions. The group access guide describes member selection, switches, saving and unsaved-change protection. Each member has one profile for all of the group's eligible shops and actions. The owner can restore the default profile. Operators with active admin mode can use the same menu in group administration.

Existing groups and new members keep the previous permissions by default: balance and history access, deposits, spending, account linking, ordinary group-shop editing and deactivation, storage access and stock warnings. Inviting or removing members, renaming the group and managing permissions are off by default. The four group-order permissions are enabled by default; their use in bilateral group orders belongs to the separate order implementation.

Shop storage permission allows opening, inserting and extracting items without granting editing, spending, deactivation or infrastructure removal. Editing does not grant storage access. Rights apply to group-owned shops; linking the group's money account to somebody else's personal shop does not grant ownership rights. Automation retains its existing rules. Locked shops, mob shops, infinite storage and system-account changes keep their operator restrictions.

For an ordinary group-owned sign, use Shift-right-click with an empty hand or Shop management > Open editor. The server checks the member's individual rights, including effective linked player-group rights. Edit shops allows changing and saving the shop. Deactivate shops independently allows deactivation; View history independently allows statistics. With only either of the latter permissions, the editor's fields and save controls remain disabled and only the permitted action is available. Editing does not grant deactivation, history or storage access. Changing the payment account still requires linking permission, and members cannot transfer shop ownership. Rights are checked again on every submitted action, so revoking a right also blocks an already open editor.

In Administration > System accounts, selection and history share the top row. Balance, linked shops and active/archive status have their own text area; rename and balance edits sit below it, followed by account mode and archiving. New-account creation is separate below those controls. Small GUI sizes use shorter rows with history beside the balance area. Help remains available through tooltips. Pending requests block duplicate submissions.

Source tests cover individual shop rights, revocation, packet flags and disabled editor controls. After manually installing matching protocol 60 builds and fully restarting client and server, check a finite group-owned shop as a non-owner: grant only editing and save changed text/price; grant only deactivation and deactivate; grant only history and open statistics; grant only storage and open the container. Revoke each right while its screen is open and verify rejection. Also check system-account administration at normal and small GUI scales, including an archived account and a newly created account. Automated checks are not gameplay acceptance. Existing balances, membership profiles and shops need no new migration for these permission and layout fixes.

The owner retains every permission. Delegated permission managers can edit other members but cannot grant permission management, change the owner's rights or expand their own profile. Owner transfer and group dissolution remain owner/operator actions. Former owners become ordinary members with default permissions; a promoted owner receives full rights. Removing a member discards their custom profile, so rejoining starts with the defaults.

Saves carry the group's revision and reject stale or repeated requests. Every money movement, shop mutation, history reply and storage opening checks current server permissions again. Permission or membership changes close affected open shop inventories immediately using Minecraft's normal cursor-item return path. Both halves of a double chest are protected. A copied world should be used for migration and revocation acceptance; see the manual checklist.

SavedData rejects nonempty economy lists with incorrect element types, including nested membership and quota lists, instead of treating them as empty.

SavedData schema 22 migrates supported earlier schemas on a copy and preserves existing group defaults and balances. Invalid permission records fail closed. Network protocol 60 requires matching client and server builds. Buying from a shop with a group account requires spending permission; selling items into that account requires deposit permission. Every shop purchase opens the confirmation dialog with a payment account selector, regardless of price. Operators also see active system accounts that allow outgoing payments; archived and sink accounts are excluded. Source and infinite accounts show unlimited spending capacity. The server rechecks current operator rights, group permissions, account status and payment direction before charging the selected account. The expensive-buy threshold no longer skips this account selection. Agreement revisions use the server-checked contract side independently of the current account-selection page.

Shop selection in the shop dashboard and All shops admin view searches the entire accessible server index, including shops in unloaded chunks. Select Owner, Account, Coordinates or Item above the search field to search a specific property. All combines words across the shop name, owner, payment account, item, dimension, coordinates and index status; for example, Flammichen boots finds that owner's boots shops. Names are case-insensitive and partial names work. Coordinates accepts exact X Z or X Y Z, separated by spaces or commas, for example 114 -1742 or 114 44 -1742. Clear the field to remove the search. Results update while typing and paging stays within the matching shops. Searching does not load chunks or modify shop or account data; administrative access still requires the existing operator and admin-mode checks.

In All shops, Delete shop opens a confirmation with the exact dimension and coordinates. An operator with admin mode can permanently remove the selected shop sign, including unreadable active records and drafts, and clear the index and claim at that location. A stale index whose sign is already missing can also be removed. Other blocks at that location, attached containers, stored items, accounts, balances and shops at other locations are preserved. An existing sign returns to the admin's main inventory as one plain shop-sign item, matching the normal block drop without shop data or cosmetic material. If there is no room, deletion stops without changing the sign or its index. A missing sign grants no item and its stale index can still be removed with a full inventory. Item delivery and deletion roll back together if execution fails. If restoring the inventory itself fails or leaves the returned item in place, the world sign is not recreated; the server logs the failure and the remaining stale index can be cleaned without issuing another item. A newer index, a different active claim or a different readable sign identity protects a replacement shop at the same location, even if the rest of its record cannot be decoded. Shared offers and trade quotas remain while another indexed location uses the same shop ID. The area must already be loaded; the action does not force-load chunks. A changed index, changed shop revision or a different valid shop at the location rejects deletion and asks for a fresh selection. The server confirms success and refreshes the shop list. This operation is separate from Deactivate, which retains an editable draft.

Transaction recovery and history

An existing economy or group-invitation file that cannot be loaded blocks access to that data. The server logs the load failure and preserves the original file; it does not create an empty replacement. Repair the file or restore a verified backup with the server stopped before trying again. A genuinely missing file still initializes normally, and the documented handling of recognized unsupported legacy schemas remains unchanged.

Mob-shop insertion exceptions are logged and checked against the actual entity in the destination level. If the prepared entity is absent, the payment is refunded. If it was already added, the purchase remains paid and consumes its normal allowance.

Existing-account balance reads do not mark economy data as changed. New accounts and money changes still persist; notification export retains its existing durable save boundary.

Item-shop trades validate the type, item data, and quantity actually extracted. If an inventory handler throws during execution, the server compensates the payment and recovers moved items, including observable slot changes made before the exception. Inventory handlers must expose their slot contents and support normal insertion and extraction for a complete rollback. Items that cannot be reinserted are given back to the player or dropped; an incomplete inventory or payment rollback is reported as an error requiring administrator attention.

History access is checked when a query starts and again when its result is sent. Losing group access, transferring a shop, or disabling admin mode prevents a pending result from exposing entries. Mob-purchase history records the acting player separately from the personal or group account used for payment.

Audit database writes and JSONL spooling run on background workers. When the database queue fills, events remain queued for the spool worker without blocking the server thread. The spool backlog is not capped by the database queue capacity; reaching that capacity triggers a warning rather than discarding events. Disk write failures are retried. If the disk remains unavailable, the backlog consumes memory until writes recover. Events still in memory are not durable across a process crash, and shutdown warns if the spool worker cannot finish in time. Restore disk access promptly when backlog warnings appear.

An audit_close_timeout_millis value of zero skips waiting for audit workers during shutdown. Positive values bound each worker wait; a zero value can leave events in memory when the process exits.

Local audit segments rotate between complete append batches at an 8 MiB or 4,096-event target. An oversized batch remains intact and is sealed before the next batch; append success still requires force(true). Restart seals abandoned active files and preserves quarantined segments. A partial disk write can leave a malformed tail, causing the entire segment to be quarantined for inspection. Replay logs the number of newly quarantined segments and their spool directory; their events require manual recovery even if the disk warning threshold has not been reached. Quarantine files remain included in the configured disk warning threshold.

Replay validates an entire sealed segment before delivering any of its records, then delivers at most 100 events per batch with a 1 MiB encoded payload target. Valid oversized records are delivered individually with a generic warning. The largest historical record and append batch still determine additional memory use; these targets are not a fixed heap ceiling. A segment is deleted only after all batches succeed. Failed writes or deletions retain it for retry with the same event IDs, which MariaDB deduplicates. Replay does not repeat economic operations. Ordering is preserved within segments; the normal and overflow queues do not guarantee a shared global delivery order.

Retained bytes are tracked under the spool lock and reconciled every 60 seconds on a background size check, or after uncertain file operations. A size-check failure warns without requeuing a successfully appended batch. The spool directory has one process owner: do not edit its files while the service is running. Replay does not hold the append lock while reading or writing to the database. These changes leave the unbounded overflow queue and shutdown timeout behavior described above in place.

Purchase counters and total targets

Finite item buying shops support Count mode: Purchased items. The button is disabled and greyed out when unavailable, including infinite-storage shops. Its state updates immediately when opening the editor or changing trade/storage modes. Existing counters remain accessible for management. Open the count mode button in the sign editor, switch from Storage, and enter a positive Total target in individual items. A target of 4000 granite applies to all sellers together, independently of the maximum amount per trade and each customer's rolling quota. The editor displays the count captured when opened; the counter screen also displays remaining demand. The initial setup can seed the count with an explicitly entered amount already delivered to the central store. Neither old transactions nor the central inventory are scanned to infer it.

Apply updates the editor draft; Save or Activate in the sign editor persists it. Each successful sale adds the actual item amount. Import buses, hoppers and manual extraction do not decrease it. At the target, further sales are denied. Variable selections are capped at the remaining target in whole trade bundles. If the remainder cannot fit a minimum bundle, the target is complete for trading. Real receiving capacity and funds still apply. Failed trades and rolled-back transfers do not advance the count; failure to save the counter rolls back the trade. Boards show progress in place of their inventory number. Jade and trade confirmations show remaining demand, and completing a target does not raise an incorrect full-storage warning.

Choose Reset counter, confirm, Apply, then Save in the sign editor to start a new round at zero with the same target. Goods, balances and lifetime statistics remain intact. Cancel discards the staged reset. Editing, mode changes, deactivation/reactivation and normal save/restart cycles retain the counter. Once configured, successful purchases continue counting in storage mode, so switching modes does not silently clear procurement history. Changing the item or its matching rules requires an explicit reset. If another trade changes the shop while editing, reopen the editor for a fresh count before saving. Newly placed preset shops use their usual storage mode and start without this counter; configure their procurement target separately.

Supported shop records and drafts migrate from schema 9 to 10 through the existing explicit migration chain, preserving identities and ordinary storage mode. Invalid current counters and unsupported versions fail closed. Economy SavedData's root schema is unchanged. Protocol 59 requires matching client and server builds and a full restart after manual installation.

For manual acceptance, sell through two players, empty the receiving inventory with an import bus, save and restart, then verify that the remaining demand did not increase. Reach the target, attempt an oversized and an old open-dialog sale, then check deactivation/reactivation. Test both saving and cancelling a reset, rights revoked while editing, a full receiving chest and insufficient funds. Source checks and automated serialization/rollback tests do not establish live Minecraft or import-bus acceptance.

Market, shop statistics and stock alerts

/money and /tdeconomy keep their existing dashboard and identical command trees. Open Market in the personal dashboard or use /money market to search active item-shop offers by item ID, server-side item name, shop name or owner. Each offer shows its buy/sell direction, minimum batch, batch price and location. Listings for unloaded chunks are cached offers, with unconfirmed availability; the search never loads chunks. Existing shops enter the catalog when their chunks next load. Locked, conflicting and unusable-account shops are excluded. Tenure and quota restrictions still apply when a player actually trades.

The shop editors' Statistics button shows revenue, purchase spending, sold/bought quantities and the five buyers ranked by spending. Counters start with this version, count successful transactions only, and live in SavedData, independently of MariaDB. Editing a shop keeps its statistics; a new shop identity starts new counters. Deactivation and reactivation of an existing item-shop draft keep its identity and counters. Both item and mob transactions are counted.

Loaded shop signs reconcile on their existing position-staggered 20-tick schedule. A completed inventory refresh during that reconciliation replaces the duplicate periodic refresh. Trades, repairs and price changes still refresh immediately, including further changes in the same tick. Stock scans read captured-mob template data once per scan and read each candidate's current components; display results are never used to authorize a transaction. Unchanged claims retain their saved data without marking the sign dirty, while identity and ownership checks continue.

Finite shops persist a warning episode when observed matching stock (selling) or free capacity (buying) is below one minimum batch, including on the first observation after loading. Repeated checks do not create additional warnings. The warning rearms only after an observed recovery. Hopper and manual inventory changes are included. Recipients follow the shop owner, independently of its money account: personal owners, group members with Stock warnings permission, and listed operators for server-owned shops. Recipients are captured at the time of the event, including offline players; later members do not inherit it.

The personal dashboard's Notifications button opens a paginated list. Select an entry to view its affected shop, location, timestamps and current status. Loaded shops are checked before showing the list or login summary; unloaded or unverifiable active shops are explicitly marked unconfirmed. No chunks are loaded for notifications. Resolved stock problems remain marked as history; removed, deactivated or transferred shops do not request refilling. Converting an item shop to a mob shop also resolves its old storage warning. Offline operator recipients are captured using the UUIDs in the OP list without performing profile-name lookups. Resolved warnings and order updates remain for 30 days after their last change; active warnings remain until resolved or removed.

Login and online updates use one bounded chat summary rather than one chat line per event. The client acknowledges that summary only after adding it to chat. Episode IDs and persisted display acknowledgements suppress repeats; an unacknowledged summary can be retried after reconnecting. This is at-least-once delivery, not an exactly-once guarantee. Lists and summaries have no gameplay quota and do not silently discard excess warnings. Current rights are checked for every list, detail and acknowledgement. Removed members and revoked rights lose the affected old notifications even if permissions are later restored.

Optional dynamic system-shop prices

Dynamic prices are disabled by default. An operator looking at an active item shop linked to a system account can run:

/money pricing on <minimum> <maximum> <step> <items_per_step>
/money pricing off

Minimum, maximum and price step accept Flammentaler amounts down to one Funke (0.01). The items-per-step parameter is a positive whole count. The maximum must be at least the minimum. The shop's configured batch price remains the base. Each complete volume step raises a selling shop's price or lowers a buying shop's price, clamped to the configured bounds. Volume is successful items sold minus items bought since the setting was enabled; small residual volumes are truncated toward zero. Enabling again establishes a new volume baseline. The price is constant for one complete transaction, then volume advances. Mob shops and player/group-account shops do not use this policy. Bounds and trade quotas should be configured together; independent shops are not a server-wide price oracle or arbitrage balancer.

Boards and market listings show the effective batch price. A changed effective price invalidates an outstanding confirmation. Dynamic trades always require a fresh confirmation, even when the ordinary price threshold is disabled.

Transfers and existing-player tenure

The existing transfer tab now has Payment purpose (up to 96 characters, without control characters). The purpose appears in account history when the shared MariaDB history is enabled. Player transfer targets still need to be online.

On login, a player with no first-seen entry gets a conservative timestamp from their accumulated vanilla play-time ticks: current time minus played time, clamped to zero. This is a lower bound on tenure, not an exact first-join date; offline time cannot be reconstructed. Existing timestamps are preserved.

Requirements

  • Minecraft 1.21.1
  • NeoForge 21.1.250 or newer compatible 21.1 release
  • LowDragLib2 (LDLib2) 2.2.37 or newer, installed on the server and every client
  • Java 21

Jade 15.10.6 or newer is optional on clients for the shop identification overlay; this integration does not require Jade on the server.

TDEconomy uses its native quest system. The former FTB Quests reward and FTB Library integrations are removed.

JEI and EMI are optional client integrations for the shared shop, quest and order material picker. Neither is required: inventory selection and the built-in icon search work without a recipe viewer. The adapters compile against JEI 19.56 and EMI 1.1.24 for Minecraft 1.21.1.

The group-account creation contract is registered and supplied directly by TDEconomy. It does not require a separate KubeJS item registration or resource pack entry.