1.0.0
Compatibility
Required content
Changes
[1.0.0]
Added
-
Initial Release of XFWorldLocker (XFWL)
-
World Area Protection System
- Define rectangular areas using X1,Z1 and X2,Z2 coordinates
- Automatic teleportation when players exit defined areas
- Y-coordinate independent protection (full height)
-
Advanced World Restrictions
- Block breaking/placing control
- Player interaction management
- Mob spawning control with automatic cleanup
- Player damage control (can be completely disabled)
- Explosion protection (except in creative mode)
-
Player Effects System
- Custom potion effects per world
- Automatic application on world entry
- Automatic removal on world exit
- Configurable effect amplifiers
-
Dynamic Command System
- Custom teleportation commands for each world
- Multiple aliases support
- Optional permission requirements
- Automatic command registration
-
Multi-language Support
- Separate
language.ymlconfiguration file - All messages fully customizable
- ActionBar and chat message support
- Color code support with
&symbol - Dynamic placeholder system
- Separate
-
Administrative Tools
/xfwl reload- Reload configuration/xfwl help- Show help information/xfwl version- Display plugin version/lock <worldname>- Instant world protection
-
Smart Entity Management
- Always protect Villagers and NPCs
- Preserve Armor Stands and Item Frames
- FancyNPCs plugin integration
- Intelligent mob cleanup system
-
Performance Optimizations
- Efficient area checking algorithms
- Minimal server performance impact
- Asynchronous update checking
- Smart event handling
-
Creative Mode Support
- Creative players can bypass block restrictions
- Explosions work near creative players
- Enhanced building capabilities for administrators
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:BsmzrLHh:Pm4SAKGe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BsmzrLHh:Pm4SAKGe"
}

