|
Here's another.
Leggy's toolset tip #7
Test. Play the module every time you add something new. Not entirely, of course, but the bit that should be affected by the change. That way you know whether or not your scripts are working, and if not, testing often gives you a reasonably good idea on where things went wrong.
Use common sense, bracket checks, Capital Counting, the PrintString("...") command and the '`' key (usually found right above the 'Tab' key) in conjunction with the 'Tab' key (usually found just below the '`' key) to find out what parts work and which ones don't and why.
Also, regularly test a larger area to make sure a script designed for one region isn't affecting things in another as well.
It saves time when you playtest often, makes it easier to discover where you've made an error and gives you a better idea of what the completed module will be like than immobile objects and lines of text ever will.
|