All versions
2.0.0
Release
ServerSwitch 2.0.04 months ago 674
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.8–1.8.9
Platforms
Bukkit
BungeeCord
Paper
Purpur
Spigot
Velocity
Waterfall
Changes
Changelog – ServerSwitch 2.0.0
This is a major release featuring a complete overhaul of the core architecture and full support for the modern Velocity API.
New Features & Improvements
- Brand New Module System (v2.0): Introduced a completely new architecture for server features. All currently available modules (including FeatureManager, Webhooks, Rate-Limiting, Cooldown, etc.) are brand new in v2.0 and did not exist in previous versions.
- Velocity Module Evolution:
- New Configuration System: Replaced the external
ConfigurationNodedependency with a faster, custom-builtSimpleYamlConfigparser. - Full YAML Support: Seamlessly handles nested values and YAML lists (e.g., for blacklists and webhooks).
- New Configuration System: Replaced the external
- Modern API Compliance:
- Resolved all deprecation warnings in the Spigot module (
PlayerLoginEvent.disallow, etc.) while maintaining full compatibility from Minecraft 1.8 to 1.21. - Updated BungeeCord to use modern
TextComponentconstructors, reducing console clutter.
- Resolved all deprecation warnings in the Spigot module (
Bug Fixes
- Fixed Proxy Join Detection: Resolved "Direct join detected" false positives by increasing the database ticket timeout and optimizing the registration order of event listeners.
- Update Logic Improvement: Fixed the update checker to correctly recognize v2.0.0 as a separate, newer branch, preventing accidental downgrades to 1.3.x.
- BungeeCord Stability: Fixed potential NullPointerExceptions during database initializations.
- Resolved a critical
NullPointerExceptionwhen loading empty configuration nodes in the Velocity module. - Fixed method ambiguity in the configuration loader, ensuring accurate property retrieval.
- Corrected syntax errors in the database auto-delete timer and update checker.
- Fixed type conversion issues between
SimpleYamlConfigand legacy configuration nodes.
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:nLpQDoDu:gfBjKb1S"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nLpQDoDu:gfBjKb1S"
}

