DyClaim 1.3.0

DyClaim 1.3.0

Claim flight, fire control, closed claims and a choice to hide claim notices, plus a lighter plugin on busy servers. Existing commands, settings and claim data are kept.

Added

• Claim flight. /claim fly [on|off] lets players fly inside their own claims, and inside claims they can build in. Flight stops when they leave, comes back when they return, and fall damage is forgiven for a few seconds after flight ends in the air. Players need the new dyclaim.fly permission (OP by default). Flight from creative mode or other plugins is never taken away. Settings: claim-fly.enabled, claim-fly.allow-trusted and claim-fly.fall-protection-seconds.
• Fire control per claim. /claim fire lets fire spread and burn blocks inside a claim. Claims stay fireproof by default. The new protection.fire-spread setting works like visitor-doors: default (off), forced-value and player-toggle, with per-world overrides. Players still need build rights to light fires.
• Closed claims. /claim entry closes a claim to visitors: only owners, coowners and trusted players or groups may walk in, and other visitors are pushed out like banned players. Claims stay open by default. The new protection.visitor-entry setting has default (open), forced-value and player-toggle. Staff with dyclaim.ban.exempt can still enter.
• Better claim notices. /claim notices [on|off] lets each player hide or show claim entry and exit notices. The choice is kept across restarts. Named claims show their name in the entry notice, and walking between two named claims of the same owner now shows a notice too. The notice can also be shown as a title. Settings: notification.player-toggle, notification.show-claim-name and notification.use-title (off).
• /claim info shows the fire and visitor entry settings.

Changed

• Claim lookups use a chunk index by world and position, with no key text built for each block, movement or redstone event.
• Protection rules (PvP, explosions, doors, containers and the rest) are worked out once per world and setting after each configuration load, instead of reading the configuration on every event.
• Boundary, farmland, permission-group and bypass settings are read once per configuration load instead of on every piston, hopper, fluid, redstone, growth and interaction event.
• Configuration reads and world blacklist checks no longer wait on a lock.
• Player joins, quits and leaving a claim during a warning no longer write state.json on the server thread. Changes are saved together a second later in the background. Shutdown still saves at once.
• The claim spacing check only looks at nearby chunks instead of every claim on the server.
• The %dyclaim_total% placeholder, bStats and /claim admin diagnose count claims without copying them.
• Movement into claims checks the claim's own ban list first and skips warning lookups when there are no warnings.
• On Folia, a player's position is only published again when they move into another chunk.
• The message prefix is coloured once until it changes. Interaction block types and potion effect lists are checked from cached tables.

Upgrading

Stop the server, back up plugins/DyClaim, replace the old JAR with DyClaim-1.3.0.jar and start the server. New settings are added with defaults that keep claims as before: fire stays out, claims stay open, and only OPs can fly until you give out dyclaim.fly. Claim data and translations are kept, and the new messages are added in every language.

Full changelog: https://dynastyplugins.com/dyclaim/versions/1.3.0