Bleh.

docs/intermediate/configspecifics.md

@@ -45,10 +45,12 @@ Move to the Event inside the `subscription` event type.
 <br />
 <br />
 
-Pay attention to the `playTime` field. This has been set to 20 ticks (20 ticks is one second). This event is also of the `subscription` type. What this means is when this Config Event is tested and passes, it gets added to the `host+subscription+bits` queue, triggers if it is the first in queue, and then CCI waits 20 ticks, before triggering the next Config Event in the queue.
+Pay attention to the `playTime` field. This has been set to 20 ticks (20 ticks is one second). This event is also of the `subscription` type. What this means is when this Config Event is tested and passes, it gets added to the `host+subscription+bits` queue, triggers if it is the first in queue, and then CCI waits 20 ticks, before triggering the next Config Event in the queue. Be mindful that when Config Events in the queue are triggered, their conditions are not tested again, so their outcomes will be triggered directly. If you need to check a condition when the outcomes trigger, use a `ConditionalOutcome`.
 
 Removing the value of the `playTime` field, or setting it to a value below 0, will make it trigger immediately without joining the queue.
 
+Just before Config Events in the queue are triggered, Global Variables are re-inserted into the variables list, just in case they have changed whilst the Config Event sits in the queue. Because of this, try not to insert any local variables with matching names as global variables, as those will be overwritten.
+
 <br />
 
 ### Ignored Types (name: `ignoredTypes`)
@@ -84,7 +86,11 @@ Normally, when an event triggers, all of the outcomes are triggered. Turning thi
 
 ### Delay (name: `delay`)
 
-Adds a delay (in ticks), before triggering the outcomes. Can also work in queues.
+Adds a delay (in ticks), before triggering the outcomes. Can also work in queues. 
+
+Similarly to queues, after the delay, when Config Events are triggered, their conditions are not tested again, so their outcomes will be triggered directly. If you need to check a condition when the outcomes trigger, use a `ConditionalOutcome`.
+
+Also like queues, just before Config Events are triggered (after the delay), Global Variables are re-inserted into the variables list, just in case they have changed whilst the Config Event waits out the delay. Because of this, try not to insert any local variables with matching names as global variables, as those will be overwritten.
 
 <br />