Playing together with TDGroupe
Mod version shipped with FlammiCraft: 0.29.0
TDGroupe manages player groups, private chat, titles and optional map and Waystones integration. A player group is separate from a TDEconomy business account and does not sell claims. This guide describes current sources; compatible server and client builds are required.
Create a group and invite players
- Open
/tdgroupeor the three-person inventory shortcut. FTB Library places it in its sidebar; the fallback sits above the inventory's upper-right edge. - Create a free group with a unique name of 3–32 characters. A player can belong to only one group.
- Select its name and one of 16 text colors and save. Left-click cycles colors forward; right-click cycles backward.
- As owner or manager, invite a known online or offline player.
- Accept using the dialog, chat action or
/tdgroupe accept;/tdgroupe declinerejects it.
Invitations do not reserve membership capacity. Acceptance rechecks current membership, capacity, expiry and inviter authority. New worlds default to seven days; existing configured lifetimes and issued deadlines are preserved. Confirm membership in the group list rather than treating a sent invitation as success.
Roles and ownership
Owners manage settings, roles, members and ownership. Managers can invite, withdraw invitations and remove ordinary members, but cannot remove peer managers or the owner, assign roles or change group settings.
Members may leave. An owner must first transfer ownership or remove all other members and dissolve the group. The previous owner becomes an ordinary member after transfer. Destructive lifecycle actions require confirmation.
Linked economy accounts retain separate authorization. Inspect their link in the dashboard: visible group membership does not automatically authorize money access or claim actions.
With TDEconomy and a current group, received invitations and linked accounts have separate buttons on the same row. Group chat and status feedback sit below them. Only the current group owner can open account management.
Chat, waypoints and Waystones
/gc <message>, /teammsg <message> and Minecraft's existing /tm <message> shorthand send to currently online group members. TDGroupe replaces the vanilla team-chat handler; scoreboard teams select neither recipients nor access rights. All three commands share the chat rate limit and preserve literal text without expanding selectors. Incomplete fragments such as @e[ remain ordinary message text, including for operators. Public group decoration is configurable; private chat always includes the group name.
Select a waypoint in Xaero and choose Share with group. The chat link opens Xaero's import dialog in the destination world. If the link reports a different world, switch to the backend serving the destination and open it again. Coordinates remain readable without Xaero.
With the Waystones integration, Share for team uses the owner's current TDGroupe membership. Reopen a destination screen after membership changes. Public and personally activated destinations retain their ordinary behavior.
Shared maps and restoration
Xaero's World Map integration archives personal exploration even without a group. Current members additionally receive one another's uploaded terrain. Open the map with its configured key, normally M, activate the relevant dimensions and allow the gradual import to progress. This does not generate unexplored terrain.
Restoring lost local terrain requires the same authenticated player identity and previously confirmed uploads. The archive does not include waypoints or XaeroPlus-specific overlays. Leaving a group cannot erase knowledge already received by a client.
From version 0.16.0, ongoing exploration no longer rewinds saved-map imports: only changed tiles are requeued, and waiting regions immediately yield to other regions. Terrain capture and application share a one-millisecond scheduling budget per frame; an already started tile finishes before the budget is checked again. Up to sixteen transfers per direction cover acknowledgement delays while buffer memory remains bounded. This does not guarantee a completion time or stutter-free gameplay; both require in-game checks with your maps and hardware.
From version 0.18.0, synchronization waits until Xaero has stopped rewriting a tile for about three seconds; a tile that keeps changing is still checked after twenty seconds. Unchanged tiles are recognized by a fingerprint and are neither re-encoded nor offered again. For saved regions, TDGroupe requests at most one Xaero region load every two seconds, and only while Xaero's own load queue is empty; received tiles may request one every quarter second. Regions Xaero already holds go first, and synchronization no longer takes priority over the regions you are viewing on the map. Received tiles are fully prepared in the background, so less work happens in Xaero's frame. In-game checks with large maps remain separate from source tests and the build.
A login also no longer re-uploads or re-downloads the whole map. Each client records in the .tdgroupe-sync folder of its Xaero map which tiles it already holds. The server sends one short digest per region; only differing regions are compared, and only missing or changed tiles are transferred. Saved regions are checked again only when their Xaero file changed, and a tile is uploaded only when it differs from the last upload the server confirmed. Received tiles are written to disk first and applied once Xaero has loaded their region; they also survive a restart. New tiles use a more compact encoding; older archive entries remain readable. Bandwidth is limited by mapDownloadKiBPerSecond in serverconfig/tdgroupe-server.toml (default 1024 KiB/s per player) and mapUploadKiBPerSecond in config/tdgroupe-client.toml (default 512 KiB/s).
New contributions for the same chunk and layer share one terrain payload when their encoded bytes match. Clients first send a 48-byte probe containing the content hash and an explorer-specific proof. The server can register a matching archived tile for another explorer without uploading the terrain again. Each explorer keeps a separate ownership record even across groups. If one explorer uploads changed terrain, the others keep their previous version. One file covers up to 4 × 4 chunks in a dimension and layer. Existing individual files continue to work. The upgrade does not reclaim their space automatically.
To compact an existing archive, work from a complete offline copy or a stationary backup. In the TDGroupe source checkout run ./gradlew compactMapArchive --args='"source/tdgroupe-maps" "output/tdgroupe-maps"' with Java 21 (on Windows use gradlew.bat). Supply absolute paths, an existing destination parent and a new output directory outside the source. Allow space for both copies. The export packs the active dataset, copies inactive datasets and other files, then reopens the result and compares every explorer, position and terrain payload before reporting success. If verification fails, the message identifies the unfinished staging directory. To adopt the export, keep the server stopped from the final source snapshot through replacement, retain the original separately and use the verified copy as the complete tdgroupe-maps directory. Older builds require the pre-upgrade backup.
Update the server and every client together to this build using map protocol 12, then restart them fully. Preserve local maps, the .tdgroupe-sync and .tdgroupe-received folders and the server archive; older .tdgroupe-received markers are imported once on first start and left unchanged. The first login afterwards builds the sync state without uploading tiles the server already archived. If .tdgroupe-sync is lost, missing tiles are simply downloaded from the server again; do not delete files or change the dataset identity to force catch-up. Synchronization starts automatically for the active Xaero dimension after archive validation. Previously explored areas do not need to be visited again while their personal local terrain data remains available. Multiplayer, dimension-switch and reload acceptance remain separate from source tests and builds.
Operators must back up the external tdgroupe-maps directory separately from world backups. Preserve the dataset identity during deliberate restoration, and deliberately choose a new identity for an unrelated world. The transition from legacy data/tdgroupe_maps.dat does not import terrain available only in that file: clients must contribute their personal exploration again. Read the detailed reference before changing archive identity or upgrading an old archive.
Every external contribution is validated at server startup before synchronization is enabled. Up to four background readers check batches of up to 32 files, with at most eight outstanding batches and lower limits on small CPUs. Longer validations log their completed contribution count about every ten seconds. Existing format 1 and 2 files stay in place, including any legacy data/tdgroupe_maps.dat. A failure keeps synchronization disabled for that run. Preserve the reported file and investigate the cause. Actual startup time for the server archive still requires a measurement after a manual update and restart.
Large map downloads continue region by region as tiles are received. After returning to a dimension, the client compares its saved state again and requests terrain that is still missing. Short Windows file locks are retried on the storage worker before the client has to resend an upload.
Titles and settings
Open My titles with /tdgroupe title. Search titles, inspect their conditions, then select an owned title or hide it. Before buying, review the exact title, price and personal-account balance. One Flammtaler equals 100 Funken. Enter 9.99 in the title editor or purchase command for 9 Flammtaler and 99 Funken. Later unlocks preserve an explicit selection.
Operators use /tdgroupe config for member limits, new invitation lifetimes, public group names and the inactivity threshold. In database mode these changes apply across the cluster. Lower limits do not evict existing members. Personal shortcut offsets live in config/tdgroupe-client.toml. See Database and several servers for the local configuration and the upgrade.
| Symptom | Check |
|---|---|
| Invitation cannot be accepted | Membership, free slots, inviter's current role and expiry. |
| Shared map does not progress | Xaero version, active dimension, accepted membership and server archive readiness. |
| Received map tiles show stone instead of a mod block | The block comes from a mod only the uploading member has; the client log names it once. Install the same mod list; tiles already received are only redrawn once that member updates them. |
| Archive loading fails | Preserve the archive and investigate the reported file; never replace it with an empty archive. |
| Paid title is missing | Inspect the purchase state and reconnect before paying again; committed entitlements are replayed without another charge. |
Server refuses to start because of tdgroupe_database.json |
The world was moved to the database. Set [database] enabled = true in tdlibrary-database.toml or return to world storage as described in Database and several servers. |
| Message that the group database is unreachable | Check /tdgroupe storage status; retry the change once the database is back. |