A new form of contest has been started on Omnimaga: The "Optimise That" contest. There is a TI-83+/84+ BASIC one, and a z80 assembly one. In both, we present you a piece of code (that doesn't necessarly work or do anything relevant) that is plenty of optimizing errors and bad code. Your job is to post a better version of the code, and the person who post the best code wins. There are no prizes (for now), but this should help people improving their skills even more, give them more interest to code, and bring back some calculator related activity at Omnimaga, since there hasn't been much recently (it seemed like the site was turning into a music only forum, when it wasn't meant to be this way).

Make sure to check those topics for the contest. A new code sample will be posted whenever the first ones are optimized completly.
Optimize This (z80 Assembly)
Optimize This (TI-83+ BASIC)

Thanks to Halifax for the idea :)

There may be some calculator RPG additions to the archives and related news soon as well.

Sounds like fun; I'll give the Basic one a look.

[after looking] This is going to take a while... but I want to try to attempt it :D

DoN't worry you have the entire week ;) or until lot of entries are submitted

what in the world would you program this in? (if you can't tell all I ever do is calc basic.... not even asm.) I'm obviously not doing this though....

Assembly and BASIC. Read carefully.

yeah, the program is located here actually

Oh, are we supposed to post it in the topic thread?

not this one, but one of the respective topic linked

No, that's not what I meant at all (I think....) Are we really making a program that optimizes TI-Basic code in TI-Basic? (same with Asm.)

Ummm no. You optimize the code given to you in the respective topic.

btw here's what the program in the TI-BASIC topic came from. Ph33r the suckiness!!!! XD

http://youtube.com/watch?v=fzFYG-NPZyQ

Talk about a Reign of Legends 3 game attempt only after 8 months of coding :D

Huh, assembly contest is already off-line. It's just I thought, from what was in this first post, meant that there were errors inside the code to find out. But that's impossible if we don't have background info, and just code info, which we interpret as a code doing something, hence we were searching for the outputs and inputs, rather than just optimizing it.

But I see I am wrong, it is just slow code (and not a buggy one), so it's kind of my error of complaining about that and asking all those questions. And i apologize.

Otherwise the contest was fun! (though a bit short)

Well the assembly contest was shutted down earlier than planned due to the complains, but it's ok though, at least you pointed out flaws of the contest, so the second contest (yes there will be another, and more in the future) will be even better.

Btw always feel free to suggest routines (not the code itself, just an idea, for example, walking engine, title screen menu, etc), so then we can write you some junk code you can optimize :P