BetterStasis

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 - give someone access to your rod
• /pearlunshare - 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

updates.

Player Binding Feature

The stasis system now supports binding pearls to specific players with configurable remote teleportation.

Configuration (config.yml)

Two new settings under settings.player-binding:

player-binding: # When enabled, using a rod teleports the player who bound it (not the user) # This allows remote teleportation of the bound player enable-remote-teleport: false # Set to true to enable

# When enabled, the binding is cleared after each teleport
# When disabled, the binding persists and can be used multiple times
clear-after-teleport: false    # Set to true to clear binding after use

How It Works

1. Pearl Binding: When a player binds a pearl (Shift + Right-click with fishing rod), their UUID is stored in the rod
2. Rod Display: The fishing rod now shows who bound it in the lore: "Bound by: PlayerName"
3. Remote Teleport (when enable-remote-teleport: true): - When anyone uses the fishing rod, the bound player gets teleported (not the rod user) - Both players receive feedback messages - The bound player must be online for this to work
4. Persistent Binding (when clear-after-teleport: false): - The pearl binding stays intact after teleportation - Can be used multiple times - Perfect for respawn points or safe zones

1. config.yml - Added new setting:

show-bound-indicator: true

• When true (default): Rod shows enchantment glint and lore with pearl location
• When false: Rod looks like a normal fishing rod even when a pearl is bound

2. PearlDataUtil.java - Updated binding logic:

• The bindPearlLocation method now checks the config before adding visual indicators (src/main/java/dev/xoperr/betterstasis/util/PearlDataUtil.java:64-81)
• The pearl location data is still stored in the rod's PersistentDataContainer regardless of the setting
• Visual indicators (lore and enchantment glint) are only added if show-bound-indicator: true

How to Use:

To make rods look normal when bound, just set this in your config.yml: settings: show-bound-indicator: false

The rod will still function exactly the same (you can still teleport with it), but it won't have any visual indicators that a pearl is bound to it.

Added the feature of toggling if the coords of the bearl which was binded are shown or hidden on the fishing rod New Features Added:

• /pearl coords show - Shows coordinates on fishing rods
• /pearl coords hide - Hides coordinates on fishing rods