Mechanics

Scheduling Mechanics

Every interval, the date is checked as for folder mechanics. If a name of the folder should react to the date change, then runs the content of the given folder, and depend on the behavior of the folder, deletes the folder or signs it executed. The later happens that way, that it generates a last execution hidden file inside the folder. Modification of the file may cause unexpected results, because not the content of that file is important, but its modification time stored by the file system.

Expression Mechanics

The expression execution is based on the expression key, which is case-insensitive. The key and the value separated by the : sign, they are both trimmed (removed the starting end ending spaces) before evaluation. The inner expressions get evaluated first and their result then used to evaluate the container expression. As many expressions can be used for one command, as pleased, and in as many layers (include/nest) as pleased.

Example command:

LOG: §7Scheduler: §f{wash:{trim:{sub:..| {sub:State:.. {call:rcmd}}}}}

LOG: §7Scheduler: §f{wash:{trim:{sub:..| {sub:State:.. {call:rcmd}}}}}
Calculated in this order: #1 #2 #3 #4 #5
Result by steps:

  1- §7Scheduler: §f{wash:{trim:{sub:..| {sub:State:.. {call:rcmd}}}}}

  2- §7Scheduler: §f{wash:{trim:{sub:..| {sub:State:.. === Remote Command 2.1.2 =====|State: §2running|  Interval: 100 ticks|SyncMode: §2on|[...]}}}}

  3- §7Scheduler: §f{wash:{trim:{sub:..| State:§2running|  Interval: 100 ticks|SyncMode: §2on|[...]}}}

 4- §7Scheduler: §f{wash:{trim:{ §2running}}}

 5- §7Scheduler: §f{wash:{§2running}}

 6- §7Scheduler: §frunning

Result:

[00:00:00 INFO]: Scheduler: running