2.7.7 PreRelease

What's Changed

• added craftengine support fixed issue #9 by @SLINIcraftet204 in #12

Full Changelog: 2.7.6...2.7.7

Summary

Fixes visual issues with CraftEngine furniture graves where the additional bGraveStones BlockDisplay glow overlay could appear as a large flat texture plane.

Changes

• Adds craftEngine.suppressVanillaGlowDisplay
• Suppresses the extra Locator-Bar glow BlockDisplay only when the grave is actually using a CraftEngine furniture visual
• Keeps Locator-Bar waypoint markers and gray/gold color behavior intact
• Keeps fallback behavior to the configured vanilla graveBlock
• Bumps configVersion to 4

Notes

This does not disable CraftEngine furniture placement. It only disables the additional bGraveStones visual glow overlay for CraftEngine furniture graves.

2.7.6

What's Changed

• Revise README for server compatibility and features by @SLINIcraftet204 in #7
• fixed issue #4 in some way by @SLINIcraftet204 in #8

Full Changelog: 2.7.5...2.7.6

Added

• Added protected admin recovery tools under /graves sudo.
• Added /graves sudo inspect-nearby [radius] to inspect nearby plugin-owned visual entities.
• Added /graves sudo cleanup-nearby [radius] to remove nearby plugin-owned visual entities and resync valid visuals.
• Added /graves sudo cleanup-orphans to remove orphaned plugin-owned visual entities from loaded chunks.
• Added /graves sudo resync-visuals to restore grave blocks, holograms and locator waypoints.
• Added graves.admin.sudo permission.
• Added adminSudo config section.
• Added locatorBar.graves.rememberViewAllUntilRestart config option.

Changed

• Bumped configVersion to 3.
• Bumped messagesVersion to 2.
• /graves locatorall view-all state can now explicitly be kept until server restart or reset on disconnect through config.

Safety

• Sudo cleanup commands only target plugin-owned visual entities such as grave holograms, locator marker armor stands and locator glow displays.
• cleanup-nearby does not delete stored grave data.
• cleanup-orphans only removes plugin-owned visual entities that no longer match stored grave data.
• Destructive cleanup actions are logged to console.

[2.7.5]

What's Changed

• fixed issue #1 by @SLINIcraftet204 in #6

Full Changelog: 2.7.4...2.7.5

Summary

This PR adds the first server-platform compatibility layer for betterGraveStones.

It detects common Bukkit-compatible server platforms and applies safe feature gates where needed. Folia is detected and blocked by default because the current plugin code still uses classic Bukkit/Paper scheduler, teleport and entity access patterns.

Added

• ServerPlatform
• ServerCompatibility
• Platform detection for:
  • Folia
  • Purpur
  • Paper
  • Spigot
  • CraftBukkit/Bukkit
  • Unknown Bukkit-compatible servers
• Startup/reload platform logging
• Compatibility config section
• Safe Locator-Bar gating for unsupported platforms/versions

Config

compatibility:
  logPlatformOnStartup: true

  folia:
    disablePlugin: true

  features:
    locatorBar:
      autoDisableWhenUnsupported: true

Notes

This does not claim full Folia support yet. Folia is intentionally detected and blocked by default until a dedicated scheduler/entity adapter is added.

Closes

Closes #1

[2.7.4] added file versioning and file backup

What's Changed

• fixed issue #3 by @SLINIcraftet204 in #5

New Contributors

• @SLINIcraftet204 made their first contribution in #5

Full Changelog: 2.7.3...2.7.4

Added

• Added generated file versioning for config.yml, messages.yml, and MySQL.yml.
• Added safe startup/reload updater for generated plugin files.
• Added automatic insertion of missing config/message/database keys from bundled defaults.
• Added backup creation before generated files are changed.

Changed

• Existing user values in generated files are preserved during updates.
• Invalid or missing generated file version values are corrected defensively.
• messages.yml receives missing message keys without overwriting customized messages.

Technical

• Added GeneratedFileVersionUpdater.
• Added configVersion, messagesVersion, and mysqlConfigVersion.
• Generated file backups are written to plugins/betterGraveStones/backups/generated-files/ before modifications.

[2.7.3] added more infos to the messages and reworked some command things

Full Changelog: 2.7.2...2.7.3

Release notes

Added

