I'm stealing your algorithms.

Where did you get them from?

I was kidding.
I just wanted to know if you made them from scratch and such.
Could I perhaps see said design doc?

Newest screenie looks awesome. I'll look at the battle doc when I have some time. I love battle engines.

Ouch it seems like you don't have much luck with this laptop

Good luck and I hope you get it fixed

As for CaDan it would be awesome, you should add a new topic about it in the CaDan thread when you got some progress ^^

This is sort of off-topic, but I've always wondered this. The grayscale routines supplied in Axe don't play nicely with interrupts, so how do yours work? I know many other grayscale games have interrupt settings, just like yours. How exactly do the interrupts play in, and when is the screen updating taking place?

DJ Omnimaga is right about the entire game running in a huge interrupt. But to really answer the question, the screen update is happening during an interrupt.

The reason why you update the screen at an interrupt is so that the screen is updated at a consistent rate, partially independent of whatever else the program is doing. Interrupt settings are there because sometimes the screen just doesn't display right at some interrupt frequencies. Now, more than ever, we've come to the realization that these calculators are not made equal, so there's gotta be a way for users to adjust conditions in case the grayscale appears crappy on your calculator.

As for the question about Axe, DJ Omnimaga is also right with the respect that this is a "pure" ASM project (Flashapp), and not an Axe project. As for why Axe doesn't play nice with the interrupts, you might want to direct your questions more to Quigibo (SP?) or someone else who's knowledgeable about Axe. I believe there's a subforum somewhere on this board that handles Axe exclusively.

Coding the battle engine resumes Monday October 4, 2010.
The game is planned to be released by December 25, 2010.
So yeah. Cutting the CaDanITE project a little short for the time being.