Better together.
Your complete Teams wiki.

Start your team

Create a home for your group, invite your friends, and learn the essentials.

A team connects your members, private chat, rank ladder, shared claim access and optional treasury. You belong to one team at a time. Your team name is its public label; its permanent identity stays the same when it is renamed.

Your first five minutes

1. Run /team list to discover teams, or /team info <team> to inspect one. /team top ranks teams by member count.
2. Join an open team with /team join <team>. For a closed team, ask someone with invitation access to invite you, then use /team accept. Use /team deny to decline.
3. To lead your own team, use /team create <name>. Creation may cost money if the server has configured a price. A failed payment cannot create the team.
4. Open /team or /team gui after joining. The menu shows your rank, group and members, with management buttons according to your access.
5. Try /tc Hello team! for a single team message. Use /team help for the server's command list and Tab to complete supported arguments.

Names and capacity

Fresh defaults allow 3–24 characters in a team name, using letters, numbers, underscores and hyphens. Names must be available and pass the server blacklist. Existing server settings can differ. The default member limit is 20 including the Leader; a Leader's capacity permissions can increase it. An invitation does not reserve a slot or bypass a full team.

New members start at the lowest enabled rank. New teams have 15 rank slots, but leaders can customize or disable unoccupied lower slots. Team ranks are separate from your server-wide donor, progression or PvE rank.

Invites, membership & leaving

Open recruitment, invitations, removals and safe team closure.

Invite or recruit

Use /team invite Alex to invite an online player. Invitations must be enabled and expire after the configured interval—60 seconds in a fresh configuration. The invitee must still be eligible when accepting: not already in another team, not banned, and within capacity.

/team open enables direct joining; /team close returns to invitation-only joining. Officers and Leaders can do this by default. Closing a team does not remove current members. A valid invitation still lets its recipient join a closed team.

Managing members

/team kick Alex removes an online lower-ranked member. /team ban Alex removes a member if applicable and prevents that player from joining your team again. Ban and unban can resolve known offline players. /team unban Alex removes that team ban; it does not automatically rejoin or invite them. A team ban is not a server ban.

The team action rule and your Bukkit permission must both allow the operation. Kick and ban also protect equal and higher ranks. Rank labels alone do not grant authority. Promoting someone into a powerful permission group can immediately unlock chat, claim or bank access.

Leaving and disbanding

/team leave removes a normal member and clears their team chat mode and linked personal-claim association. Their personal claim ownership remains. If the Leader leaves, the team is disbanded, subject to the treasury being empty. Arrange an admin leadership transfer before leaving if the team should continue.

/team disband deletes your team when your group allows it. Treat the command as immediate: do not rely on a confirmation dialog. Withdraw or distribute every currency in the team treasury first. A nonempty treasury blocks closure, including admin closure and removal of the Leader. If the banking service is unavailable for a previously linked team, restore it before trying to close the team.

Using the team menus

Know which changes are drafts and which actions apply immediately.

The main menu contains Members, Ranks and display, Group permissions, Claims and chest access, and Team bank when the relevant integration and access are available. A missing button can mean a missing permission, a team group restriction or an unavailable integration.

Editing a draft

1. Open Ranks and display or Group permissions.
2. Choose a rank or action. Text fields close the inventory and ask for input in chat. Type cancel to abandon the input.
3. Use Back to navigate within the editor. Choose Review and save to inspect the draft.
4. Choose Save to apply it, or Discard to abandon it. Closing a draft is not the Save action.

Drafts remember the team's revision. If someone else changes the team, reopen the editor instead of trying to overwrite newer settings. Access is checked again when saving, so an old open menu does not retain authority after demotion.

Actions that are not drafts

Direct commands save immediately after validation. Member rank assignment, moderation buttons, claim presets and object/claim trust commands also apply through their own immediate actions. The Review / Save / Discard workflow belongs to the rank, group-rule and team-wide trust drafts; it is not a universal confirmation screen.

Members are paginated in groups of 45. Open a member and choose Assign rank for direct assignment, including offline members. The legacy promote, demote and kick buttons call commands that require an online target. The bank button opens /bank; choose a currency and then Team treasury.

Team & officer chat

Toggle a channel or send one message with /tc, /to and /toc.

After /tc, ordinary chat goes to your team until you toggle it off or switch channels. Running /to switches to officer chat. Running the currently selected toggle again turns it off. A one-message command does not change your current toggle.

