The Clickteam chatroom is down, so my time away from the code at work will have to be spent typing things into here instead. I've been staring at a stacktrace all morning and my eyes are now pointing in opposite directions, but I've almost solved a problem that I've been working on since the beginning of the week (see the last post for a brief summary of why it's taken so long).

The issue was that the Publisher would work fine if it was left to run, but was slightly overenthusiastic and carried on regardless if you ever happened to cancel it. After going step by step through about two thousand lines across ten or so individual classes, I've now successfully got it to crash when you cancel it, which is not exactly what I'm aiming for but a definite improvement.

I finally opened up Crystal Towers 2 again when I was on the train, so I got the chance to work on that a bit as well. It's amazing how you can see a problem immediately on Monday morning after spending all day on Friday looking for it, and just about the same applied here - the catastrophic slowdown throughout the game has now mostly been removed because of reworking everything that read an external file, but there are still some problems in the enemy handling section of one level. This is probably because I'm asking the computer to calculate rotation angles and sine functions on every frame, but I have a clever idea on caching the results to solve that. This should probably be in my other journal. Never mind.

I'm sure that there was going to be a point to this post when I started writing it. As an experiment I wore my USB drive with its handy neck strap on the walk from the station this morning just to see if I was beaten up or not, but I didn't even get any strange looks.

Now I've got something to do - proofread an essay from Whitney, who was explaining to me this morning why using mouthwash is like selling your soul to Satan.