maxHearts

I know we only have 3 downloads so far but I couldn't help picking over my code.

MaxHearts v1.1.0 — Changes and Improvements

1. UUID-based storage

   • Player max hearts are now stored by UUID, not username.
   • Prevents issues if a player changes their name.
   • Last-known name is still tracked for display purposes.

2. New data.yml file

   • Player data is stored in plugins/MaxHearts/data.yml.
   • config.yml is now only for defaults and bounds.
   • Admins no longer have to manage overrides in config.yml.

3. Legacy migration

   • Any overrides: section in config.yml is automatically migrated into data.yml.
   • Migrated once on startup; config.yml is cleaned up afterward.

4. Configurable bounds

   • Added minHearts and maxHearts in config.yml.
   • All set/give/take/transfer operations are clamped to these values.

5. Event handling cleanup

   • Switched from MONITOR to NORMAL priority in event listeners.
   • Still applies heart updates on the next tick for safety.

6. Command flexibility

   • Commands accept both player names and UUIDs.
   • Transfers can target pending names (applied once that player joins).
   • Sources must be actual players with UUIDs (to prevent ghost transfers).

7. Runtime data management

   • data.yml is created and updated automatically by the plugin.
   • Admins should not edit data.yml manually.

Overall result:

• Safer, more reliable storage of heart data.
• Cleaner config file for admins.
• Improved protection against edge cases (name changes, invalid values).
• Better code semantics for long-term maintainability.