Darn Opera browser sucks so bad at rendering CODE tags on SMF boards

ANyway gonna give this a try later

Oh, was that the really, really long line problem?

And wow, that is a lot of code. I'll try to help if I can.

What causes the problem? Maybe it was meant to do that? :?

The main optimization I see you should do here is subroutine-ize more of your code.  Even simple operations like adding 2 variables together can become subroutines if they're used really often.  For instance, I see a lot of reference to K+V in the code.  Loading a variable takes 3 bytes and adding is another byte so that's 7 bytes each time you use it.  A subroutine however is always 3 bytes.  So if you used the expression K+V in your code 50 times (which seems like the case here) you save 4 bytes for each call which saves almost 200 bytes from your program with this simple one:

:Lbl KV
:Return K+V

^ By the way, this is valid syntax now to put a return before an expression.  It was something I added in 0.4.5 so that you can do it all on one line instead of having the return on the next line.

You can do similar optimizations to other often-used expressions.  The cost of using a subroutine is 1 byte for the extra "return" and then a savings of original size minus 3 each subsequent time its used.  It turns out that if a routine is more than 7 bytes and used even just twice, you still get a size optimization to subroutine it.  7 breaks even (but of course is more optimized if it were used 3 or more times instead of just twice):

Original: 7 bytes used 2 times = 14 bytes
Subed: 3 bytes for each call to subroutine, called 2 times = 6 bytes + subroutine itself (7 bytes) = 13 bytes + return (1 bytes) = 14 bytes

Also, here is a more optimized "Length of Numbers"
:.Length of Numbers
:Lbl LN
:r1>=10+(r1>=100)+(r1>=1000)+(r1>=10000)→Y
:Return

* FinaleTI casts Arise on this topic

Well, I decided to pick this up again, since I've gotten some work done on Pokemon and I'll be finishing Collision Course soon (hopefully).
There probably won't be any new screenies and such for a little bit, because I'm busy optimizing. With a little work I just managed to shave about 195 bytes off the menu, and I haven't even fully implemented one of the sub() optimizations I started. (See Quigibo's post if you're wondering what I mean)
I'm sure I can find some more optimizations, and when I finish, I'll probably post the code again, in case I missed something that someone else might catch.

GLad to see this is not dead

Just make sure to not fall into the "Endless loop of rewriting code" though, that some coders felt into in the past, killing their project. Optimizing is good, though.

I hope this gets finished because I've been looking forward for this since the start.

Nice . I heard that this command had a bug, though, according to Nemo. You might want to check the IRC logs, though, because I forgot what it was...

Well, I decided to pick this up again

YES!
I'm so glad this is being worked on again.  I can't wait for more progress.

Optimization is going smoothly. I managed to cut the size from 10416 bytes to 9910! That's 506 bytes saved! And I'm pretty sure there are still several things I can optimize.