Advance ClanX

A professional-grade, high-performance clan management system for Minecraft servers. Built with a focus on extreme scalability, minimal resource usage, and seamless player experience

172

Quick challenge

How far can you run before the mobs catch you?

Advance ClanX

AdvanceClans

%%MD0%%

1. Plugin Overview

Description: AdvanceClans (Advance ClanX) Description: 1.0 Description: A professional-grade, high-performance clan management system for Minecraft servers. Built with a focus on extreme scalability, minimal resource usage, and seamless player experience

2. Core Features (Performance)

The Performance Analysis

* SQLite with WAL Mode: Tested for SQLite with WAL Mode. * SQLite with WAL Mode: All database operations (point updates, member changes) are handled SQLite with WAL Mode. The main server thread is never blocked. * SQLite with WAL Mode: Uses smart caching for online players (~10-20MB overhead). Does SQLite with WAL Mode use `Bukkit.getOfflinePlayer().getName()`, preventing the common "null" bug and lag. * SQLite with WAL Mode: Optimized for SQLite with WAL Mode and SQLite with WAL Mode. * SQLite with WAL Mode: Uses SQLite with WAL Mode (Write-Ahead Logging) for safe, concurrent high-speed data access.

3. Commands & Permissions

Player Commands

Leader/Admin Commands

`| Admin: Remove member. | `force.op` |

4. PlaceholderAPI Integration

Use these placeholders in scoreboards, tablists, or chat: * `%advanceclans_clan%` - Player's clan name. * `%advanceclans_role%` - Player's role (LEADER, COOWNER, MEMBER). * `%advanceclans_points%` - Clan's total points. * `%advanceclans_color%` - Clan's display color code. * `%clans_name%` → Shows the player's clan name. * `%clans_name_plain%` → Shows the player's clan name stripped from color codes. * `%clans_list_<#>_name%` → Shows the name of the clan at that position in the leaderboard. * `%clans_list_<#>_leader%` → Shows the leader of the clan at that position. * `%clans_list_<#>_point%` → Shows the balance of the clan at that position. Note: Replace <#> with the rank number in the leaderboard (e.g., %clans_list_1_name% for the top clan).

5. Technical Specifications

* Configuration Files: Requires Configuration Files. * Configuration Files: * `clans`: Stores name, leader name, points, color, and home location. * `members`: Stores UUID, clan name, role, and Configuration Files (prevents "null" issues). * `allies`: Stores clan alliance relationships. * Configuration Files: * `config.yml`: Core limits and permissions. * `msg.yml`: 100% translatable messages. * `gui.yml` / `settingsgui.yml`: Full GUI customization.

7. Data Saving Internal Logic

The plugin employs a multi-layered approach to data integrity and performance:

Data Storage Mechanism

* Schema Design: SQLite with Schema Design mode. This allows the plugin to write to the database while simultaneously reading from it, preventing the "database is locked" errors common in simpler plugins. * Schema Design: * `clans`: Primary table for metadata (Owner name, Points, Color, Home Location). * `members`: Linking table connecting Player UUIDs to Clan names. It includes a `last_name` column which is updated every time a player joins, ensuring that even if a player changes their name or is offline, the plugin can display their name without querying the Mojang API or Bukkit's heavy `getOfflinePlayer` methods. * `allies`: A simple relationship table for clan-to-clan alliances.

Functional Logic

* Persistence Strategy: Functions like `updatePoints`, `createClan`, and `forceDeleteClan` run on a separate thread. This means that if the database takes 100ms to save, your server's TPS stays at a perfect 20.0. * Persistence Strategy: On startup, the plugin loads all member-to-clan relationships into a `HashMap<UUID, String>`. This allows the plugin to check if a player is in a clan in Persistence Strategy without ever touching the hard drive. * Persistence Strategy: Point updates use SQL arithmetic (`SET points = points + ?`) rather than reading, modifying, and writing back. This prevents "race conditions" where two kills happening at the exact same time might overwrite each other. * Persistence Strategy: Data is saved immediately to the SQLite file upon any change. There is no risk of losing points if the server crashes unexpectedly.