Difference between revisions of "Trig time block"
Line 1: | Line 1: | ||
trig_time_block is a [[Extended Trigger Before Move]] trigger. It blocks a PC from going a given direction for the specified start and end times. May be combined with other trig_time_block triggers. If time falls outside of specified times, access is granted. Time wrapping is ''not supported'', so specifying times that extend past midnight will not work as expected. The specified times are ''include'' the listed start and end hours. | trig_time_block is a [[Extended Trigger Before Move]] trigger. It blocks a PC from going a given direction for the specified start and end times. May be combined with other trig_time_block triggers. If time falls outside of specified times, access is granted. Time wrapping is ''not supported'', so specifying times that extend past midnight will not work as expected. The specified times are ''include'' the listed start and end hours. Though it is possible to stack trig_time_block special functions to block multiple time ranges, keep in mind that if you do so, you should not include a success message. The reason is that the success message would display if the first trigger was successful, but a subsequent trigger could block the exit, resulting in both success and failure messages being displayed. | ||
Usage: | Usage: |
Revision as of 23:23, 25 December 2011
trig_time_block is a Extended Trigger Before Move trigger. It blocks a PC from going a given direction for the specified start and end times. May be combined with other trig_time_block triggers. If time falls outside of specified times, access is granted. Time wrapping is not supported, so specifying times that extend past midnight will not work as expected. The specified times are include the listed start and end hours. Though it is possible to stack trig_time_block special functions to block multiple time ranges, keep in mind that if you do so, you should not include a success message. The reason is that the success message would display if the first trigger was successful, but a subsequent trigger could block the exit, resulting in both success and failure messages being displayed.
Usage:
Q <room vnum> <door direction> trig_time_block <start time (00-23)> <end time (00-23)> <success msg or -1> <fail msg or -1> -1
Field | Description |
---|---|
Room vnum | Room to apply the trigger to |
Door direction | The direction of the door to apply the trigger to |
Start time | The time to start denying access to specified exit, using a 24 hour clock. This number must be less than the end time |
End time | The time to start allowing access to specified exit, using a 24 hour clock. This number must be greater than the start time |
Success string vnum | -1 - No success message #STRINGS vnum with success message |
Fail string vnum | -1 - No failure message #STRINGS vnum with failure message |
-1 | Unused field |
Example:
Q 1200 1 trig_time_block 05 07 <success msg or -1> <fail msg or -1> -1 S