Updated Execution Order.md (markdown)
commited
commit
52e9461961e6c5f4c399a109004d59596c051b8c
| ... | ... | @@ -11,6 +11,10 @@ will be executed as A → B → C → D. |
| 11 | 11 | |
| 12 | 12 | [[/uploads/gkZWtHD.jpeg]] |
| 13 | 13 | |
| 14 | In 3D, you can think of the execution order as a vertical collumn that executes scripts from highest y value to lowest, and then travels in the xz plane left to right, top to bottom. |
|
| 15 | ||
| 16 | [[/uploads/execorder3d.png]] |
|
| 17 | ||
| 14 | 18 | That's helpful, but what if you want to modify it? Here comes *Execution Wires*. Those yellow wires at the top and bottom of some scripts named "Before" and "After" are what we call as execution wires. Execution Wires overrides the default execution order. |
| 15 | 19 | |
| 16 | 20 | Once a script executes according to the default execution order, it'll execute all the scripts connected to it via Execution Wires before moving on the next script. A picture is worth a thousand words. So check these out: |