Argument Formatting

Some types of arguments are common amongst the different directives. This section discusses the appropriate formatting options available to them.

Delay Formats

Various directives allow for a delay= argument to be applied. This argument specifies a delay period between the event trigger time and when an item is released. In essence, the format is [number][unit specifier], where number is a numeric value and the unit specifier is m , h , d or w for minute, hour, day or week respectively.

Example	Description
20m	20 Minutes
2.5h	2.5 Hours
1d	1 Day
2.25w	2.25 Weeks

Source \ Destination Formats

Some directives can take a subset of tasks as an argument. As tasks can be either source tasks or destination tasks, the s: or d: prefix can be used to explicitly specify what type of tasks where applicable. Without this prefix, it will default assuming the argument relates to source tasks.

Source \ Destination Format Examples

Example	Description
s:A/1/1	Source Tasks
d:A/1/1	Destination Tasks
A/1/1	Source Tasks; because no prefix is specified, source tasks are assumed

Dates

Various directives allow for a on= , start= , end= argument to be applied. This argument specifies a date at which a particular event should occur.

Internally, the script calls the C# method System.DateTime.Parse, so theoretically any string accepted by that method should be valid.

The behaviour of this parse method also depends on the region/locale settings of the host Operating System. Different locales can produce different results for the same literal string. For instance, the string 1/12/2023 will represent the date 1st December 2023 in an Australian locale. In a US locale, this will represent the date 12 January 2023.

Date Examples

Example	Description
1/1/2023	1/1/2023 12:00 AM (Midnight)
5/7/2023 2:37 PM	5/7/2023 2:37 PM
5/7/2023 2:37 AM	5/7/2023 2:37 AM
5/7/2023 2:37	5/7/2023 2:37 AM
5/7/2023 14:37	5/7/2023 2:37 PM