Skip to content

Releases: cjburkey01/ClaimChunk

0.0.25-FIX1

25 May 06:44
3962978
Compare
Choose a tag to compare
0.0.25-FIX1 Pre-release
Pre-release

Fixes crash on startup from the /plugins/ClaimChunk/data folder not existing on first launch :)

0.0.25

24 May 20:09
110cb60
Compare
Choose a tag to compare
0.0.25 Pre-release
Pre-release

This update fixes, once and for all, the data loss issues we've been seeing
since I first created this plugin!

Migration:

  • Should not require any extra work, keep your config the same for at least the first run.
  • 0.0.26 will remove the database section of the config, but leave it be for your first launch to make sure old data loads.
  • Prior data from JSON and from MySQL will be converted automatically to the SQLite data file, and JSON backups will be made for you in the /plugins/ClaimChunk/data directory.

0.0.24-RC1

06 May 05:16
f7f263b
Compare
Choose a tag to compare
0.0.24-RC1 Pre-release
Pre-release

Note: The messages.json and world.txt files WILL need to be recreated due to new additions to them in this update.
For English language, this can be done by deleting them and running the server. Remember to transfer any custom config
to the new world.txt files after they are recreated.

Major thanks to @AlexFF000 for contributing this entire release!

This update allows individual permissions to be granted on a per-chunk basis. These changes required a major overhaul
of the internal workings of the plugin. The commands have changed, and there have been some changes to the format used
to store the data.

Players will not need to make any changes to their claims as a result of this update; the data conversion process will
convert any existing accesses in such a way that they will continue to function as they did in 0.0.23.

