At Time Wait

Use this block if you are trying to trigger something in your mission based on a time. This block has a time resolution to the hour and minute of the current time.

RobotAgentz uses 24 hour clock or also known as military time. If you are not familiar with this please read What is Military Time?

The At Time Wait task block consists of an input and a Done output.

If the input to this block is triggered the block will wait until the military time set in the first entry will be compared to the current military time and if they match the Done output will be triggered.

The timezone of the time entry will be set to the timezone of the browser that the mission editor is running in.

TIP

One thing to keep in mind when using this block is that an minute will be true for a minute, so if you run some other task blocks when this block is true and then go back to it to check for the minute it will run again. This could cause a situation where you could be running some logic many times during a minute instead of just running it once for that minute. The way to combat this is to add another At Minute after your logic to determine if the next minute has come before going back to the original minute to be checked. The example below will show this configuration.

Examples

Here is an example of a mission that checks if the current time it 17:15. If it is then it will trigger a log message block to write "You have reached 5:15PM!" in the mission log. Then after the logging of the message there is a delay block set for 60 seconds to make sure that the At Time doesn't trigger again. If so, then the process moves back to the original At Time block.

Copy / Settings / Docs

Each task block has three buttons named Copy, Settings, and Help.

• Copy: This will duplicate the task block with all the current settings.
• Settings: Settings will show a dialog that allows some added configuration for the block
  • Note: This allows you to add a text note for the current block. This note will appear in the log file if the Block Loggin option is enabled.
  • Transition Out Time: Each block can specify a delay in milliseconds that it will wait after an output trigger is activated. This feature is generally not used but is avilable for more granular flow control of the mission if needed.
  • Block Logging: If this is enabled then the internal logging of the block is turned on and will be sent to the mission log. Each block has different amounts of internal logging which can make mission logs become large in some cases. Users generally do not enable this feature because of the limits to data storage.