It's amazing how quickly this stuff comes back. I stayed up way too late last night, but I have all sorts of stuff moving around & animated. I'm definitely over-optimizing, but that could just mean more features. I'm pretty amazed at what I've done in about 10 lines of code so far and 6 lines of data... I could definitely tighten up my data too...
So, is it me, or does XB IF / THEN / ELSE work a bit funny? It seems to be doing all the stuff in a statement.... So, if I have:
REM I didn't run this test specifically, but this is sort of what I think happens based on my work so far
10 A=1::B=2
20 IF B<A THEN PRINT "HELLO"::PRINT "GOODBYE"
In this case it prints nothing....
Also, it appears that you can't put a FOR loop after the conditional... - it blows up
This stuff is forcing me to waste precious lines of code...

But I'm sure I'll have plenty left...
Also, are there any tips on optimizing XB? I remember there used to be a CALL LOAD that would limit the # of sprites processed - so that the system wouldn't waste as much time. IIRC it was pretty negligible, but I'd like to do whatever I can to speed things up.... I'm gonna need it.
-Howie