/tc Meet at the main gate.
/to Please review the new recruit.
/toc I will check the storage permissions.

Team chat is available from Initiates by default; officer chat starts at Officers. Both senders and recipients need the matching server permission and team group access. A cosmetic rank called “Officer” does not qualify unless its group does.

A team permissions manager can use /team officerchat group MEMBERS to change the minimum group, or edit the officerchat action in the permissions menu. The word group is reserved for this control path. Modes clear on disconnect, leaving, removal or disbanding. GUI text prompts take priority over channel routing, so your editor input is not broadcast as team chat.

Ranks, groups & customization

Fifteen stable slots, four permission groups, and a protected Leader.

Each rank has a stable ID, display name, color, icon, lore, group, order and enabled state. The ID identifies the slot; its order determines hierarchy; its group determines which minimum-group rules it meets. Changing a name or color does not change its group.

Higher groups satisfy lower minimums. If an action requires Members, Officers and Leaders also qualify. A separate relative-rank check still prevents managing equal or higher-ranked members.

Promote, demote or assign

/team promote Alex moves an online member up the enabled ladder; /team demote Alex moves them down. The Members menu can assign an eligible rank directly, including for an offline member. You cannot change yourself, assign the Leader slot, or raise someone to your own rank or above. Leadership transfer uses the protected admin command.

Customize the ladder

Use /team rank for the draft editor and /team rank list to inspect slot IDs, aliases, names, groups, ordering and enabled state. Technical examples below apply immediately:

/team rank level_8 name Officer
/team rank level_8 color #00ccff
/team rank level_8 icon CYAN_CANDLE
/team rank level_8 lore Trusted teammate|Can help manage recruits
/team rank level_8 group OFFICERS
/team rank level_8 order 9
/team rank level_3 disable
/team rank level_3 enable

Names are 1–48 characters. Colors use #RRGGBB. Icons must be valid item materials. A vertical bar separates lore lines. Order changes swap positions rather than creating duplicate positions; lower slots use orders 1–14. Disable only unoccupied slots, and keep at least one nonleader slot enabled.

The Leader slot always stays enabled at order 15 in Leaders. No lower slot can be mapped to Leaders. Use level_N or the retained enum alias in commands, not a custom display name. Renaming a rank does not rename its stable identity.

Who can do what?

The default action matrix and how your team can change it.

These are fresh-team defaults. Your team can set different minimums with /team permissions. Click an action to cycle the group, then Review and Save. A direct example is /team permissions bank.withdraw OFFICERS.

The four groups are internal team roles, not LuckPerms group names. A server permission is a second gate: granting a command node does not automatically grant the team action. Prefix editing additionally remains actual-Leader-only, and personal-claim linking requires the actual claim owner.

Use care when delegating permissions or ranks: these controls can change who qualifies for other actions. For a recruit-friendly team, keep chat and deposits open to Initiates, decide explicitly who can withdraw funds, and grant build/container access only to groups you trust.

Team identity, MOTD & statistics

Set your name and prefix, write a welcome message, and inspect team stats.

/team edit <field> <value> supports name, prefix, description, color and motd. The edit action is Leaders-only by default. Prefix changes always require the actual Leader.

/team edit name Ember
/team edit prefix [EMBER]
/team edit description Builders and explorers
/team edit motd Meet at the base before our next expedition.
/team edit color #00ccff

Fresh defaults permit 16 visible prefix characters and 128 visible characters each for description and MOTD. The MOTD can display when a member logs in. Server configuration controls these limits and the public chat format.

Colored prefixes and charges

Plain prefixes are free. MiniMessage, legacy color, legacy formatting and RGB styles require their own permissions and may have configured prices. Mixed styles require every applicable use permission; the highest applicable non-exempt price is charged, rather than adding all prices together. A fee-exemption node does not grant permission to use that style.

Prefixes must have usable visible text and be unique according to the plugin's validation. Interactive or special tags such as click, hover and newline are rejected. Reapplying the same prefix is not a new purchase. Check the requested price and your balance before changing a paid style.

Information and rankings

/team info shows your team; add a team name to inspect another. /team list lists teams. /team top shows the member-count leaderboard, with 15 entries in a fresh config. Kill, death and KD statistics can also appear through server displays using PlaceholderAPI. KD uses kills when deaths are zero, and otherwise kills divided by deaths.

Claims & team access

Keep ownership while sharing the right level of access.

