This feature suggestion has another name, CHANGED_REGION_RESTART and was suggested in conjunction with SVC-1086. The problem with CHANGED_REGION_RESTART is that the name is a misnomer. Since the script isn't running during a restart there are two distinct events, the simulation being stopped and it being started. Restart is commonly accepted to mean an event where the time between stop and start is a short period (or it could be interpreted to mean that things are reset back to their initial state!) but the use of this event would be to indicate when a simulation was started. By using the _START nomenclature and not _RESTART, we can later add _STOP without causing confusion; additionally we can later also add _RESTART in conjunction with the _STOP as to tell the script that the interruption is only planned to be a short one.

To state it another way:

• CHANGED_REGION_START - fired when a region comes online
• CHANGED_REGION_STOP - fired a 30 seconds before the script is stopped before the region goes offline.
• CHANGED_REGION_RESTART - fired in conjunction with CHANGED_REGION_STOP to indicate that the region will be back up shortly.

--------------------------

Edit:

• CHANGED_REGION_START - fired when a region comes online
• CHANGED_REGION_SHUTDOWN - fired a 30 seconds before the script is stopped before the region is shutdown.
• CHANGED_REGION_CRASHED or CHANGED_REGION_HARD_SHUTDOWN - fired in conjunction with CHANGED_REGION_START to indicate that the region was brought down without CHANGED_REGION_SHUTDOWN.