EventClockRK

Read the full EventClockRK Wiki

Overview

EventClockRK lets you automate server events using cooldowns or fixed CRON schedules. Create key giveaways, announcements and timed activities through configurable console commands.

Configure your events in YAML, choose when they run and display their countdowns through PlaceholderAPI.

Features

• Cooldown-based events and five-field UNIX CRON schedules.
• Configurable scheduler timezone, including America/Lima.
• Run schedules every N weeks using a reference date.
• Trigger all listed events or select one randomly.
• Instant events and events with an active duration.
• Advance alerts and customizable start announcements.
• Separate natural completion and cancellation messages.
• Minimum online-player requirements and world filtering.
• Execute commands once, per eligible player or per loaded world.
• Persistent YAML storage for cooldowns, active durations and completion.
• Optional PlaceholderAPI integration.
• Countdowns, next execution dates, status and progress bars.
• Legacy colors, hex colors and MiniMessage gradients.
• No database or GUI required.

Commands

Short alias: /ecrk

Administrative commands are available to OP players and the server console. There are no permission nodes to configure.

PlaceholderAPI

For an event named keyall, the following placeholders are available:

Replace keyall with your event's ID.

Text countdowns hide leading zero units by default while preserving intermediate zeros:

While an event is active, its countdown shows the remaining time until it ends.

PlaceholderAPI is optional. Install it to display these placeholders through other compatible plugins. EventClockRK registers its own expansion automatically.

Example Event

Create plugins/EventClockRK/events/keyall.yml:

Then configure plugins/EventClockRK/schedulers.yml:

This example runs every two weeks on Friday at 1:15 AM in Lima, anchored to September 11, 2026. Past occurrences are not replayed.

Keep only one top-level timezone setting when adding more schedules.

The example action sends a test message. Replace it with your reward plugin's actual command. Include %player% to execute a command once per eligible online player.

EventClockRK does not include its own crate or key system.

Installation

1. Place EventClockRK-1.0.0.jar in your server's plugins folder.
2. Start the server to generate the configuration files.
3. Create your events inside plugins/EventClockRK/events/.
4. Configure fixed schedules in schedulers.yml, if needed.
5. Run /ecrk reload.
6. Check your event with /ecrk info keyall.

To trigger the example immediately:

This command executes the event's configured actions immediately.

Configuration Files

• config.yml — Global display settings, prefix and time formats.
• messages.yml — Internal messages, status labels and time-unit labels.
• schedulers.yml — Timezone and CRON schedules.
• events/ — Your event definitions.
• data/ — Automatically saved event state. Do not edit manually.

Default plugin messages are in English and can be customized in messages.yml.

Scheduling and Restarts

• A valid scheduler reference overrides the event's cooldown.
• Cooldown-only events require a positive cooldown in seconds.
• Cooldown progress and event state persist across restarts.
• CRON occurrences missed while the server is offline are skipped.
• If a CRON occurrence lacks eligible players, that occurrence is skipped.
• If a cooldown lacks eligible players, it waits until enough players are available.
• An already active event ignores additional start attempts.
• Pausing prevents automatic starts without stopping an active duration.

Random schedules: time, date and progress placeholders are suppressed for events referenced by a random scheduler. Their status remains available.

Requirements and Compatibility

• Java 17 or newer. Use the Java version required by your server.
• Targets Paper/Spigot 1.16–1.21.x, built against the Spigot 1.16.5 API.
• Not every version in the target range has been tested on a live server.
• Folia is not supported.
• PlaceholderAPI is optional.

Updating

Stop the server, remove the previous EventClockRK jar, install the new jar and start the server again.

Keep the entire plugins/EventClockRK folder to preserve your events, schedules and saved progress.