GriefPrevention owns the land claims. SimpleTeams supplies dynamic access based on team membership, ranks and groups. The current Leader's player claims automatically participate. Other members can opt in their own root claims with /team claim link while standing in a claim they own.

Linking does not transfer ownership or spend team funds. The owner retains full access. To stop sharing a linked personal claim, stand in its root and run /team claim unlink. Leader-owned claims already use team trust and do not need linking. Admin claims cannot be linked through this path.

Understand the three trust levels

Build includes Container and Interact; Container includes Interact. A restrictive container threshold alone is not a complete security policy if another rule still grants Build. Review all applicable paths, including manual GP trust and any object override.

/team trust
/team trust interact INITIATES
/team trust container OFFICERS
/team trust build OFFICERS
/team claim list
/team access Alex

With no arguments, trust shows the team's rules and whether the bridge is active. Setting a threshold requires the trust action. Group thresholds follow group mappings; explicit rank thresholds follow the team's current rank order. Existing teams may retain legacy rank thresholds instead of the fresh group defaults.

/team claim list lists Leader-owned and linked personal claims with locations and thresholds. /team access explains your team/ally access in the current claim; add an online player's name to inspect their bridge access. This explanation is not a guarantee that every GP or siege condition permits the action.

Rooms, containers & temporary trust

Apply claim overrides, object rules, presets and timed grants.

Current claim and subdivisions

Stand inside a claim belonging to your team. Its actual owner can manage their linked personal claim; delegated team management needs the trust action and the correct team association.

/team trust here container OFFICERS
/team trust here build LEADERS
/team trust here container default

here sets the root claim policy. default returns that team rule to inheritance. For a subdivision, first use GP's /restrictsubclaim so parent permissions do not defeat a tighter rule, then use /team trust subclaim <type> <group|rank|default> while standing inside it. Check both container and build inheritance.

Choose a chest or door

1. Run /team trust this container OFFICERS, or select the chest control in the Claims menu.
2. Right-click the intended container within 30 seconds. For a door, use /team trust this interact MEMBERS.
3. The selected block must still be in the same root claim you manage. The plugin rechecks ownership/access before saving.

An object-specific rule is evaluated specifically for that object. Use default to restore inheritance. Physical layout, other access routes, manually trusted players and GP restrictions still matter; inspect the result with an ordinary member account.

Presets and history

/team trust preset team-base applies all three configured thresholds to your current claim (or current subdivision for that preset path). The bundled private-storage preset uses Lieutenant for interaction and Leader for containers/building. Presets can be changed by the administrator, so review the menu's three displayed rules before applying. Use /team trust history to view recorded changes for the current claim.

Timed access

/team trust temporary Alex container 30
/team trust temporary team:Ember interact 60

The duration is 1–10,080 minutes, up to seven days. Player targets must be known to the server. A team target must be a mutual ally. Expiry ends this temporary grant; it does not revoke unrelated access the player already has. Grants are scoped to the claim and are recorded with an expiry timestamp, rather than requiring the recipient to stay online.

Alliances

Agree to an alliance first, then grant claim access deliberately.

An alliance requires agreement from both teams. It does not merge membership, chats, ranks or treasuries, and accepting it does not automatically open claims.

/team ally request Ember
/team ally accept Ember
/team ally deny Ember
/team ally list
/team ally remove Ember

Use request on your side; the other team's authorized manager uses accept with your team's name. Deny rejects an incoming request. List shows mutual allies. Remove ends the relationship on both sides and makes ally-based claim grants inactive. The ally management action defaults to Leaders; viewing the list does not require that action.

Give allies access to a claim

Stand in the managed claim and use /team trust ally interact MEMBERS, for example, to grant qualifying allied members interaction. The threshold applies to the visiting allied player's team group or rank. It is a claim-level allied-team policy, not a named-team selector. /team trust ally container off disables that ally rule; review higher Build grants too.

Use a timed team:Name grant for a specific mutual ally and duration. Each claim-owning team chooses its own permissions independently; reciprocal alliance membership does not imply reciprocal land access. Online members of allied teams are notified when applicable access is granted.

GriefPrevention essentials

The land-claim commands that complement your team.

/claim is GriefPrevention land creation. /team claim links or lists an existing claim. They are different commands. Claim tools, block allowances and claim costs come from GP's server configuration.

Stand inside the intended claim before changing manual trust, and read the response. GP commands can have broader scopes when used outside claims. Trusting a player is a meaningful grant: team membership does not protect you from someone you deliberately allow to open containers or build.

Siege: Seasonal world only

