Enemy data is now coded in. Gotta choose a working structure for the battle engine to easily interface with, and then I'll be working on victory conditions.

Because you know. It would suck if you win a fight and something goes wrong.

I'm also thinking about turning the maze in a certain optional place into a warping hypercube maze. Won't code that in 'till much later, tho. Can't let extras prevent me from getting the core in.

Lack of progress on my part is making me somewhat unhappy. Even more so if nothing gets done on this wonderful spring break that started just today.

Just letting ya know. Started working on some "victory" conditions and getting the code looking the way it needs to be. Testing a few conditions there, and then throwing together the data needed for all them monster-y goodness. Keep ya posted on that respect.

I post this here because it's the most appropriate topic. I didn't post the image to the front page because this is unofficial and I was playing around with a blurring effect suggested (for other things) on IRC. This is the result, and does get strange results due to the dealings with grayscale.

EDIT: Augh. It was shot at high FPS mode. IE and Chrome users will see it rather slow-mo. but that's okay.
EDIT2: Grammatical typos. Argh "cold" Florida weather and sitting outside.

...
If you end up going with the typewritter effect, maybe you could implement a configuration menut that includes a speed adjustment option. (perhaps pressing a specifc button while on the map will bring you straight to this menu) I wonder what other settings could appear in that menu, though...

User-specific settings for grayscale. Not every TI-84+(SE) is made the same, and some of them have wildly varying specs when you speak of grayscale, all affected by what LCD TI chose to put into those calculators at the time and perhaps the age of the calculator itself.

There may be other settings that need to be addressed, but that is the only thing I can think of at this moment.

Marginal progress. Not enough to justify this delay, though. I'll work on it as soon as I get some time. Got a paper due yesterday to do.

Still gotta render them enemy sprites. They won't draw themselves. That's why there's a large blank space above.

Oh, man. Someone already posted before I can edit.

For the keywait version, you may have to hold some of these buttons a while after the song's over to make it back to the homescreen (or press ON if you're really impatient). I did this to give a little extra time with the black screen when it was running on a timer. The number of cycles chosen for that timer wasn't an exact science. I just guessed some number that looked good and called it done.

Sorry if this is causing anyone any trouble.

The best of all

Altough in a game ppl would probably not like to have to wait through it

I took it out of the game because it took up loads of space, and for that reason. I would not want to force the player to endure a rickroll if they're trying to grind. Unless ... it might work its way into the secret secret boss battle simply to help discourage savescumming.

This is soooo much fun!  I love rickrolling people, but using this in conjunction with the Start-Up App.
Excellent job!  I can't wait until I can get this on my math teacher's calc!

I'm glad you're having fun with it! If you haven't noticed, you can exit the app using the ON key in much the same way that you can (or will once the game's out) in the real game. There's so much of E:SoR code left in that, you can probably get a good idea of how E:SoR works just by viewing the source that's attached to the project.

If you want, I can probably remove the ON key quick exit (and force the user to sit through the rickroll) or add a key combination requirement like ON+CLEAR or something (if you want to obfuscate the method of getting out but still have a way).

This standalone thing is your idea. Whatcha want?