Updated What are some common problems related to execution order?.md (markdown)
commited
commit
83fe5a8bb9ade1ab08f115ff7a0acdb4cbb7e577
| ... | ... | @@ -1,6 +1,4 @@ |
| 1 | [[Execution order]] is a boon and a curse at the same time. While it helps determining what to execute, sometimes the default Execution Order doesn't actually do what you want. Thankfully, you can easily fix that using Execution Wires. |
|
| 2 | ||
| 3 | Here are two common problems related to execution order. |
|
| 1 | Script blocks are executed top-to-bottom, left-to-right, [by default](Execution order). When you need more control over the order, connect them with yellow wires. Here are some examples where it's easy to forget that the default order may not be what you want: |
|
| 4 | 2 | |
| 5 | 3 | 1. This one is common among newbies. In this case, the problem is easy to spot. The variable **A is defined AFTER the Set Position** that has A as an input. Since A is not yet defined when Set Position was run, it simply does nothing resulting in a buggy script. |
| 6 | 4 | [[https://imgur.com/NZgn9C7.jpg]] |