Tags
Creators
Details
0.7.2
Compatibility
Changes
LagX 0.7.2 - Integration & Polish Update
🔧 Fixed Issues
Towny Integration Detection
- Fixed: Towny integration not being detected on servers with custom forks
- Fixed: Integration system now defaults to enabled for backward compatibility
- Works seamlessly with both standard Towny and custom forks
- No config changes required - existing configs work automatically
Color Code Display
- Fixed: Warning messages showing raw color codes (
&6&lLagX &7&l>>&r) instead of formatted colors - All warning messages now properly display with beautiful colors
- Consistent color formatting across all plugin messages
Config Version Management
- Fixed: Config version synchronization between code and YAML files
- Build-time replacement ensures version consistency
- Config version 0.2.0 properly synced
✨ New Features
Plugin Integrations System
- New configurable integrations framework in
config.yml - Towny integration enabled by default for seamless experience
- Future-ready for additional plugin integrations (map protection, etc.)
- Backward compatible with configs missing the integration section
Enhanced Integration Manager
- Smarter plugin detection and initialization
- Better defaults for common integrations
- More robust error handling and logging
📝 Configuration
New optional config section (automatically uses defaults if missing):
integrations:
towny:
enabled: true # Default: true
copyright-plugin:
enabled: false # Default: false (future feature)
🔄 Compatibility
- Minecraft: 1.20.6+
- Server: Paper, Folia
- Java: 21
- Towny: All versions (including custom forks)
📦 Installation
- Download
LagX-0.7.2.jar - Place in your server's
pluginsfolder - Restart server (or use
/lagx reloadif updating from 0.7.1) - Towny integration works automatically if Towny is installed!
🐛 Bug Reports
Found an issue? Report it on our GitHub Issues
Note: This is a polish and bugfix release. If you're upgrading from 0.7.1, your existing config will work without changes. The new integrations section is optional - the plugin uses smart defaults when it's missing.
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:avq9Azt9:nV5MzlF5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:avq9Azt9:nV5MzlF5"
}

