Script Limit [2]
commited
commit
5a4b9d8ed7fee0596251deecf084aeda59e5c64e
| ... | ... | @@ -1,5 +1,16 @@ |
| 1 | 1 | Fancade has a hard script limit. After a certain number of scripts in the editor, adding anything else will cause a "Too many scripts" error, and the game will refuse to run, as long as the extra scripts are not removed. Games that do not optimise scripts, that affect multiple objects, into loops are most likely to run into this issue. |
| 2 | 2 |  |
| 3 | 3 | |
| 4 | # Technical details |
|
| 5 | Script limit has been a mystery for a long time. An elusive upper limit that creators randomly hit, and are forced to scrap their ambitious project. Fancade 1.2 significantly improved the scenario by introducing Advanced Inspect blocks. Those blocks, when enabled, showed how much of the script limit has the game consumed already. |
|
| ... | ... | \ No newline at end of file |
| 0 | # History |
|
| 1 | Script limit has been a mystery for a long time. An elusive upper limit that creators randomly hit, and are forced to scrap their ambitious project. Fancade 1.2 significantly improved the scenario by introducing Advanced Inspect blocks. Those blocks, when enabled, showed how much of the script limit has the game consumed already. |
|
| 2 |  |
|
| 3 | ||
| 4 | # Technical Details |
|
| 5 | The introduction of advanced inspect allowed for more robust testing, which helped in discovering some key insights regarding the elusive script limit. Among those, Andrew Clark's discoveries were crucial for our current understanding of it. |
|
| 6 | ||
| 7 | ## Current Understanding |
|
| 8 | The limit is 4096. The value doesn't matter as much as how you decide to use them. There are three things that consume the script limit. |
|
| 9 | ||
| 10 | * Script Blocks |
|
| 11 | * Wire Splits |
|
| 12 | * Pointer Dereferencing |