Runtask denizen command not dcommand9/3/2023 #Use to run a task script named 'example' 3 days later. Returns a list of all scheduled task IDs for Command: runlater. Specifically for the case of very large delays (hours or more) - in the short term, 'wait' or 'run' with a delay will be better. Implementation note: the system that tracks when scripts should be ran is a fair bit more optimized than 'wait' commands or the 'run' command with a delay, Use Tag: nlater_ids if you need to dynamically check if an ID is in use. If you use IDs, they must be unique - you cannot have the same ID scheduled twice. You can optionally specify the "id" argument to provide a unique tracking ID for the intended future run, which can then also be used to cancel it via Mechanism: system.cancel_runlater. Objects that are lost before the delay is up (such as a linked NPC that is removed) may cause errors. The delay input is a DurationTag instance, that is relative to system time (not server delta time).ĭefinitions and queue object links will be preserved, so long as they remain valid at time of execution. The guarantee can be broken if the server crashes or other errors occur. Script runs are guaranteed to happen after the time is up - if the server is turned off at the scheduled time, they will run at next startup. This command will store intended script runs to a file, so that even if the server restarts, they will still run. Script, path, and definition inputs work the exact same as with Command: run. : )Ĭauses a task to run sometime in the future, even if the server restarts. Learn about how commands work in The Beginner's Guide. Commands are always written with a '-' before them, and are the core component of any script, the primary way to cause things to happen.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |