Tags
Creators
Details
Licensed ARR
Published 8 months ago
Updated last month
All versions
1.1.10
Release
Nexus Region Manager 1.1.108 months ago 130
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Folia
Paper
Changes
Big update:
Added
- Full command tab-completion across all NRM commands:
/nrm/shop/shopedit/rental- Added tab-complete handling in fallback mode as well.
- Added shop teleport support from shop UI and command (
/shop tp <shopId>). - Added admin waypoint override for teleport target (
/shopedit waypoint [shopId]). - Added baseline override command (
/shopedit baseline [shopId]) for reset snapshots. - Added owner listing flow from My Regions (owner sale/owner rent auction workflows).
Changed
- Setup/wizard and shop flows refined for consistency and clearer progression.
- Rental/shop duration display formatting updated to avoid raw second strings.
- Sign behavior updated to support live state refresh and purchased/rented status display cycling.
- Startup/config versioning and release metadata aligned to
1.1.10.
Fixed
- Fixed economy provider auto-selection crash path when optional providers are missing.
- Fixed shop ownership handling so renting out a region does not incorrectly drop owner ownership.
- Fixed region border particle rendering to show full 3D bounds (not only bottom outline).
- Fixed multiple menu interaction/state issues where clicks became unresponsive after selection.
- Fixed command UX gaps by adding proper suggestions for subcommands and IDs.
Notes
- This release is focused on production hardening, command UX, ownership correctness, and admin tooling.
- Recommended: regenerate/merge config keys if upgrading from much older builds.
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:dXiCbisH:lS0VvVWa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dXiCbisH:lS0VvVWa"
}

