Tags
Creators
Details
1.5
Compatibility
Changes
CraftersBan ā Full Network Support & Universal JAR
š Network Support (BungeeCord, Waterfall & Velocity)
CraftersBan now ships as a single universal JAR that automatically detects the environment it runs in ā whether it's a standalone Spigot server or a proxy ā eliminating the need to install separate versions for each platform.
Supported proxy platforms:
- BungeeCord
- Waterfall
- Velocity
š What's New
Universal JAR & Auto-Detection
- A single JAR file now covers all platforms: Spigot, BungeeCord, Waterfall and Velocity.
- The plugin automatically detects its runtime environment on startup and loads the appropriate modules.
Network-Wide Punishment Sync
- Punishments are synchronized across all servers through a shared database.
- A ban applied on one server is automatically enforced across the entire network in real time.
Network-Wide Punishment Broadcasting
- Staff members on any server are notified in real time whenever a punishment is applied or revoked anywhere on the network.
Network Lockdown
- Lockdown mode now operates at the network level.
- A single command blocks access to all servers on the network simultaneously.
New proxy-config.yml
- Dedicated configuration file for proxy environments.
- Controls messaging channels, target servers and other proxy-specific behavior.
Simplified Database Support
- Removed support for PostgreSQL, MariaDB and SQLite.
- Supported databases are now H2 (local mode) and MySQL (network mode) only.
- This simplifies maintenance and reduces the final JAR size.
Independent ID System per Sanction Type
- Each sanction type (ban, mute, warn, kick, etc.) now has its own independent ID counter starting from 1.
- Makes it easier to identify and manage sanctions without confusion between types.
Warnings Are Now Permanent
- Warnings (
warn) no longer support temporary durations. - All warnings are permanent until manually revoked by a staff member.
šļø Database Overview
| Mode | Database |
|---|---|
| Local (single server) | H2 |
| Network (multi-server) | MySQL |
These changes lay the foundation for CraftersBan to operate reliably in production network environments, with a focus on consistency, simplicity and real-time coordination across servers.
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:89MtK2xN:KOLO0XhP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:89MtK2xN:KOLO0XhP"
}

