Flight, warps & favourites

Claim Flight

Players can fly within their own claims for a limited time:

/claim fly

Toggles flight mode. When active, a timer counts down your remaining fly time (displayed in the action bar). When the timer runs out or you leave your claim, flight is disabled and you are gently lowered to the ground.

Fly time is a per-player balance, not a permission node: set or top it up with /scs player <player> set-fly <seconds> and /scs player <player> add-fly <seconds> (vote rewards, crates…), and choose the starting value for new players with players.default.fly in config.yml.
/claim auto-fly automatically enables flight when you enter your claims and disables it when you leave.
Fly time recharges when you are not flying (configurable).

Unlimited fly time

The claim.fly.infinite permission (default false, declared with that exact prefix — not scs.) overrides the per-player fly limit. Holders fly indefinitely inside their own claims; the action-bar timer is replaced with the infinity symbol. Convenient for staff or top-tier donors.

Respawn in Claim

Players can choose to respawn inside one of their own claims instead of the server's default spawn or their bed:

/claim respawn

Must be executed while standing in one of your own claims. The claim's spawn location (set with /claim setspawn) becomes the player's respawn point on death. Running the command again in the same claim removes the setting.

The feature must be enabled server-side before players can use it:

claims:
  respawn-in-claim:
    enabled: true

How it survives edge cases

The plugin stores the claim's numeric id (not its name) in the player's data. Consequences:

Claim renamed — respawn keeps working; the name isn't used.
Claim deleted or transferred to someone else — the respawn silently falls back to the server default on next death. No cleanup is needed; the stale id is harmless because MySQL's auto-increment is monotonic and the id is never reused.
Claim's world unloaded — same fallback to server default.
Spawn point moved with /claim setspawn — respawn uses the updated location automatically.

Return to Last Claim

Quickly teleport back to the last claim you walked into during your current session:

/claim back

History is kept in memory only — it resets when you log out. The command teleports you to the claim's spawn point, and it honors the same teleport delay / cooldown settings as /claim tp.

"Last claim you walked into" means the most recent claim boundary you crossed entering. Walking back out of your own claim, or standing still, doesn't update the history.

Restricting the scope

A config toggle controls which claims /claim back can teleport to:

claims:
  claim-back:
    only-own-claims: false

false (default) — any claim the player walked into this session.
true — only claims owned by the player; entries into other players' claims are simply ignored at teleport time.

The remembered claim id is recorded the same way regardless of this setting; the setting is consulted at teleport time, so admins can change it at runtime without clearing any state.

Favourites

Players can bookmark claims they care about so they float to the top of the list and carry a ★ marker. Works on both Java and Bedrock.

How to toggle

/claim favorite while standing in a claim.
/claim favorite <name> for a claim you own.
Inside /claim list (Java): shift-click the claim head.
Inside /claim list (Bedrock): tap the Manage favorites button at the top.

Viewing favourites

/claim favorites opens a GUI filtered to your favourites only (Java or Bedrock variant, auto-detected).
Inside /claim list, the top button on Bedrock and the ★ marker on Java make it easy to spot them.

Where it's stored

The favourite list lives in PlayerData.settings["favorite-claims"] as a simple array of claim ids — no new table, no schema migration. Deleted claim ids are lazily pruned the next time the favourites are consulted.

API

Plugins can read or mutate favourites through the public API:

api.isFavorite(playerUuid, claimId);
api.addFavorite(playerUuid, claim);     // fires ClaimFavoriteEvent
api.removeFavorite(playerUuid, claim);  // fires ClaimFavoriteEvent
api.getFavoriteClaimIds(playerUuid);
api.getFavoriteClaims(playerUuid);

Both mutators fire ClaimFavoriteEvent with a FAVORITE or UNFAVORITE action, so other plugins can react (e.g. persisting to an external dashboard).

Public Warps

Any claim can be opened as a public warp so other players can teleport to it via /claim visit. Useful for public shops, community farms, contest zones, or simply a "front door" to a base — no extra player-warps plugin needed.

How to open a warp

Stand in your claim, run /claim settings, click the Public warp toggle (ender pearl icon). The warp's teleport point is the claim's spawn — change it with /claim setspawn.

Charging a visit fee (optional)

Owners can charge visitors a Vault fee, credited directly to the owner (even when offline) on every /claim visit. Since 2.7.1 the fee is only taken once the teleport actually happened — a visit cancelled by moving during the teleport delay costs nothing:

/claim setvisitprice <amount>     # 0 = free

The following players never pay and can also access closed warps:

The claim's OWNER, MEMBER, MODERATOR and any custom role member
Players with scs.admin
Players with scs.bypass.warp-cost

Banned players are always blocked, regardless of the rules above.

Visiting other players' warps

/claim warps                          # paginated GUI: every player with at least one open warp
/claim warps <player>                 # shortcut: jump straight to that player's warps
/claim visit <player>                 # same as the line above
/claim visit <player> <claim>         # direct teleport (with delay/cooldown like /claim tp)

Tab-completion resolves offline player names from the cache, so you don't need the target online. Both /claim warps <player> and /claim visit <player> error out cleanly when the target has no open public warps instead of opening an empty menu.

Limits per rank

Two limits keep warps under control, both configurable server-wide and overridable per rank: (2.7.1)

claims:
  warps:
    max-warps: 0          # claims a player may keep open as warps at once (0 = unlimited)
    min-visit-price: 0.0  # lowest price an owner may set (0 = free visits allowed)

Permission	Effect
`scs.limit.warps.<n>`	How many warps the player may keep open. Highest value wins; `scs.limit.warps.*` = unlimited. Closing a warp is always allowed, so lowering the limit never breaks an existing setup.
`scs.limit.min-visit-price.<value>`	Lowest visit price the player may set. Lowest value wins, so a VIP rank can undercut the others.

The warp count is checked against the owner of the claim, so a moderator opening a warp on someone else's claim is checked against that owner's allowance. /scs player <player> set-max-warps <n> sets it for one player.

Defaults

Closed by default. Configure defaults applied to every new claim in config.yml under claims.default:

claims:
  default:
    warp: false        # public warp closed
    visitPrice: 0.0    # 0 = free

Admin override

Server staff with scs.admin.forcewarp can force-close (or open) any player's warp:

/scs forceWarp <player> <claim>                          # standalone form
/scs player <player> manage-claim <claim> forceWarp       # via the player-management flow
/scs player <player> manage-claim * forceWarp             # toggle every claim of the player

Toggling a warp on/off fires ClaimWarpToggleEvent (cancellable). Teleports via /claim visit fire ClaimVisitEvent after the ban/warp-closed checks and before the balance check + TP, so anti-grief or custom-rule plugins can veto on the fly. See the API README.