Most are minor issues and on your game wouldn't be noticed, but take as example at the med data center where they are running over 500 terminals simultaneously, any slow down as errors stacking up in the program is simply unacceptable. So if any module, mod, makes a change to the engines configurations and you have no debugger, it is almost inevitable that problems will arise. It makes the program crawl at a snails pace. With your game, the debugger was removed in the final version. If you have to change the engine itself, the debugging must be reran. Then you add modules to the program that utilize the engines built in capabilities. 'When you build a program or game engine in this case, the engine's operations are ran under a debugging program that monitors every tiny aspect. I've also been told to always suspect any mod that makes global changes (as lighting mods) as it is almost impossible to predict all the possible side effects. Crashes stopped and I've never used a lighting mod since.
(Wuss video card) My response to new crashes is to remove any recent mod additions. Never got as far as nuances as the game crashed twice in a half hour. I had a mod for a while that supposedly improved interior lighting.
