I believe I've done all I can with page 3 of E:SoR. That is all.

Maybe spambots are getting more and more intelligent. You all say it's a spambot but it actually contributed to this forum in a manner not unlike a few other people. Now, if only there was an alternative that required just one blue lobster

But, it's always better to keep the local blue lobster alive. So much fun. Lasts much longer if you only lick

Wow. Necroposting. However, the forum flagged it for me as "new" so I sorta disregarded that.

The poll has been closed (finally) and the verdict...

was in ages ago. This project is being coded for the TI-83 Plus SE / TI-84 Plus (SE). There's no turning back. Too much of the code relies on the extra memory that the higher end calcs have.

What wasn't discussed back when this poll was first established was the fact that the newer 84+'s lack much of that extra RAM, effectively giving it a total of 48KB. This isn't a problem, since the game is being coded to work with just one page of extra RAM.

Thanks for all the input and lobster votes!

EDIT: DJ Omnimaga, is there a feature of this forum that allows posts to NOT bump it to the top? I feel bad that a topic that needs no further input is placed at the top of the list.

Zomg! It's a disease now?

Better not catch it. It's been said that IRC is the method upon which it's easiest to catch it.

I will admit that I didn't quite work as hard as I could've (but still pretty darned hard) on the graphical simulation of xLIB functions. I even had to go as far as a nice talk with teh author of xLIB for all the quirks that were involved when missing variables were introduced into the equation.

As for the real(14) thing not working, that's an oversight. I had to check that one earlier today, and that's pretty amazing that such managed to slip through the cracks. I know that at one point, it *did* work. But still, if you are coding any new game, there is a decent workaround: det(4)

Just so you know, you can also check the amount of free ROM (Archive) by doing det(4,1)

All spells take from a common pool of "charges". It doesn't matter whether or not you're casting something relatively weak or something insanely strong. If you have it, it costs just one MP.

If you've got your max number of charges ( 8 ) and if you wanted to cast Quietus eight times, go right ahead (good luck getting it, though). If you wanted to cast some sort of healing magic eight times, you're free to do so as long as you have those charges. You're encouraged to pay attention to your common pool of charges since they ain't that cheap to get. As far as I can tell, they're more for that extra "push" when you really want to beat down that boss but just don't have the kind of strength to do it.

Try to believe me. I'm the guy programming it

Lol I doubt the former, altough we never know about the latter. Games or not, though, I am certain if TI decided to find a way to cut down production cost by a penny, they would get rid of some of the 16 KB additional RAM on 84+ calcs or rewrite the OS so on newer calcs the additional memory is not needed at all for USB stuff. Who knows? Maybe they would even drop the user RAM to like 16 or 20 instead of 24. With TI, these days, we never know what they will do.

Something like that is not likely. The new OS would still have to run on every graphing calculator that came before it and reducing the amount of RAM that you do happen to see would not only be difficult to do on their side, it would also go against the advertising that they do for their calcs. Next time you look at the package for one of these things, it should say something like "Has 23KB of user memory". It's a selling point because their OS actually uses it and it's been available for ages. It's what people expect. What wasn't expected was the lack of "extra" RAM because it was never advertised, therefore, they've got no reason to be held to it.

In addition, it wouldn't make much sense to cut memory down further in multiples that aren't 16KB, since the calculator has to map in pages in multiples of 16KB. It would be cheaper to have that memory in there than to add extra logic to appropriately map missing bytes from a page.

EDIT: While I'm on the topic of memory, I do plan on having that project remain compatible with the "crippled" newer calcs that seem to only have 48KB of RAM. The game would impose some steep memory requirements but after rearranging memory as needed, I can net myself a full 32KB of "saferam" in one flat memory model. ($8000 to $FFFF. w00t.)

I'm gonna go ahead and use this thread to post varying images that have been produced for this game. They may be screenshots. They may be other things. This post will be updated each time I have something to add, though I will (if legit) bump the topic and let it be known.

( 1 ) The first contribution I've got to add is a map of Escheron in all its goodness, with markings that show all the important parts. The small airship symbol next to the names means you need to fly to get there. Courtesy of Zera.