| Troubleshooting By 'Crackerz' (via the forum) GENERAL Every time you compile, the level is saved first. This means that you must save a master copy or original copy before you start to troubleshoot - and leave it alone, otherwise after many little changes, the mess will be worse than before.! Change one thing at a time. Tempting as it is, avoid the "scattergun method" of troubleshooting. Even if you get lucky, you will have no idea what the real problem was, and the answer will be 'magic'. Overall, you'll save time. TRIGGERS If you have a mess, start by narrowing your focus. Delete all triggers belonging to one side. Then delete the remaining triggers one at a time, compiling after each, and test. Once the problem goes away, you'll know it will have something to do with the last deleted trigger. ECOM An area that has caused a number of problems for the beta testers in the levels is the ECom messages. Keep them short if possible, and avoid non-alphanumeric characters - some of them are control characters - such as @ and [ ]. |