Skip to content

1.0.0

Choose a tag to compare

View all tags
@dmccoystephenson dmccoystephenson released this 15 Oct 01:52
v1.0.0
853425b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

1.0.0

This release closes gaps in land protection and fixes fief renaming. On a server running v0.13.1, players who are in no fief can no longer break or place blocks on fief land. Each fief's claimedLandProtected flag now decides whether that fief's own land is protected. It no longer depends on the flag of the fief the acting player belongs to. Renaming a fief now keeps its land attached to it, where before that land was left unprotected under the old name.

Changes

Land protection

  • Breaking and placing blocks on protected fief land is now refused for players who are in no fief. Before, only interactions were refused for them, so they could still break and place blocks on another fief's land (#223).
  • Whether land is protected now depends on the claimedLandProtected flag of the fief that holds the land. Turning the flag off opens that fief's own land to everyone. It no longer lets the fief's members build on other fiefs' land (#223).

Fief management

  • Renaming a fief now also renames the land it holds. Before, renamed fiefs lost their land, which stayed unprotected under the old name and went to any fief that later took that name (#222).

Upgrade notes

  • Check which fiefs have claimedLandProtected set to false. Their land is now open to everyone, including players in no fief. Before, the flag only affected what their own members could do elsewhere. Fiefs that want their land protected should set the flag back to true.
  • Land belonging to a fief renamed before this release is not moved over. It stays under the fief's old name and is unprotected. It also goes to any new fief created with that old name. Find and re-claim land of any fief renamed before this release.

Version

v0.13.1 → 1.0.0 — MAJOR. Mechanical floor from comparing the two jars: MINOR.
Judgment: Two behaviour changes in #223 can break an existing server even though they fix bugs. First, the per-fief claimedLandProtected flag now applies to the fief that holds the land, not to the player acting on it. Any fief that had this flag set to false now has land that anyone can break and place on. Second, block break and place on fief land are now refused for players who are in no fief, where before they were allowed. Changing which fief's setting counts changes what a stored setting means, so this is raised above the minor floor. #222 also changes the data written on rename but adds no migration for land orphaned by earlier renames.

  • minor: storage path changed: src/main/java/dansplugins/fiefs/data/PersistentData.java
Java API changes (informational — nothing depends on this plugin)
  • dansplugins.fiefs.data.PersistentData: added public void renameFief(dansplugins.fiefs.objects.Fief, java.lang.String);

Verification

Verified on a real Spigot server before publication; this release carries the exact jar that was verified.

  • boot gate run: booted twice on a fresh Spigot server running Minecraft 1.19.4 (11 assertions passed).
  • boot gate run: booted twice on a fresh Spigot server running Minecraft 1.21.11 (11 assertions passed).
  • boot gate run: booted twice on a fresh Spigot server running Minecraft 26.2 (11 assertions passed).
  • boot gate run: booted twice on a fresh Spigot server running Minecraft 26.3 (11 assertions passed).
  • save-compatibility gate run: data written by v0.13.1 was loaded by this release across two restarts with nothing lost (16 assertions passed).

Install with Dan's Plugin Manager: /dpm get <plugin>. How stable releases are made: Release channels.

drafted by Claude on behalf of Daniel Stephenson

Assets 3
Loading