ProtoSMP enables siege only in the Seasonal world.

In the Seasonal world, /siege <player> asks GriefPrevention to start a siege against an eligible player. It is a GP feature, not a SimpleTeams command. Being on a team does not start a siege, extend siege to other worlds, or automatically grant victory.

The command checks the world, player eligibility, proximity to the claim, existing sieges, immunity and cooldowns. Admin claims cannot be besieged through this path. A failed attempt explains the applicable restriction in chat.

What changes during a siege?

GriefPrevention applies its configured siege rules to the encounter. The list of breakable blocks, post-siege door-access duration and cooldown are server settings. Do not assume a team trust threshold overrides those rules or that this wiki's normal access examples promise siege protection. Follow the current in-game messages and ProtoSMP's Seasonal rules.

Normal team membership and treasury rules still apply. Siege is not a permission to withdraw bank funds. Container access, physical banknotes and claim interactions are separate from a shared bank balance. Ask staff about any live siege rule not shown in game; this handbook does not invent a loot window or a block-breaking whitelist.

Your team treasury

Keep shared funds separate from personal money and debt.

1. Open /bank or select Team bank in /team.
2. Choose the currency.
3. Open Team treasury, available when the team bridge grants View.
4. Choose an allowed deposit or withdrawal action and follow its amount/confirmation flow.

The team treasury belongs to the team UUID, not to its name or Leader. Renaming the team or transferring leadership keeps the same account identity. Different currencies have separate balances, and personal balances remain separate from the team's balance.

No team overdraft

Team accounts have no fees, overdraft or debt interest. They can only spend funds they hold. A player's unlimited-overdraft permission does not turn a team account into a credit account. Positive team balances may earn savings interest when configured.

You may fund a team deposit using personal overdraft if your personal plan, credit availability and penalties permit it. The resulting debt belongs to your personal account. Your personal transaction rules and fees can still apply even though the receiving team account has no fees.

Before you close a team

Empty every currency, not just the one you last viewed. The plugin checks the treasury centrally when disbanding, when the Leader leaves, and when an admin removes the Leader or disbands the team. Funds are not automatically distributed. A bank-linked team cannot be deleted while the economy integration is unavailable.

Personal banking, fees & debt

Read your account, understand its cycle, and avoid confusing credit with savings.

/bank (also /azobank) opens currency/account menus. The account screen shows signed balance, debt, pending fees, pending interest, available credit, transactions remaining, reset time, strikes and any scheduled plan. The statement includes recent journal history.

A negative balance is debt. Available credit is how much further spending your account can support, not money you own. Pending obligations reserve credit too. Incoming money reduces a negative balance naturally, but it does not cancel pending charges.

Transactions and plan changes

Successful outgoing operations that use bank funds count against your cycle allowance. Incoming credits and cash-only purchases do not. Normally, spending after the allowance uses the plan's configured overage fee. Plans may allow rollover of unused transactions. Comparing and selecting a new plan schedules it for renewal; it does not instantly refill your allowance.

Interest

Ordinary overdraft interest is assessed at renewal from bank debt. Borrowing cash at an ATM assesses cash interest immediately on the newly borrowed portion and records it as pending until renewal. The first term tracks that cash borrowing to avoid charging both first-term rates on the same portion.

For example, withdrawing 100 from a balance of 40 borrows 60. At a hypothetical 5% cash rate, 3 is recorded as pending interest. Depositing money later reduces the outstanding borrowed principal but does not refund that already-assessed charge. Rates are examples; the selected plan defines the real percentages.

Positive bank balances can earn configured savings interest. Inventory cash does not earn bank interest. Personal and team savings are calculated separately. Due cycles catch up while you are offline, in time order, so unpaid debt or retained savings can compound.

Failed billing

If renewal cannot be paid, the account drops to the free plan and records a strike while keeping outstanding debt and pending charges. Borrowing perks—including unlimited overdraft—stop providing debt spending. After the free allowance is exhausted, bank payments are denied; earnings and cash-only payments can still be possible.

Forgiveness begins only after your balance is strictly positive and all pending obligations are zero. Stay in that state for the configured forgiveness duration. A relapse resets the timer. Time never writes off debt, and there are no separate loan contracts in this release.

Banknotes, ATMs & payments

Use physical currency and understand where the money comes from.

When enabled for a currency, banknotes represent value using database-backed unique note IDs. Their material, name and denomination are configurable. Ordinary renamed paper is not a valid note, and copying a note does not create another redeemable balance.

