RuneScript/Queues: Difference between revisions
From RuneWiki
(Created page with " === Commands === queue getqueue clearqueue === Queue Types === ==== Normal ==== Requires protected access before it can execute ==== Weak ==== Requires protected access before it can execute. Cleared when closing modals. Moving or interacting with something new closes modals and inherently clears weak queues ==== Strong ==== Requires protected access before it can execute. Closes modals before executing and if the queue contains a strong queue at all (modals tec...") |
|||
| Line 27: | Line 27: | ||
Not granted protected access so it can always execute. | Not granted protected access so it can always execute. | ||
This concept comes from soft timers, which share the same behavior | This concept comes from soft timers, which share the same behavior. No protected access means they typically cannot edit anything on the player - unless the command or type is marked as not requiring protection | ||
Revision as of 18:10, 15 February 2024
Commands
queue
getqueue
clearqueue
Queue Types
Normal
Requires protected access before it can execute
Weak
Requires protected access before it can execute.
Cleared when closing modals. Moving or interacting with something new closes modals and inherently clears weak queues
Strong
Requires protected access before it can execute.
Closes modals before executing and if the queue contains a strong queue at all (modals technically close twice)
Modals are aggressively closed because they block protected access
Soft
Not granted protected access so it can always execute.
This concept comes from soft timers, which share the same behavior. No protected access means they typically cannot edit anything on the player - unless the command or type is marked as not requiring protection