Tags
Creators
Details
Licensed ARR
Published 4 months ago
Updated last month
All versions
1.0.2
Release
Team 1.0.2last month 1,398
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
Teams 1.0.2 — Major Improvements & Bug Fixes
This update improves team menus, creation and renaming, banking, requests, permissions, storage, and overall reliability.
Team Creation & Renaming
/team createnow opens a name-entry interface instead of requiring a name in the command./team renameopens the same interface with the current team name already filled in.- Added native name-entry dialogs for supported Java clients, optional Floodgate forms for Bedrock, and an anvil fallback.
- Name-entry sessions expire after two minutes and can only be submitted once.
- Permissions, membership, and team identity are checked again when submitting.
- Native name dialogs can be disabled for clients that require the fallback.
Commands & Admin Help
- Added working
/team admin helphandling and tab completion. /team adminnow opens help without displaying “Invalid Usage.”- Updated admin help with cyan headings and arrows, white commands, and gray descriptions.
- Added transaction and request recovery commands to admin help.
- Added the admin help entry to regular help for authorized administrators.
- Improved membership-based command suggestions.
- Players without a team no longer see the team menu suggestion.
- Players already in a team no longer see create, inbox, accept, or deny suggestions.
- Direct inbox access remains available for request workflows.
- Nested tab completion now rechecks command permissions.
- Fixed inaccessible admin commands appearing in suggestions.
Extension Access
- Added
/team extensionas an alias of/team extensions. - Extension access now requires
itzzteam.command.extensions. - This permission is disabled by default, including for administrators.
- Command execution, suggestions, menu opening, and menu clicks check access.
- Revoking access also prevents further use of an already-open extension menu.
- Individual extension entries retain their separate permission checks.
Custom Bank Dialog
- Added a native custom deposit/withdrawal dialog for supported Java clients.
- Left-click Custom to deposit; right-click Custom to withdraw.
- Added editable amount input, a centered label, submit/cancel actions, and preset buttons.
- Default presets include 1K, 10K, 100K, 1M, 10M, 100M, and 1B.
- Clicking a preset submits the labeled transaction.
- Presets above the configured transaction limit are hidden.
- Dialog text, initial amount, and presets are configurable in
gui.yml. - Input sessions are single-use, expire after two minutes, and remain tied to the original team.
- Permissions, membership, limits, and funds are rechecked before processing.
- Native bank dialogs do not intercept normal chat.
- Unsupported clients and Bedrock retain the existing chat fallback.
- Fixed older chat callbacks potentially consuming a newer bank input session.
Financial Safety & Recovery
- Added durable transaction journaling for deposits, withdrawals, disband refunds, admin balance changes, and ally-slot purchases.
- Added unique transaction IDs and recorded transaction states.
- Improved decimal arithmetic, invalid-amount checks, and overflow protection.
- Improved handling of rejected or uncertain economy-provider operations.
- Disband refunds now target the current owner.
- Offline-owner refunds are supported where the Vault economy provider allows them.
- Failed or uncertain refunds prevent disbanding from continuing.
- Added
/team admin transactionsfor inspecting unresolved financial operations. - Added explicit reconciliation commands for recording verified outcomes.
- Reconciliation does not replay an external payment.
- Withdrawal request recovery checks the transaction journal to prevent duplicate approval of completed payments.
Requests & Inbox
- Added persistent join, alliance, withdrawal, and custom requests.
- Added pagination, expiration, cancellation, and audit history.
- Improved tooltips with readable request types, team names, senders, amounts, and expiry information.
- Internal IDs are stored in item metadata instead of cluttering tooltips.
- Sent and received requests display the appropriate actions.
- Players can cancel their own sent requests without accidentally accepting them.
- Added empty-state text, a close button, and page preservation.
- Added
/team bank request <amount>for withdrawal approval requests. - Added
/team inbox cancel <request-id>. - Improved protection against duplicate approvals.
- Requests persist a processing state before applying an operation.
- Interrupted or uncertain requests remain available for administrator review instead of being automatically retried.
- Added
/team admin requestsand request reconciliation. - Expired requests are saved together in one atomic update.
Membership & Admin Fixes
- Fixed admin force-join removing a player from their original team before validating the destination.
- Destination capacity, membership, and cancellable events are checked before changing membership.
- Full, cancelled, or stale destinations leave the original membership intact.
- Added revalidation after event callbacks.
- Failed force-joins no longer display success messages.
- Expanded immutable change notifications for admin add, remove, kick, force-join, and disband actions.
- Leave notifications now run after membership caches are updated.
PvP, Homes & Teleportation
- Added a dedicated home-deletion confirmation screen.
- Home deletion checks permission when opening and confirming.
- Saved home coordinates are preserved when their world is missing or unloaded.
- Missing-world teleports are refused without deleting the saved home.
- Improved destination hazard checks and final teleport permission checks.
- Improved cancellation handling for movement, damage, death, logout, world changes, vehicle entry, and shutdown.
- Added native Paper/Folia scheduling entry points.
Shared Chest & Backups
- Improved chest access validation.
- Fixed stale menu and refresh handling.
- Added restrictions around restore, rename, and disband operations while affected chests are open.
- Improved backup validation and atomic replacement.
- Chest archives now use stable team IDs.
- Corrupt item data is rejected instead of silently becoming empty items.
- Chest archives are cached instead of repeatedly loaded from disk.
- Ordinary backup snapshots write in the background.
- Pending backup writes are flushed during shutdown.
- Restore and identity migration retain explicit durability checkpoints.
- Failed safety backups prevent restoration from proceeding.
Configuration, Names & Statistics
- Added configuration validation and versioned default migration.
- Existing configuration files are backed up before migration.
- Matching older defaults are updated while customized text is preserved.
- Removed retired rank-related settings and messages.
- Expanded configurable GUI labels and Unicode icons.
- Added an option to disable small-cap item titles.
- Improved password redaction in migration displays.
- Improved Unicode name validation and normalized, case-insensitive lookup.
- Added checks for common mixed-script impersonation patterns.
- Added exact reserved-name matching.
- Improved statistics overflow handling and K/D placeholders.
- Expanded permission and operational documentation.
Developer API & Integrations
- Expanded immutable team snapshots and post-change notifications.
- Added persistent, plugin-namespaced team metadata.
- Added custom request handlers.
- Added permission-checked extension menu entries.
- Added extension PlaceholderAPI support.
- Improved extension registration and cleanup when an owning plugin disables.
- Retained legacy APIs where required for compatibility.
- Removed assignable-rank mutation APIs. Integrations using removed rank features require updates.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:BiaAD8Ew:x1IqXIDm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BiaAD8Ew:x1IqXIDm"
}