Use /bank atm near a registered ATM block, or interact through the available ATM flow. Without remote access, the command requires a registered ATM within four blocks. Choose the currency, add denominations to the withdrawal draft, review the total and charges, then confirm. In the denomination draft, left-click adds and right-click removes. Deposits select actual valid notes.

Leave inventory space for a withdrawal. Do not discard a note while troubleshooting a delivery problem; ask staff to inspect its ledger state. Cash-first, account-first or account-only payment priority is a currency setting. An ATM withdrawal that needs overdraft can create pending cash interest as explained in Personal banking.

Paying and receiving

The bank's Pay a player flow accepts a recipient and amount in chat and asks you to confirm. Currency-specific balance, send, exchange and top commands depend on the server's configured labels; use their help or tab completion instead of assuming a universal /eco alias.

Player transfers, team transfers and cash redemption move existing value. Ordinary mob/ore rewards, selling to an admin shop and admin give operations create currency. They are not automatically deducted from Protosmp's treasury. The economy has no automatic inflation adjustment; staff control reward rates and configured costs.

Player command reference

Every registered Teams player command, plus the advanced trust forms.

Permissions are listed in the admin reference. Most commands require a player; info, list, top and help also support console. The direct rank and trust forms below supplement the legacy help text.

Advanced trust syntax

<type> is interact, container or build. Thresholds accept groups or stable rank IDs/aliases. Use default only for team overrides, and off only for ally rules. See the claim guides before using broader grants.

Common questions

Practical answers when a command, claim or bank action is blocked.

Installation & compatibility

Supported versions, optional bridges, build and ProtoSMP deployment.

This handbook targets SimpleTeams 2.4.0-azo on Paper 26.2 and 26.3 with Java 26. Optional integrations are the Azo GriefPrevention 16.18.7-teambridge2-azo API, Azo ExcellentEconomy 2.8.0-azo.1, Vault and PlaceholderAPI. Economy requires its compatible NightCore dependency. Folia support is not advertised for this GUI/banking release.

Base team features work without the economy service. Claim integration requires the custom GP bridge, including ClaimAdditionalTrustEvent#getTriggeringEvent; a stock or older GP jar does not supply the same integration contract. Banking requires the compatible TeamTreasuryBridge registration.

Build from source

git pull
./compile.sh

The build uses Java 26 and Maven. It installs the provided custom GP, economy and Vault APIs from the standard-named jars in the ProtoSMP plugins directory into the local Maven cache, then runs mvn clean verify. Override their locations with SIMPLETEAMS_GP_JAR, SIMPLETEAMS_ECO_JAR and SIMPLETEAMS_VAULT_JAR when building elsewhere.

The output is target/SimpleTeams-2.4.0-azo.jar. Runtime optionality does not remove compile-time dependency requirements.

Deploy to ProtoSMP

1. Stop the server and back up plugin data and the economy database.
2. Move any old differently named SimpleTeams jar outside the plugins directory.
3. Run ./deploy.sh after compiling.
4. Start the server and inspect integration/startup messages.

The Teams deploy script targets only /opt/minecraft/multicraft/servers/protosmp/plugins, rejects arguments and duplicate differently named jars, and does not build or restart the server. Do not confuse it with another fork's deployment script.

All Teams permission nodes

Bukkit permissions, internal group rules, limits and prefix privileges.

simpleteams.player.* is declared default true and contains the player nodes below. simpleteams.admin.* defaults to OP and contains the five admin nodes. Specific permission negations can restrict access. Internal team group checks remain in force even when a command node is granted.

Member capacity

simpleteams.maxmembers.<positive integer> sets the Leader's team capacity. The highest granted numeric value wins; values do not add together. simpleteams.maxmembers.unlimited overrides finite grants and defaults false. Without these grants, use limits.max-members-per-team. The Leader counts as a member. Offline leaders use the saved effective limit until refreshed.

Prefix style nodes

All listed prefix-style and free-style nodes default false. Plain prefixes are free. Mixed styles need every applicable use node, then charge the highest non-exempt price. The global colored-prefix setting can still disable formatted prefixes. A previously saved prefix does not automatically disappear when the Leader loses a formatting permission; the next edit is validated again.

Administrative node semantics

simpleteams.admin.bypass bypasses the closed-team invitation requirement when joining. It is not a universal team, ban, capacity or bank-safety bypass. simpleteams.admin.disband authorizes the named-team form, but the command dispatcher still checks simpleteams.player.disband first. Account for this if you negate the player wildcard for staff.

