CustomDeathMessages v1.3 Changelog

This release addresses critical issues with configuration reloading, cross-world sound broadcasting, and localization consistency. Server owners upgrading from v1.2 should review the notes below before deployment.

Bug Fixes

• Fixed a critical issue where /cdmreload would unregister all event listeners without reinitializing them. This caused the plugin to stop intercepting player deaths, resulting in vanilla death messages appearing and making configuration changes appear ignored or reset.
• Resolved an issue with the GLOBAL sound broadcast mode. Sounds were previously anchored to the victim's coordinates, causing distance-based attenuation and preventing playback for players in different worlds (particularly noticeable in Multiverse environments). Global sounds now play directly at each recipient's location, ensuring consistent server-wide audio.
• Fixed configuration validation during reloads to properly abort on critical YAML parsing errors, preventing broken plugin states from malformed configuration files.

Localization & Translations

• Corrected missing, inconsistent, and improperly formatted translation keys across messages.yml and internal system messages.
• Standardized language formatting and improved fallback strings to ensure reliable multi-language server support.
• Fixed color code parsing in localized messages to maintain consistent formatting across all supported languages.

Technical Improvements

• Overhauled ReloadManager to safely reinitialize all event listeners, formatters, and dependency references during hot-reloads.
• Updated BroadcastManager to dynamically adjust sound origin based on the configured broadcast mode. GLOBAL and VICTIM_ONLY now use recipient coordinates, while WORLD and RADIUS retain victim coordinates for positional audio.
• Improved internal caching and validation routines for configuration and message files.

Upgrade Notes

• A full server restart is recommended when upgrading from v1.2 to clear any lingering listener states from previous reload attempts.
• If you maintain custom translations, review the updated config.yml template to ensure all corrected keys are properly merged.
• The /cdmreload command is now fully functional and safe for production use. Configuration changes will apply immediately without requiring a server restart.

For detailed technical changes, refer to the commit history or source repository.