GPExpansion v1.0.8

Bug Fixes

Config Migration Fix

Fixed a critical bug in the player-commands section migration that could corrupt config.yml:

• The ensurePlayerCommandPresent() method now properly inserts new entries immediately after the player-commands: header
• Previously, the insertion logic could place entries at incorrect indentation levels, causing YAML parse errors
• This fixes the InvalidConfigurationException: expected <block end>, but found '-' error during plugin startup

Technical Changes

• VersionManager.java: Rewrote ensurePlayerCommandPresent() to:
  • Detect the player-commands: header with proper regex matching
  • Preserve existing indentation structure
  • Insert entries immediately after the header before existing list items
  • Add proper logging for insertion failures

Migration

If your config.yml was corrupted by v1.0.7's migration:

1. Stop your server
2. Delete or rename plugins/GPExpansion/config.yml
3. Start the server - a fresh config will be generated
4. Re-apply your custom settings from backup

Alternatively, manually fix the YAML structure ensuring player-commands entries are indented with 2 spaces:

player-commands:
  - claimfly.use
  - claims

Files Changed

• src/main/java/codes/castled/gpexpansion/config/VersionManager.java

Notes

• No new features in this release - strictly a bugfix for the config migration
• All existing claim flight functionality remains unchanged
• PlaceholderAPI placeholders, admin commands, and passive claim flight mode work as documented in v1.0.7