Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated 3 days ago
All versions
3.9.0
Release
AlixSystem 3.9.04 months ago 379
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
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
- Added 26.2 support
- Drastically reduced additional latency caused by Alix during join
- Fixed several errors causing random disconnects to players
- Enhanced bot attack & DDoS detection algorithms (Some new ones are still in production)
- Optimized several critical parts of connection handling
- Added automatic HAProxy support
- Reduced the firewall's memory footprint & introduced time-based firewall entries
- Added Panic Mode, which allows only already-registered players to join, activated whenever suspicious network activity is detected
- Players will now, by default, be sent to the virtual limbo for login, if possible, in order to reduce main server pressure. If this option causes issues or isn't desired, it can be turned off at 'virtual-limbo-login' in config.yml
- Enhanced automatic host recognition, now accounting for a reverse-proxy
- Added the ability to configure whether users with differently-cased, but ignoring case equal nicknames, should be allowed to join
- Reworked Alix's Fast Unsafe Epoll init mechanic
- Added atomic file writes & graceful continues at read fail
- Fixed 'Already connecting (...)' sometimes appearing for players
- Premium requests are now always cached, reducing rate limits
- The virtual limbo can no longer be turned off, due to the extreme optimization and functionality it provides. As such, manual visual captcha should no longer ever appear for any player
- Fixed several virtual limbo issues, related to a read never completing
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:dXkFpOAK:mJQeAbBU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dXkFpOAK:mJQeAbBU"
}

