GPExpansion v1.1.7

Changes

Ban Enforcement Refactor

• Extracted ejection logic into reusable ejectFromClaim method
• Added getClaimMinY / getClaimMaxY helpers to GPBridge for vertical bounds
• Simplified BanEnforcementListener using the new GPBridge methods
• Added banlist subcommand support in tab completion and command list

Bug Fixes

• Config overwrite on restart: Fixed a bug where the Config class and VersionManager operated on separate in-memory configs. When VersionManager called plugin.saveConfig(), it would overwrite disk changes made by the Config class — resetting values like claim-flight.passive-mode to their defaults on server restart.
• Prevent repeated config backups: ensureVersion112Structure() now only runs when the config version is older than 1.1.2, preventing unnecessary backup files from being created on every server restart.

Migration

If you had the 1.1.2 config migration bug and ended up with multiple config.yml.backup_* files:

1. The oldest backup is your pre-1.1.2 config (before any migration).
2. The second oldest is your first post-migration 1.1.2 config (before the repeated backup bug kicked in).
3. Any newer backups were created unintentionally each restart because the defaults: section was missing from the migrated file, causing ensureVersion112Structure() to re-trigger. With this fix, that no longer happens.

You can safely delete all backup files except the second oldest (which preserves your migrated config if anything goes wrong). If you prefer, you can also manually re-apply any custom config values like claim-flight.passive-mode: true — they will persist across restarts now.