2.0.0.0-alpha

The version on the Alpha channel might be unstable. This version is for early testing; please report any issues promptly.

The plugin is being re-architected into a platform-agnostic core (common/, core/) with thin platform shims (bukkit/, fabric/).
- All block / dimension identifiers now use the canonical Minecraft namespace format (minecraft:diamond_ore, minecraft:water, minecraft:air, minecraft:cave_air, minecraft:ancient_debris). World folder names in xray.worlds and the group file names (overworld, nether, end) are preserved — only the contents are normalized.
- The Bukkit platform translates World.Environment to the canonical id at runtime, so the same config.yml works regardless of how the server admin named the on-disk folders.
- The v1 code path under src/main/legacy/ is preserved for reference but is no longer wired into plugin.yml; BukkitPlatform is the only entry point.

v2 now auto-completes user config.yml and per-world Configuration/<group>.yml against the JAR defaults on startup, so upgrading the plugin no longer requires manual config.yml cleanup.
A new _config-version key in every YAML file (main config and each group file) drives an automatic back-up-and-replace upgrade path: when a user's version is older than the JAR's, the file is saved as <name>-<yyyy-MM-dd>.yml.bak and seeded with the JAR default. The merge then fills in any keys added between the user's version and the latest.
The merge step counts the number of leaf keys it added and logs a summary line, e.g. [Merger] config.yml: filled 5 missing key(s) from defaults. No log is emitted in the steady state, so logs stay quiet.
A separate Created <file> from default line is emitted on the first run when the user file doesn't exist yet.
A new eager load of group configs in BukkitPlatform.onEnable() ensures the per-world files are copied from the JAR on fresh install and the in-memory CoreConfig is populated before the first mining event.

v1 → v2 config migration: stale user config.yml would silently keep the old layout, causing v2 to fall back to defaults at the call sites without ever updating the file on disk. Root cause was a MemorySection ↔ Map mismatch between Bukkit's YamlConfiguration and the core merger's instanceof Map checks, plus a missing _config-version upgrade path on the main config. Both are now fixed.
Group config files were not being created on fresh install (only on the first mining event) — the eager loadGroupConfigs() call in BukkitPlatform.onEnable() fixes this.
/minertrack reload was serving the previous 5-second-cached config instead of the freshly-merged one — the cache is now explicitly cleared before reloading.

BukkitAdapter.reloadConfig() no longer calls plugin.reloadConfig(). v2 reads config.yml via the platform-agnostic ConfigMerger, not Bukkit's JavaPlugin#getConfig(), so the legacy reload call was a no-op.
The webhook custom-JSON template in config.yml had a stray quote ("world": %world%',); now properly quoted as "world": "%world%" so the payload is valid JSON.

Recommend to rebuild the config.yml and the Configuration/*.yml files after upgrading.

MinerTrack Anti XRay