Tags
Creators
Details
1.0.0
Compatibility
Changes
QTeams 1.0.0 - Initial Release
Welcome to the initial launch of QTeams! QTeams is an advanced team routing, tablist management, and client-side anti-leak plugin developed specifically for Paper and Purpur 1.20+ servers running competitive tournaments, scripted SMPs, and multi-world events.
Included Features in v1.0.0
Tablist Sorting & Custom Formatting
- Weight-Based Tab Ordering: Sort players on the tablist by custom numeric priorities (
tab_weight). Teams with lower weights sort higher on the vanilla player list, allowing admins, leaders, or priority squads to appear first. - Tab Roster Formatting: Automatically formats player list names with team colors and assigned roles (e.g.,
[Red ┃ Healer] Username). - Global & Per-Team Controls: Toggle the entire tablist formatting system globally in the Main GUI, or customize individual team weights and visibility independently.
Async Full Render-Distance No-Leak Engine
- Event-Driven Chunk Masking: Listens to Paper's
PlayerChunkLoadEventto automatically mask newly loaded chunks up to the player's full client render distance. - Off-Thread ChunkSnapshot Scanning: Processes block analysis asynchronously off the main server thread, eliminating TPS drops and Netty packet buffer overflows during world rendering.
- Batched Packet Updates: Sends block updates using section-wide multi-block change packets, drastically lowering outgoing network packets per chunk.
- Radial Restoration: Toggling No-Leak off smoothly refreshes the player's view distance radially outward, restoring true blocks without server lag or visual glitches.
PlayerView Distance & Limit Culling Engine
- Configurable Visual Culling: Limit how far players can render each other or cap the maximum number of visible players to reduce client-side FPS drop in crowded arenas.
- Automatic Staff Bypass: Server Operators (OPs) permanently bypass all visual culling rules.
- Custom Exemption Lists: Configure specific teams or player UUIDs that remain permanently visible to all players.
Command Selectors & Teleport Utilities
- Squad Target Selectors: Native
@teamand@team:rolecommand selector expansion for Bukkit commands (e.g.,/give @blue iron_swordor/effect give @red:scout speed). - Random Teleport Operator: Execute
/tp r <player>or/qt tprand <player>to teleport a random eligible player to a target coordinate.
GUI Management Suite
- Complete visual control through
/qt gui, covering team creation, wool-based color palettes, friendly fire toggles, glow outlines, No-Leak mode, tablist weights, and player role assignments. - Expanded 36-slot role picker with presets for Staff (Admin, Moderator, Member) and Combat classes (Tank, Scout, DPS, Healer, Runner, Hunter), plus custom chat input.
QWorlds Integration
- Server Network Hub: Running
/qt guiwhile QWorlds is installed opens a shared dashboard connecting both plugins. - Queue Synchronization: Allows QWorlds event queues to assign incoming players to QTeams squads automatically upon entry.
Installation
- Place
QTeams-1.0.0.jarinto your server'splugins/directory. - Ensure your server runs Paper or Purpur 1.20 or newer.
- Start or restart your server to generate
plugins/QTeams/teams.yml. - (Optional) Install
QWorldsto enable the shared network hub and automated queue routing.
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:C4ecAd2k:RyODUFkm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:C4ecAd2k:RyODUFkm"
}

