I've been fiddling with the main.scm file in GTA3 using Sanny Builder. I've been adding little bits of code to make the city feel a little more alive (making taxis pick up pedestrians occasionally or making the car crusher actively picking up a random car as you approach it being a couple examples). I've been placing these threads in the area where all the other background threads are (such as the thread that makes hobos spawn in the tunnel under Saint Marks or the thread that make the store clerk appear in the Ammunation). Unfortunately, I've noticed my game has started to crash occasionally, seemingly at random. I'm assuming it's one of my new background threads that's causing the problem, but I can't for the life of me figure out which one or where in the thread the problem is originating. The way I normally debug code is by using 00BC to make messages appear at the bottom of the screen so I know where the game is in the thread. However, adding the 00BC opcode to every single part of my existing code that I've made so far would be horribly tedious. So my question is: Is there some sort of debug mode that can be used to constantly show exactly what code the game is executing (in another window or in the game window) so that when it crashes I can see exactly where it stopped? If not, does anyone have any other suggestions for pin-pointing bad code over the 00BC method that I currently use?
Right, so I went back and read the FAQ thread at the top of this board (which I passed over like a dope before) and found this little gizmo. It seems to do the trick. Now I just have to wait for the game to crash again while I'm using this tool. I'd delete this thread since it's basically just me answering my own question by reading the FAQ thread, but I can't seem to find the delete button anywhere.