Skip to main content

Accounts and player groups

Mod version shipped with FlammiCraft: 2.64.0

Economy business accounts have their own members and permissions. Linking a TDGroupe player group adds permissions for its owners, managers and members. It moves no money, goods, shops or ownership. A new link grants no additional permissions until the account owner explicitly configures them.

Cluster writes (2.56.0)

Account definitions, names and permissions are edited under one shared metadata lease. A backend refreshes the current definitions before editing or spending group funds. A competing action may be temporarily unavailable. Successful administrative replies wait for the database commit; conflicts report failure instead of acknowledging a change that later disappears. See cluster operation for recovery and the manual permission-revocation checks.

Select a business account in the dashboard and open Link. Player-group access shows the account, selected or linked group, and both owners as information. Choose account appears when other accessible accounts exist.

  1. Open Choose player group. Type directly into search; both names and owners are searchable. Paging follows the current results.
  2. Review the selection and owners. Selecting a group alone does not create a link. Change reopens group selection.
  3. Choose Send request and confirm the review. If the same person owns both sides, the action is Link group and one approval is sufficient.
  4. The other owner opens the connection through the group view or notification and chooses Approve. An owner who already approved sees the waiting state instead of being asked to confirm again.

Requests last seven days. Background refreshes keep the view current without regularly blocking the controls. Refresh remains available for an explicit check. An unavailable player group grants no shared access; direct account permissions remain independent.

Linked group permissions

Open Edit group permissions or View group permissions. Owner, Managers and Members select the exact player-group role directly. Each permission name has a separate [x] Allowed or [ ] Not allowed switch. The page counter identifies the current page; arrows change the visible permissions without changing roles.

Only the account owner can edit. Save role permissions applies the draft after server confirmation. Other viewers can inspect it; archived accounts cannot be edited. Current role permissions add to direct account permissions without copying player-group members into the direct membership list.

Changing roles or leaving with unsaved edits offers Save changes, Discard changes and Keep editing. Rejected saves preserve the draft. A concurrent permission change produces a warning; review your preserved draft before saving again.

Direct member permissions

Open Permissions for the business account and use Select a member. Switches apply to that direct member. Save confirms the changes; restoring defaults remains a separate deliberate action. Switching members and closing protect unsaved drafts just like role editing. Linked group permissions are managed separately.

Status, unlinking and errors

  • Pending: the explanation identifies whether your approval or the other owner's is missing. Shared access is not active yet.
  • Paused: both current owners must approve again after an ownership change.
  • Expired: unlink the old request, then send a new one.
  • Unlink: either current owner reviews and confirms the unlink. Derived access ends while direct membership and account contents remain intact.
  • No confirmation: refresh and inspect the current state before submitting the same change again. Closing the screen does not cancel a submitted action.

Tab and Shift-Tab move focus; Enter or Space activate a button. Escape returns and protects unsaved drafts. Long reviews can be read with the mouse wheel or Page Up/Page Down. Shortened names have full hints, and selection/review shows the relevant context again.

Acceptance after updating

Manually install matching client/server builds and fully restart both. Test a request, both approvals and unlinking with two owners, then repeat with one person owning both sides. Edit roles and direct members, switch context and test Save, Discard, Keep editing and Escape. Keep a draft open during an external permission change and check a rejected save preserves it. Check small GUI sizes, long names and keyboard-only operation. Automated source and widget tests do not establish gameplay acceptance.