KeyAllZ

KeyAllZ v3.3.1

Customization update focused on titles and localization.

What's New

* Added fully customizable title messages * Supports fade in, stay duration, and fade out timing * Allows better control over announcement presentation * Added subtitle support * Send secondary messages alongside titles * Useful for extra context, rewards, or branding * Added configurable language file * Users can now edit messages according to their server needs * Makes localization and customization much easier

Improvements

* Better flexibility for server owners configuring broadcasts and announcements * Cleaner overall title handling system

KeyAllZ v3.3.0 is out!

This is one of the biggest KeyAllZ updates yet! Redis sync is now fully stable and the entire system has been heavily optimized for large Minecraft networks. Servers can now handle thousands of players across multiple servers with smooth Redis synchronization and better overall performance.

What's New

* Production-ready Redis synchronization * Non-destructive /keyallz reload * Major performance improvements * Better timer accuracy across servers * Improved async reward processing * New Redis tuning options

Reloads No Longer Reset Timers

Running /keyallz reload will now reload configs, rewards, and messages without restarting active timers. Everything continues seamlessly while applying the new changes live.

Improved Network Sync

* Better drift correction between servers * More accurate timer syncing * Fixed looping timer desync issues * Rewards now execute more reliably on high-latency networks

Fixes

* Fixed timers resetting on reload * Fixed rewards occasionally missing on follower servers * Improved Redis cleanup after timers end * Fixed duplicate command execution during leadership changes

KeyAllZ v3.3.0-beta is out

This update focuses on multi-server support. If you're running a network, timers now stay synced across all servers using Redis. No more separate timers or players switching servers to claim rewards twice.

Multi-server sync

Timers are synced across your entire network in real time. Start it on one server and it shows up everywhere with the same countdown and timing. When a timer fires, each server handles its own online players so nobody gets missed. If a server restarts mid-timer, it catches up automatically. If the server that started the timer goes down, another one takes over. Redis is required for this, but optional. Without it, the plugin works the same as before for single-server setups.

No double claiming (Redis)

Players can no longer switch servers to claim the same KeyAll multiple times. Once processed on one server, the reward is locked across the network for that cycle.

Fixes

- Console commands (non-player) running once per server instead of once per network - PLAYER console commands only running on one server - Finished timers showing as ghost entries in /keyallz - Timer recovery after restart being off - /keyallz reload not clearing state properly All fixed.

Performance

KeyAll processing has been optimized a lot for larger player counts.

Setup

redis:
  enabled: false
  host: "localhost"
  port: 6379
  password: ""
  database: 0
  # Key prefix for all Redis keys. Change this if you share Redis with other plugins.
  key-prefix: "keyallz"
  # Unique ID for this server in the cluster. Leave empty to auto-generate.
  server-id: ""

Set enabled to true and fill in your Redis details. All servers need the same Redis connection and the same KeyAll names. Rewards can differ per server.

Notes

This is a beta build bugs with redis are expected to be reported if faced.

Changelog

[3.2.1]

Added

- Periodic timer autosave (every 30 seconds) to reduce data loss on crashes/restarts. - Immediate timer persistence on admin actions: - /keyallz start - /keyallz stop - /keyallz loop - /keyallz remind - /keyallz reload - Saved timer timestamp (savedAtEpochMillis) for accurate restart recovery.

Fixed

- Fixed timers becoming Inactive after restart in common restart/crash scenarios. - Fixed looped timers restoring with wrong timing after downtime. - Fixed expired non-loop timers incorrectly restoring after long downtime. - Fixed reminder interval updates not being respected by runtime timer ticks. - Fixed reward dedupe reset edge case caused by key-name casing differences. - Fixed locale-sensitive lowercasing issues by using Locale.ROOT for key normalization.

Changed

- Timer restore now compensates for offline time: - Non-loop timers that expired while offline are skipped. - Loop timers resume at the correct point in the current cycle. - Saved timer file is no longer deleted on load; stale files are removed only when no active timers remain. - Added stronger command input validation: - Timer duration must be greater than 0. - Reminder interval cannot be negative.

Performance

- Reduced allocation/object churn in reward batch command execution. - Removed repeated RewardExecutor/FoliaLib construction inside player-batch command paths. - Optimized placeholder timer lookup from map scan to direct normalized lookup. - Reduced repeated Bukkit.getOnlinePlayers() calls within the same timer tick/end cycle.

Internal Refactor

- Cleaned up timer persistence flow with explicit persistence entrypoint. - Refactored player batch console command handling into instance-level execution for reuse and lower overhead.

Notes

- No config format migration required. - Existing commands and placeholders remain compatible.

Changes

The placeholder now returns "Inactive" if the timer is not running.