• Added configurable date/time output to /graves list entries.
• Added listDateFormat to config.yml for list timestamps.
• Added number-based grave teleporting through /graves tp <list-number>.
• Added tab-completion for /graves list stored player names and /graves tp list numbers.
• Added emergencyLookDistance to control how far /graves emergency can target a grave.
• Added Modrinth Updater Notification

Changed

• /graves list now shows a readable grave number and creation time instead of only coordinates.
• Clickable teleport entries now use the visible list number instead of exposing the full grave UUID.
• /graves tp <uuid> remains available as a fallback, but normal usage is now /graves tp <list-number> after opening /graves list.
• /graves emergency no longer opens the newest grave of a player automatically. It now only opens the grave block the authorized emergency player is actively looking at.

Fixed / Improved

• Offline player names stored in graves can be resolved for admin list commands.
• Emergency recovery is safer because it requires explicitly targeting the affected grave.

[2.7.2] fixed some bugs with the locatorbar and the tabcompletion of commands

Full Changelog: 2.7.0...2.7.2

[2.7.0] better-GraveStones cleanup / DB keepalive / Locator-Bar update

Changed

• Cleaned the plugin lifecycle in GravePlugin:
  • clearer storage initialization,
  • clean storage close on reload/disable,
  • separate listener/command registration,
  • safer reload flow.
• Reworked MySqlGraveStorage:
  • no global static connection anymore,
  • validates the connection before SQL operations,
  • reconnects automatically if the DB server closed the idle connection,
  • async SELECT 1 keepalive task,
  • configurable keepalive interval in MySQL.yml,
  • safer table-prefix handling,
  • waypoint_entity_id column support.
• Cleaned SerializationUtil with try-with-resources.
• Added waypointEntityId persistence to YAML and MySQL storage.
• Added LocatorBarManager for Minecraft 1.21.6+:
  • optional player waypoint colors,
  • deterministic player colors via UUID hash,
  • optional per-player color overrides by name or UUID,
  • optional grave waypoint markers via invisible marker ArmorStands,
  • normal grave color and near grave color,
  • near-distance glowing state,
  • stale marker cleanup when chunks load.

Locator-Bar notes

This version intentionally uses only colors. It does not require or configure resource-pack textures/styles.

Player color modes in config.yml:

colorMode: "vanilla"   # leave player colors untouched
colorMode: "fixed"     # use defaultColor for every player
colorMode: "uuid_hash" # calculate one stable color from each player's UUID

Graves use color normally and nearColor when a player enters nearGlowDistance.
A real separate golden border around the locator-bar icon is not available with pure server-side colors only, so the plugin switches the grave waypoint color to gold and can enable vanilla entity glow while nearby.

Enable the feature in config.yml under locatorBar.enabled and locatorBar.graves.enabled after your server is on Minecraft/Paper/Spigot 1.21.6+.

2026-05-02: Locator-Bar player colors adjusted

• Removed texture/style based locator configuration completely.
• Player UUID colors now use a fixed safe palette.
• gray, dark_gray, gold, and yellow are reserved for grave markers and are not used by player UUID colors.
• Player defaultColor and perPlayerColors ignore reserved grave colors as a safety net.

2026-05-02: UUID gradient style added

• Added locatorBar.players.uuidHashStyle with solid and gradient.
• solid keeps the previous stable UUID-to-color behavior.
• gradient animates player waypoint colors through safe hex color pairs.
• Gradient pairs are intentionally chosen so players do not become gray, dark gray, gold, or yellow.
• Added locatorBar.players.uuidGradient.intervalTicks and steps for animation speed/smoothness.

2026-05-02: Grave waypoint marker protection

• Grave locator ArmorStands are now treated as internal static marker entities.
• Marker ArmorStands are configured as invisible, marker-sized, gravity-free, invulnerable, silent, non-collidable, non-pickup, persistent entities.
• The locator tick now repairs marker state and position regularly.
• Damage, fire/combustion, portal movement, and external teleports are cancelled for managed grave waypoint markers.
• If a command/plugin still manages to kill the marker entity, the plugin clears drops/XP and recreates the marker automatically from the stored grave data.
• Added locatorBar.graves.markerProtection config for enabling/disabling marker protection behavior.

Note: no Bukkit/Spigot plugin can make an entity absolutely immune to every possible server command or another plugin that force-removes entities after this plugin has handled events. The plugin therefore protects normal events and recreates missing/killed marker entities on the next repair cycle.

Full Changelog: https://github.com/CrayonSMP/Crayon-GraveStones/commits/2.7.0