The best way to find these mistakes is to ask a friend. For example, accidentally inserting the wrong variable, or changing the order in subtraction will mess up a script without giving a trace. These are often the hardest to track down because there is no true 'error'. Sometimes, the error is purely logical and appears sensible only at the moment. To fix these problems, either use the wait() block in the 'Control' section between the blocks, or use the Say () for () seconds block instead. The script will just say 'Wasn't that great', because the previous two actions happen in a split second, or sometimes, within a single render cycle of the evaluator. A practical example is a continuation of the script above: For example, if a sprite is hidden or has a ghost effect of 100.
Other issues can occur when actions do take place but are not seen by the user. This will not work, because on inspecting the script, the 'n' variable will be equal to 0 on the last iteration (loop/repeat), and will cause a zero division error. For example, to find the sum of the fractions 1/2+1/3+1/4+…+1/100 one may use the following script: Often, thinking from the computer's perspective will highlight the issue. Finding a problem with a script is difficult because it makes sense to the writer. Inspecting a script that does not work is often not easy.
