SRVCron (1.8-1.21.11) [Scheduler | Events | Jobs | Condition

Added richer time syntax support: - Named weekdays: every wednesday at 00:00, every monday,friday at 18:30 - Lists/ranges: every day of week in 1,3,5 at 12:00, every day of month in 1..5 at 09:00 - Multiple daily times: every day at 08:00,12:00,18:00 - Time windows: every 15 minutes from 09:00 to 17:00 - Nth/last weekday of month: every 2nd monday of month at 10:00, every last friday of month at 22:00 - Relative keywords: every weekday at 09:00, every weekend at 11:00, every month on last-day at 23:55 - Date constraints: between YYYY-MM-DD and YYYY-MM-DD - Timezone support per job: timezone Europe/Berlin - One-shot jobs: at 2026-06-10 14:30 - Optional jitter: jitter 30s / jitter 2m - Optional cron backend: cron: 0 0 3 New validation command: - /srvcron validate <time-expression> shows parsed interpretation + next runs. Improved schedule preview: - /srvcron checkschedule <job> [count] to view upcoming executions.

- Updated base version to 1.21.11. - Updated to Java 21. - Fixed some timers not firing properly.

Mostly code cleanup and couple additional config options.

Changes: · Fixed version issue; (Plugin v2.8.0 shows as v2.7.0 · Issue #2) · Fixed startup error for PlayerQuitEvent. (Could not pass event PlayerQuitEvent · Issue #1 )

Changes: · Fixed StackOverflowException issue when debug is enabled; · Added condition parsing when sender is [CONSOLE] (Ex. send a console command when there are X players online (%server_online% = 10)); · Remove AdvancementDoneEvent since it caused issues on older versions; · Added readable operator options (> - greater_than, = - equals, etc.)

Changes: · Added language configuration. (plugins/SRV-Cron/lang/messages_en.yml) · Fixed an issue with config not appearing on first start. · Added "notify-update" config option. · Added "silent-start" config option. If notify-update is set to false - there won't be a notification in the console. If silent-start is set to true - there will be less messages in the console on startup.

Changes: · Added command action to log text into a file. · Added option to enable debugging (sends a lot of extra information to the console and debug.log file.) · Added HEX color support (ex. &#FFFFFF) · Fixed the color issue with raw text actions [MESSAGE] & [TEXT]. · Updated the backup config. Logging text: - '[LOG <filename.log>] This will log this text to file named filename.log' - '[LOG] This will log this text to the console.'

Changes: · Added a bunch of new events. (chat-event, command-event, etc ...) · Added more event-specific placeholders. You can find the full list of events and placeholders on github: Configuration · M0diis/SRV-Cron Wiki (github.com)

"<ALL+>" prefix for command in Event-Job will be executed by every online player INCLUDING the player who dispatched the event. Otherwise, it will exclude the player who dispatched the event. Example usage without <ALL+> prefix: Code (YAML): join-event: welcome: time : 1 commands : - tell {player_name } Hello! # Console will send a message to the player. - <ALL> [CHAT ] Hello {player_name }! # Every online player will send a chat message.

Added <ALL> command tag. If command starts with this tag, it will be executed by EVERY online player. If not supplied in a Cron-Job - the placeholders will still be parsed, but without a player. (Ex. Server expansion will still work) and the command will be executed by console. If not supplied in an Event-Job - the placeholders will be parsed only for the player that dispatched the event and the command will be executed by the PLAYER if the command does not start with [CONSOLE]. For events, if you wish to parse placeholders (using PlaceholderAPI) regarding the player, that dispatched the event - use {}`s. (Ex. {player_name}).

Fixed an issue where you couldn't run jobs manually. Added an update checker.

- Added Tab-Completer - it is easier to browse the commands now. - Added some new API related things for developers. - Fixed the issue where the config would regenerate. - Added four new commands - Changed the permission of the existing commands. - Improved the look of the current job list and also added event job list. You can view event jobs using /srvcron list events command. srvcron.reload » srvcron.command.reload srvcron.list » srvcron.command.list srvcron.command.jobinfo /srvcron jobinfo <job-name> - displays some information about a job. srvcron.command.suspend /srvcron suspend <job-name> - suspends a job and it's execution will be skipped on the next dispatch. This will also show a message to the console, that the job is suspended and was skipped. srvcron.command.resume /srvcron resume <job-name> - resumes a job and it's execution will no longer be skipped on the next dispatch. srvcron.command.run /srvcron run <job-name> - dispatches the job manually. /srvcron run event <event-name> - dispatches event commands manually. (May cause some issues, use at your own risk)

Added some more API related things for developers. Changed the way the jobs are dispatched. They now work through events and are cancellable.

Added couple of events for developers. API · M0diis/SRV-Cron Wiki Added ability to check for permission as a condition for command execution. Code (Text): - '[PLAYER (PERMISSION:some.permission)] This will only be executed by the player if he has the defined permission'` Documentation has been moved to github wiki: Configuration · M0diis/SRV-Cron Wiki

Fixed an issue with timer command permission. You can now filter out the players using placeholders: - '[PLAYER (%vault_eco_balance% > 1000)] This will only be executed by the player if he has more than 1000 balance.' Same applies to all the other actions, title, message, sound, etc., ex: '[TITLE (%vault_eco_balance% > 1000)] You have more than 1000 balance!' This will send a title to all the players that have more than 1000 balance. Available operators: - X less than Y: < - X is greater than Y: > - X less or equal to Y: <= - X is greater or equal to Y: >= - X is equals to Y: == - X is not equals to Y: != This works best for placeholders that return numeric values. Operators might also work for values that return yes or true, ex.: - '[PLAYER (%player_is_op%)] shout Yay, I'm an OP when this job was executed.'

Added additional command action types. Commands that do not start with [ will be executed via console by default. [MESSAGE] or [TEXT] -> this will send a direct message to the player. [PLAYER] -> a command will be sent by the player. [CONSOLE] or none -> a command will be sent by the console. [TITLE] -> will show a title to a player. A more detailed usage below. [SOUND] -> this will play a sound to the player. Detailed explanation: This will play a sound to the player. The first argument is the sound, the second is the volume and the third is the pitch. You can find a list of sounds here: https://www.digminecraft.com/lists/sound_list_pc.php - '[SOUND] ENTITY.PLAYER.LEVELUP, 1.0, 1.0' This will show a title to the player. The first argument is the title, the second is the subtitle. The last three are: fade-in, stay and fade-out times. - '[TITLE] This is a title, This is a subtitle, 20, 60, 20' Alternatively you can use opt out the subtitle or the times, or just the subtitle. - '[TITLE] This is a title' - '[TITLE] This is a title, 20, 60, 20'