Administrator commands

Moderation, leadership transfer, reload and banking tools.

/team setleader requires an online target already in the team. The old Leader moves to the highest enabled nonleader rank. The team UUID and treasury identity stay unchanged. The new Leader's capacity is cached, linked claim policies are cleared, and team inventories are closed. Review land access afterwards: current-Leader ownership is dynamic, and personal links/policies need deliberate re-establishment.

Admin kick uses an online target. Kicking the Leader takes the disband path, including the treasury guard. Administrative disband does not erase or distribute funds. Empty all currencies first.

Related economy tools

Economy nodes in that table are relative to excellenteconomy.. Supply the currency ID explicitly; omission selects the first ID in sorted order. Console supports only the treasury path of /bank. Currency-specific give, take, set, balance, send and exchange labels follow the currency's configured commands. Admin give creates money, take removes it, and set directly adjusts it. Active banking reset operations are rejected rather than erasing debt.

PlaceholderAPI reference

Every fixed Teams placeholder and all leaderboard patterns.

The expansion identifier is simpleteams and the expansion is supplied by this plugin when PlaceholderAPI is present. Use the exact percent-delimited forms below in compatible scoreboard, tab-list or chat configurations.

Text/rank fields normally return an empty string without a team. Numeric fields use the fallbacks noted above; max_size resolves the configured limit rather than a blank label.

Leaderboard patterns

Supported stat tokens: kills, deaths, members, size, kd, kdr and kdratio. Size aliases members; kdr and kdratio alias kd. Sorting is descending, including deaths. KD has two decimal places and treats zero deaths as kills. Invalid ranks or unknown teams return unresolved/null for leaderboard lookups; no viewer context returns an empty result. Do not promise a fixed tie-break ordering.

These are team statistics, not bank-balance placeholders. No new team-treasury placeholder is declared by this Teams expansion. Keep currency/economy placeholders tied to their own provider instead of inventing a simpleteams_bank placeholder.

Teams configuration reference

Default values, messages, rank profiles and which edits affect existing teams.

config.yml contains limits, formatting, trust defaults, presets, creation/prefix prices and new-team rank profiles. messages.yml contains command responses. Existing values survive the additive defaults migration; the values below describe bundled defaults, not a claim about the live server.

Rank profile defaults

Each ranks.level_N entry has name, color, icon, lore, group, order and enabled. New teams copy those defaults. Existing teams retain their saved profiles, so changing YAML defaults or reloading does not rename every existing team's ranks. Edit an existing team through its commands or GUI.

Trust defaults and presets

trust-bridge.group-defaults initializes new teams to Initiates for interaction and Officers for containers/build. Legacy rank defaults are Prospect/Lieutenant/Lieutenant. Saved thresholds remain compatible. Presets under trust-presets.<name> supply three rules; missing preset fields inherit DEFAULT. Validate every rule before relying on a preset in restricted subdivisions.

Formats and text

Team chat uses team-chat.format; officer chat uses officer-chat.format. Sender/message/rank substitutions are handled as literal Adventure placeholders for those channels. The older public chat format is under chat.format. Keep the bundled placeholder spelling for the format you edit instead of assuming all format systems share syntax.

Reload boundaries

/team reload reloads config, messages and team data. Direct team-management commands persist immediately. Use a full restart for plugin jar changes and integration installation. Do not use the server-wide /reload as the deployment procedure.

Claims & siege administration

Bridge requirements, policy storage and Seasonal-only configuration.

The GP bridge evaluates additional team/ally grants at permission checks, using the original triggering event for object-specific policies. It does not rewrite GP's manual trust lists. Rules are stored in SimpleTeams/claim-rules.yml, separately from GP's claim storage and teams.yml.

Check the current Leader's UUID, the root claim owner, linked personal claim membership, restricted subdivisions, object rules and mutual alliances when diagnosing access. A higher team group is not a global GP administrator. Manual GP trust can still provide access independently, and siege handling can constrain or alter the final outcome.

Seasonal-only siege policy

ProtoSMP's rule is explicit: siege is enabled only in the Seasonal world. GP implements this through GriefPrevention.Siege.Worlds. Configure the exact Bukkit world name for the Seasonal world as the only entry; display names and folder names are not automatically interchangeable.

GriefPrevention:
  Siege:
    Worlds:
      - YOUR_EXACT_SEASONAL_WORLD_NAME