Changes:

  • Access is now granted on a per-chunk basis, a chunk owner can grant another player access to only specific chunks
    rather than all of their chunks.
    • When the data is converted from the 0.0.23 format, a player that has previously been given access by a chunk owner
      will continue to have access to all the owner's chunks.
  • Players are now granted specific permissions on the chunks that they have access to (so for instance, a player could
    be granted permission to place blocks in a chunk, but not break them).
    • These permissions are:
      • break: Allow the player to break blocks
      • place: Allow the player to place blocks
      • doors: Allow the player to open / close doors and trapdoors
      • redstone: Allow the player to press buttons, levers, pressure plates etc...
      • interactVehicles: Allow the player to interact with mine carts and boats
      • interactEntities: Allow the player to interact with other entities (also allow the player to throw ender pearls
        even if preventPearlFromClaims is true in the world profile)
      • interactBlocks: Allow the player to interact with blocks
      • useContainers: Allow the player to open:
        • Chests
        • Trapped chests
        • Barrels
        • Furnaces
        • Dispensers and droppers
        • Hoppers
        • Brewing stands
  • Commands:
    • The changes have involved significant changes to the /chunk access command; it has now been split into three
      commands:
      • /chunk access <player> [break:true/false] [place:true/false] [doors:true/false] [redstone:true/false] [interactVehicles:true/false] [interactEntities:true/false] [interactBlocks:true/false] [useContainers:true/false] [allChunks:true/false]
        • Give a player permissions on a chunk (or modify their existing permissions)
        • All arguments except player are optional, and can be provided in any order
        • If allChunks:true is provided, the changes will be made to all the executing player's chunks. If false
          (the default) the changes will apply only to the chunk the player is currently standing in (if it belongs
          to them)
        • Any permissions not specified will retain their existing values (e.g. if the command is run without the doors
          option, the player's existing doors permission will remain unchanged) or will default to true if the player does
          not have access to the chunk already.
        • usage example: /chunk access examplePlayer break:true place:false allChunks:true
      • /chunk checkaccess [<player>]
        • List the permissions the given player has on the chunk where the executor is standing
        • If no player is provided, lists the permissions of all players with access to the chunk
      • /chunk revokeaccess <player> [ALL CHUNKS? true/false]
        • Revoke the given player's access to the chunk
        • If all chunks is true, the player's access will be revoked from all the executor's chunks. Otherwise, only the
          one they are standing in (if they are the owner)
        • Usage example: /chunk revokeaccess examplePlayer false
  • Removed "am_trusted" placeholder
  • Added new "CONTAINER" block class
  • Added trapdoors to "DOOR" block class
  • Added boats to "VEHICLES" entity class
  • Changed default world profile permissions for players in claimed chunks who have not been granted access:
    • Interacting with vehicles and monsters is now disallowed
    • Damaging monsters is now disallowed
    • Interacting with redstone is now disallowed

0.0.23-RC8

03 Aug 00:45
0c3fb15
Compare
Choose a tag to compare
0.0.23-RC8 Pre-release
Pre-release

For all the other changes pertaining to 0.0.23, see the 0.0.23-RC1, 0.0.23-RC2, 0.0.23-RC3, 0.0.23-RC4, 0.0.23-RC5, 0.0.23-RC6, and 0.0.23-RC7 releases.

Changes:

  • Slightly change boolean parsing for commands
  • Add block class for signs and add pressure plates to the redstone class
  • Try to fix some WorldGuard errors
  • Add enderpearl protection
  • Change some localization
  • Fix placeholders being required sometimes(?)
  • Update the update checker! (To use Java 11's new HTTP client thingy)
  • Add minecart protection class (VEHICLES)

As always please report any bugs (or minor changes that may still need to be made) you find to the GitHub issue tracker or our Discord server.

0.0.23-RC7

08 Feb 19:33
9a0216f
Compare
Choose a tag to compare
0.0.23-RC7 Pre-release
Pre-release

For all the other changes pertaining to 0.0.23, see the 0.0.23-RC1, 0.0.23-RC2, 0.0.23-RC3, 0.0.23-RC4, 0.0.23-RC5, and 0.0.23-RC6 releases.

Changes:

  • Add translation keys for command arguments.

Main remaining changes that need to be made before 0.0.23 is fully released:

  • Proper PvP support (the current support doesn't leave much to customizability).

As always please report any bugs (or minor changes that may still need to be made) you find to the GitHub issue tracker or our Discord server.

0.0.23-RC6

04 Feb 22:01
eecd471
Compare
Choose a tag to compare
0.0.23-RC6 Pre-release
Pre-release

For all the other changes pertaining to 0.0.23, see the 0.0.23-RC1, 0.0.23-RC2, 0.0.23-RC3, 0.0.23-RC4, and 0.0.23-RC5 releases.

Changes:

  • Add DOOR block class

Main remaining changes that need to be made before 0.0.23 is fully released:

  • Proper PvP support (the current support doesn't leave much to customizability).

As always please report any bugs (or minor changes that may still need to be made) you find to the GitHub issue tracker or our Discord server.

0.0.23-RC5

30 Jan 23:02
c9b6211
Compare
Choose a tag to compare
0.0.23-RC5 Pre-release
Pre-release

For all the other changes pertaining to 0.0.23, see the 0.0.23-RC1, 0.0.23-RC2, 0.0.23-RC3,and 0.0.23-RC4 releases.

Changes:

  • Downgrade to Java 16 (Java 17 becomes too restrictive for older version support)
    • It should be noted that ClaimChunk will always try to be up-to-date with Spigot or Minecraft API changes. Generally, new versions should support the previous release or two, but unless major issues arise, there aren't likely to be updates for older versions of the game.
  • Make some internal structural changes (Most APIs should be safe, but be sure to double-check that things still function as intended.
  • Disable debug spam being overridden in versions with an extra marker (such as snapshot or RC).
  • Add my_remaining_claims placeholder that displays the number of claims a player can make
    • (Provides the value of my_max_claims - my_claims)

Main remaining changes that need to be made before 0.0.23 is fully released:

  • Proper PvP support (the current support doesn't leave much to customizability).

As always please report any bugs (or minor changes that may still need to be made) you find to the GitHub issue tracker or our Discord server.

0.0.23-RC4

07 Jan 00:36
cdba7c7
Compare
Choose a tag to compare
0.0.23-RC4 Pre-release
Pre-release

For all the other changes pertaining to 0.0.23, see the 0.0.23-RC1, 0.0.23-RC2, and 0.0.23-RC3 releases.

Changes:

  • Remove unused debug from the log section of the config file as it was unused.
  • Update to Java 17.
  • Fix plugin reloading (fingers crossed! /chunk admin reload should work!).
  • Try to fix dragon eggs teleporting from claimed chunks.
  • Add preventAdjacent list to world profiles to prevent chest connections if owned by different players (or unclaimed into claimed).
  • If a message from the messages.json file is empty, it won't be sent.

As always please report any bugs you find to the GitHub issue tracker or our Discord server.

0.0.23-RC3

21 Dec 18:29
9c88fd1
Compare
Choose a tag to compare
0.0.23-RC3 Pre-release
Pre-release

For all the other changes pertaining to 0.0.23, see the 0.0.23-RC1 changelog and the 0.0.23-RC2 changelog

Changes:

  • Update to the latest version of the bStats Metrics class
  • Fix null pointer when loading plugin and not converting old config values.

As always please report any bugs you find to the GitHub issue tracker or our Discord server.

0.0.23-RC2

19 Dec 03:10
ba349ae
Compare
Choose a tag to compare
0.0.23-RC2 Pre-release
Pre-release

For all the other changes pertaining to 0.0.23, see the 0.0.23-RC1 changelog

Changes:

  • Update to Spigot 1.18.1
  • Add config conversion!
    • Config values under the protection category of the config should be automatically converted and removed from your config.yml files.
  • Reduce debug spam

As always please report any bugs you find to the GitHub issue tracker or our Discord server.