Quote:Heh, congrats, it looks great.
I guess you had to recode 50% of it, eh? 
My graphics and input functions are extremely well encapsulated. In the end, I only had to change a few kilobytes of code, a few hundred lines at most. I spent WAY more time taking out %s and hunting down minor bugs.
Really, unless you're a bad coder, all your input should point to a single input function anyway, right? Any half-assed tutorial tells you to define your keycodes somewhere outside of your individual functions? Also, you probably have it set up to draw everything in one sub, objects in another, text in a third. Since I was using a multikey routine anyway, input was done in a suprisingly short amount of time, with taking out the joystick routines taking the longest.
In the end, the hardest part (other than finding the bug where the palette was destroying itself because it wasn't originally *THE* palette, but an approximation designed to be able to record values outside of 0-255 for palette scrolling), was parting with my super optimized renderer to go with something that looks like it came out of the screen 13 era.
![[Image: Image2.png]](http://www.qbxl.net/Image2.png)