This is a template, not a literal world name. Do not add other worlds. BreakableBlocks, DoorsOpenDelayInSeconds and CooldownEndInMinutes under Siege control separate behavior. The fork's defaults for the latter two are 300 seconds and 60 minutes, but this handbook does not assert that production uses those values. An explicit empty BreakableBlocks list differs from accepting the bundled breakable-block defaults.

Relevant GP nodes and tools

These are the GP permissions relevant to this handbook, not a replacement for the full GP administration manual. GP claim deletion and transfer are separate from team disband and setleader. Review associations after ownership changes and test using ordinary accounts without OP bypass.

Economy configuration & treasury

Plans, account identity, monetary flows and live currency editing.

Banking is optional per currency. Missing Banking/Banknotes sections leave those features disabled, so an upgrade does not silently convert every currency. Keep existing currency IDs and storage columns. Use the compatible ExcellentEconomy fork and its own documented migration path.

Banking settings

Plan fields

The free plan must exist and have zero recurring price. Plan monetary values must be nonnegative and fit the currency precision. Transactions uses -1 for unlimited. Rollover_Cap 0 carries none; a negative cap is uncapped. Rates are percentages per configured cycle, not APR. Existing accounts keep their term snapshots until renewal; changes do not reset their allowances immediately.

Protosmp treasury

Configure the real Minecraft UUID under Banking.Treasury.UUID; the name is only a label. That account has unlimited overdraft and transactions, no plan/transaction fees and no debt, cash or savings interest. The exemption applies online and offline without permission nodes. A similarly named player with a different UUID is not the treasury.

/bank treasury <currency> reports its actual signed balance. Collected fees and interest credit it when Collect_Fees is enabled; otherwise collected value leaves circulation. Savings funding can be DISABLED, TREASURY or CREATE. With TREASURY, a payout debits Protosmp; with CREATE, it creates value. Team balances can earn positive savings interest separately from personal balances.

Ordinary reward/admin-shop deposits and admin give operations create currency. They are not automatically treasury-funded. An integration must deliberately use the treasury payout API for that behavior. ProtoLottery needs its own integration change before describing lottery payouts as treasury-funded.

Live currency editing

/bank edit <currency> opens a draft editor. Review and save supported currency/plan/note settings for a targeted live update. Keep identity, storage and precision changes out of casual live edits; restart after manual command/storage configuration changes. There is no automatic ledger export or precision-conversion utility.

The current player account menu exposes pending fee and interest totals, debt and reset time. Richer itemized pending-charge presentation, a player exchange GUI and some menu pagination remain release limitations; do not advertise them as finished screens.

Banking permissions & bonuses

Exact access nodes, additive plan bonuses and fee discounts.

Replace example numbers with the desired grant. Currency-scoped forms are excellenteconomy.currency.<id>.<suffix>, for example excellenteconomy.currency.pc.bonus.overdraft.1000. The highest applicable numeric grant wins across global and currency-scoped nodes. Numeric grants do not add to one another, but the winning bonus adds to the plan base. Discounts clamp to 0–100.

Unlimited bonus nodes default false. Strikes override credit perks, including unlimited, and prevent unlimited transaction perks bypassing the penalty allowance. Effective permissions refresh on the main thread for online players; offline billing retains the last saved values. A changed offline LuckPerms grant may not affect a bill until the next refresh.

The configured treasury exemption needs none of these bonus nodes. Team accounts never gain overdraft from them. Upstream economy command/currency nodes remain under their existing command configuration; avoid granting broad wildcards merely to diagnose a single bank operation.

Storage, UUIDs & backups

Preserve team identity and financial records across changes.

Economy account keys are player:<Minecraft UUID>:<currency ID> and team:<team UUID>:<currency ID>. Team names and Leader UUIDs are not substitutes for the team UUID. A rename or leadership transfer must not create a replacement bank account.

BankStore uses the existing ExcellentEconomy JDBC connector and table prefix. Suffixes are _bank_accounts, _bank_journal, _bank_notes and _bank_lock. Account documents record signed balance, term snapshot, renewal, usage, pending charges, cash-interest tracking, strikes and saved bonuses.

A legacy native player balance seeds a newly managed account. Afterwards the banking ledger is authoritative; the old native row is not a continuously synchronized mirror. Editing that row will not reliably change a managed account. Balances, fee recipients, journal records and note state commit together in SQL; physical inventory delivery happens after that commit.

