Renamed Execution Order to /Script/Execution Order
commited
commit
0c4543f4bb448e60d61482534f3c0b6c594610c7
... | ... | @@ -170,3 +170,4 @@ Questions/How was Fancade made%2C language%2C tools?.md: Questions/How was Fanca |
170 | 170 | made (language, tools)?.md |
171 | 171 | Will there be multi-player?.md: Questions/Will there be multi-player?.md |
172 | 172 | Change or Forgot Password.md: Questions/Change or Forgot Password.md |
173 | Execution Order.md: Script/Execution Order.md |
... | ... | @@ -1,25 +0,0 @@ |
1 | Execution Order is something that determines which script is after the current one. In Fancade we follow the execution order *"top to bottom, left to right"* (in other words, the way you read this text). |
|
2 | ||
3 | Thus, a set of scripts arranged in the following order: |
|
4 | ||
5 | ``` |
|
6 | AB |
|
7 | CD |
|
8 | ``` |
|
9 | ||
10 | will be executed as A → B → C → D. |
|
11 | ||
12 | [[/uploads/gkZWtHD.jpeg]] |
|
13 | ||
14 | 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 | ||
16 | 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: |
|
17 | ||
18 | [[/uploads/e0EYbHB.jpeg]] |
|
19 | [[/uploads/qsPi1I0.jpeg]] |
|
20 | ||
21 | **NOTE:** all built-in blocks use the **bottom-left corner** (the corner closest to the origin) for execution order: |
|
22 | ||
23 | [[/uploads/execution-order-closest-to-origin.png]] |
|
24 | ||
25 | Check out some common problems related to execution order [[here|what are some common problems related to execution order?]]. |
|
... | ... | \ No newline at end of file |
... | ... | @@ -0,0 +1,25 @@ |
1 | Execution Order is something that determines which script is after the current one. In Fancade we follow the execution order *"top to bottom, left to right"* (in other words, the way you read this text). |
|
2 | ||
3 | Thus, a set of scripts arranged in the following order: |
|
4 | ||
5 | ``` |
|
6 | AB |
|
7 | CD |
|
8 | ``` |
|
9 | ||
10 | will be executed as A → B → C → D. |
|
11 | ||
12 | [[/uploads/gkZWtHD.jpeg]] |
|
13 | ||
14 | 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 | ||
16 | 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: |
|
17 | ||
18 | [[/uploads/e0EYbHB.jpeg]] |
|
19 | [[/uploads/qsPi1I0.jpeg]] |
|
20 | ||
21 | **NOTE:** all built-in blocks use the **bottom-left corner** (the corner closest to the origin) for execution order: |
|
22 | ||
23 | [[/uploads/execution-order-closest-to-origin.png]] |
|
24 | ||
25 | Check out some common problems related to execution order [[here|what are some common problems related to execution order?]]. |
|
... | ... | \ No newline at end of file |