Tags
Creators
Details
1.1.2-1
Compatibility
Changes
[1.1.2-1] - 2026-01-07
Added
-
New
/rwadmin reloadcommand - Dedicated reload command with enhanced feedback- Displays reload time in milliseconds
- Reports number of reset timers cleared
- Shows cached worlds cleared count
- Confirms config cache rebuild status
-
New
/rwadmin test <feature>command - Comprehensive testing system for diagnosticscache- View world and config cache contents with entry countstimer- Display next reset times for all worlds (shows remaining hours/minutes)performance- Show operation performance metrics (teleport, reset timings)tps- Check current server TPS with color-coded health indicators (green/yellow/red)config- Verify configuration loading for all worlds (displays name, auto-reset status, interval/time_of_day mode)
-
Enhanced tab completion - Added full tab completion support for
/rwadminsubcommands and test features
Improved
- Reload command feedback - More detailed output showing exactly what was cleared and recalculated
- World cache management - Reload now properly clears world cache in addition to config cache and reset timers
- Admin panel access -
/rwadminwith no arguments opens admin panel, or use/rwadmin panelexplicitly - Console compatibility - Reload and test commands now work from console, not just in-game
Fixed
- Continued fix from v1.1.1: Reset timers properly clear on reload, ensuring
time_of_daychanges take effect immediately
Technical
- Refactored command handler to support subcommands (panel, reload, test)
- Added dedicated test methods for each diagnostic feature
- Updated ResourceTabCompleter to handle both
/resourceand/rwadmincommands - Improved error handling and permission checks for admin commands
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:ELVXMw22:NXkBpVFC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ELVXMw22:NXkBpVFC"
}