Back up team data, GP claims, the complete economy database and relevant player/world inventories together before a coordinated migration. Do not delete bank-linked metadata or database rows to get around a closure guard. There is no automatic journal/note pruning or third-party team-bank conversion in this release.

Upgrades & settings migration

Add new defaults while preserving existing teams and configuration.

1. Stop the server. Save a matched backup of SimpleTeams, GP, economy data and inventories when cash is involved.
2. Test the upgrade on an isolated copy using the same currency and world identities.
3. Replace the jar and start with Java 26 on supported Paper.
4. Inspect migration/startup logs and the timestamped config/message backups.
5. Check old teams, legacy ranks, trust rules, member limits, prefixes and every funded currency.

Config/messages migration adds missing defaults while preserving existing leaf values and custom keys. It writes a backup before rewriting. Bundled comments are rebuilt; arbitrary custom comments are not guaranteed to survive. The defaults marker is internal.defaults-version: 2.4.0-azo.

Teams gain schema 3 with rank profiles, group overrides, revision and optional bank-linked metadata. Team/member UUIDs and retained legacy rank aliases survive. The first legacy-team persistence creates a teams.yml backup, and saves use temporary files with atomic replacement where available. Unknown ranks and future schemas fail loading rather than silently dropping teams.

Fresh defaults such as 15 leaderboard entries do not overwrite an existing configured value of 10. Global rank defaults initialize new teams only. Saved trust thresholds remain valid and can be deliberately migrated to group thresholds through commands or GUI.

Rollback

An older jar cannot interpret every new rank slot or profile. Restore a matched pre-upgrade team/config backup when rolling back, and coordinate it with the economy state. Rolling back only the plugin jar after assigning intermediate ranks is insufficient. Native economy balances are not a safe substitute for a current banking-ledger backup.

Troubleshooting & release checks

Known verification, operational checks and current limitations.

The release's Maven verification covers 16 regression tests, including rank migration, stable identities, group behavior, profile/rule persistence, invalid/future data rejection, claim inheritance, membership, prefixes and officer chat. Disposable probes passed on Paper 26.2-132 and 26.3-166 with banking present and absent.

Inventory probes use simulated players. Real connected-player clicks, chest selection, live shop interactions, siege behavior and large-team performance still need deployment testing. Economy MySQL validation and cross-server cash coordination are not implied by SQLite regression success.

Before opening to players

• Use ordinary test accounts from each of the four internal groups; test both sending and receiving officer chat.
• Verify a known offline member can be assigned an eligible rank in the menu, while protected Leader/equal-rank changes fail.
• Test a Leader claim, linked personal claim, restricted subdivision, object override and mutual-ally rule.
• Confirm siege works only in the Seasonal world and fails in every other world.
• Deposit and withdraw a small amount in each currency; verify nonempty-bank closure is denied.
• Inspect treasury UUID and signed balance, plan cycle length, rates and forgiveness settings.

Diagnose in the right layer

For missing commands, check plugin load and Bukkit permissions. For denied team actions, inspect group mapping and relative order. For claim issues, inspect owner/link, all trust paths and GP siege state. For payment failures, inspect debt, pending charges, available credit, allowance and strikes. For a failed save or reload, preserve the log and original data rather than repeatedly editing until the error disappears.

Do not install disposable integration-probe plugins on production: they create/delete fixtures and can shut down the server. Use the normal plugin jar and a separate staging copy.

Sources & handbook scope

Versioned implementation references and the site theme.

This handbook is based on the SimpleTeams 2.4.0-azo source and its wiki, the ExcellentEconomy 2.8.0-azo.1 banking documentation, and the Azo GP command/configuration source. It describes bundled defaults separately from the explicit ProtoSMP rule that siege is Seasonal-only. Live prices, rates, world IDs and customized team rules are not inferred from defaults.

• AzoFork-SimpleTeams source · Markdown wiki
• ExcellentEconomy banking wiki
• AzoFork-GriefPrevention source
• Original Azotorp Bootstrap theme, used for the previous top-voters work.

The handbook embeds the original Azotorp Bootstrap CSS and Bootstrap bundle for a portable HTML file. Its documentation layout adds navigation, search, copy controls and print styles. Player/Admin is a reading filter, not authentication; the admin documentation contains reference material, not live management controls or secrets.

Original SimpleTeams authorship belongs to _GodlyCow and upstream contributors. Bootstrap retains its embedded MIT license notice. Documentation prepared for ProtoSMP; review it when plugin behavior or server policy changes.