EzCountdown provides configurable countdown timers for events, launches, and maintenance windows across your server.
- Fixed date, duration, recurring, and manual countdown modes.
- Display options: action bar, boss bar (1.9+), chat, title, and scoreboard.
- PlaceholderAPI support for
%ezcountdown_<name>_days%,_hours,_minutes,_seconds, and_formatted. - Customizable messages (messages.yml), permissions, and update intervals.
- Run console commands when countdowns finish.
See docs/commands.md for the full command list and usage.
- Fixed date: Runs toward a specific date/time (e.g.
2026-01-01 00:00). - Duration: Runs for a set amount of time starting immediately (or on create if enabled).
- Manual: Uses a duration but stays stopped until
/countdown startis run. - Recurring: Repeats on the same month/day/time every year.
See docs/permissions.md for permission details.
See docs/configuration.md for configuration details and examples.
You can configure recurring countdowns to align to real-world clock boundaries and specify a timezone. Example keys in countdowns.yml:
# every 2 hours on the UTC clock: 00:00, 02:00, 04:00...
my_recurring_countdown:
type: RECURRING
align_to_clock: true
align_interval: "2h"
timezone: "UTC"
missed_run_policy: SKIP
Behavior:
align_to_clock(default:false) enables clock alignment.align_intervalaccepts duration strings like2h,1d,30m.timezoneis an IANA ZoneId (e.g.Europe/London). If omitted the plugin default zone is used.missed_run_policycontrols what happens if the server was down for one or more scheduled occurrences (defaults toSKIP).
See the full timezone reference for recommended IANA identifiers: docs/feature/timezones.md
Comprehensive documentation is available in the docs/ folder. Quick links:
-
Commands & Configuration
-
Features
-
API
/countdown create new_year 2026-01-01 00:00
You can configure a countdown to teleport all online players to a named location at the start or end:
countdowns:
my_event:
...
teleport:
start: spawn
end: arena