New features:

• Added {id} placeholder to ban screen

Release Notes

Fixed

• ClassCastException in OfflineNameResolver: Fixed crash when loading legacy flat-format name cache by properly handling both old and new YAML structures
• Reload command: /bjustice reload now properly reloads both config and punishment data

Improved

• Data folder creation now handled gracefully to prevent file save errors

Release Notes - v1.0.4
Added

• Added persistent moderation audit logging.
• New audit file now records punishment lifecycle events:
  • APPLY
  • REMOVE
  • EXPIRE
• Audit entries include: timestamp, punishment ID, type, target, actor, reason, createdAt, expiresAt, and removedBy (for removals).

Changed

• Updated ban/mute punishment screens to include an appeal link.
• Unpunish flow now tracks who removed a punishment (actor-aware removal).
• Ban list command now uses /banlist with permission checks enforced.

Fixed

• Kicks are no longer shown in ban list output.
• Kicks are excluded from ban list header count.
• Permission handling verified across moderation commands:
  • ban
  • mute
  • ipban
  • ipmute
  • kick
  • warn
  • note
  • unpunish
  • banlist
  • reload

Implement OfflineNameResolver and WarnCommand functionality
- Added OfflineNameResolver class for caching player names and resolving UUIDs.
- Implemented WarnCommand class to allow users to warn players with a specified reason.
- Integrated name resolution in WarnCommand to support both UUIDs and player names.
- Enhanced error handling for loading and saving name cache.
- Updated message configurations for user feedback on command execution.