Tags
Creators
Details
1.5.0
Compatibility
Changes
BetterStasis v1.4.1 - Economy, Sharing & Customization
Three new features: economy integration, pearl sharing, and toggleable rod info.
Economy Integration
Vault support for charging players to bind and teleport.
How it works:
- Flat cost to bind a pearl to a rod
- Teleport cost = base cost + (distance × cost per block), capped at max
- Cross-world teleports cost more
- If teleport fails, you get refunded automatically
- Without Vault installed, everything still works - economy features just won't be active
Config: economy: enabled: false teleport: base-cost: 10.0 cost-per-block: 0.5 max-cost: 1000.0 binding: cost: 5.0
Needs Vault + any economy plugin (EssentialsX, CMI, etc.)
Pearl Sharing
Share your bound rods with other players so they can teleport too.
Commands:
- /pearlshare <player> - give someone access to your rod
- /pearlunshare <player> - remove their access
- /pearlshared - see who can use your rod
Max 5 shared players by default (configurable). Both you and shared players get charged for teleports if economy is on. Rod lore shows how many people it's shared with.
Permission: betterstasis.share (default: true)
Toggleable Rod Info
Hide/show the coordinates and enchantment glint on your rods.
Command:
- /pearltoggle - switch between hidden and visible
Rod still works when hidden - this is purely cosmetic. Good for keeping inventory clean or hiding pearl locations from other players.
Permission: betterstasis.toggle (default: true)
Technical Stuff
All data stored in rod's PDC. Old rods without an owner can be used by anyone (backward compatible). Everything is config-driven and optional.
New config sections: settings: player-binding: clear-after-teleport: true pearl-sharing: max-shared-players: 5
Dependencies:
- Vault API (optional, soft-depend)
Changelog
Added:
- Vault economy integration
- Pearl sharing system + 3 commands
- Rod info toggle command
- Owner assignment on binding
- Permission checks for rod usage
- Sharing count in lore
- Refunds on failed teleports
Modified:
- Binding now sets owner
- Teleport checks permissions first
- Lore includes sharing info
- Clearing removes all new data
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:Gc9b9xGA:4GYbC8XQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Gc9b9xGA:4GYbC8XQ"
}

