Tags
Creators
Details
1.2.0
Compatibility
Changes
Advanced whitelist management system with UUID support and enhanced reliability!
What's New in v1.2.0:
- UUID-Based Whitelist System: Advanced player verification for licensed servers
- Nickname Change Protection: Players stay whitelisted even after changing names
- Enhanced Data Reliability: Guaranteed data integrity across plugin reloads
- Universal Compatibility: Works seamlessly across all server types
UUID System Features:
- Smart Verification: Checks UUID first, falls back to nickname for compatibility
- Automatic Updates: Real-time synchronization of player data on login
- Migration Support: Automatic upgrade from legacy nickname-only entries
- Mode Awareness: Different behavior for licensed vs offline servers
Licensed Servers (online-mode=true):
- Players remain whitelisted after nickname changes
- Protection against nickname spoofing
- Automatic UUID registration on first join
Offline Servers (online-mode=false):
- Classic nickname-based verification
- Full backward compatibility
- Simple and predictable behavior
Reliability Improvements:
- Fixed data loss issues during plugin reloads
- Enhanced file handling and error recovery
- Synchronized operations preventing corruption
- Robust configuration parsing
Features:
- Complete whitelist management with in-game commands
- Discord bot integration with modern slash commands
- Multi-language support (13 languages)
- Cross-platform compatibility (Bukkit/Paper/Velocity)
- Permission system compatibility
- Minecraft 1.21.x support
Installation:
For Bukkit/Paper servers:
- Download the jar file below
- Place in your server's
pluginsfolder - Restart server
- Configure in
plugins/NekoList/config.yml
For Velocity proxy:
- Download the jar file below
- Place in Velocity's
pluginsfolder - Restart proxy
- Configure in
plugins/NekoList/config.yml
Upgrade Note: This version maintains full compatibility with previous configurations. Existing whitelists will be automatically upgraded to the new format.
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:MUXv6Dpt:H35rv32C"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MUXv6Dpt:H35rv32C"
}

