Here it is!  An early release build / test build of my new RPG game "Elimination."  If you like Final Fantasy, Earthbound and Pokemon, you'll probably like this game.  Download the game here:  http://ceme.tech/DL2201

This is an early release build.  That means that this is for testing purposes.  If you manage to finish the game, you won't be able to see the final cutscene because it's not ready yet, but your game will be saved, and then you can see the ending simply by loading your saved game once the final cutscene is ready to go.

There are two things I'd like to know:
1. Does the game work?  (I've only been testing this on an emulator)
2. Is the game too easy or too hard?

You can send me an email or make a post here if you find a bug or if you think the game is too easy or too hard.

What do I mean by if the game is too easy or too hard?
* The first two levels should be easy.  Levels 9,10 and 11 should be hard but not frustrating like NES Battletoads or Atari 2600 E.T.
* Are there any weapons that are overpowered?
* Are there any weapons or projectiles that are too expensive or too cheap?
* Do you find that you have to return to the main hub too often to heal yourself?
* Is money too easy or too hard to come by?
* Is it too easy or too difficult to level up?
* Is there a world where one character gets under-used because he / she can't fight most enemies?
* Are any of these bosses (besides the Alien CIC) too easy or too hard? Firebird, supercomputer, Zebella, Balkstone, Tank Mark X, Cardon Bol, Red Hawk

I'll be able to fix bugs and statistics, such as how much money a robot gives you, how much health you get for leveling up, how much damage a weapon can do, etc. I won't be able to add any more features. For example, I was hoping to add an option so that you could instantly heal all your health at once instead of pressing "heal" over and over, but I won't be able to.  I was also hoping to add an option where damaging shields with protons gives you more experience points, but I won't be able to.

I cannot send the 8xk file to my 84+. I get an error saying the application file is broken and to redownload it again, and if it doesn't work, to contact TI for help.

Out of curiosity, can you send it to an emulator?

Could it be that I used WabbitSign?  Should I use something else to sign the app?

Could it be that I used WabbitSign?  Should I use something else to sign the app?

I haven't used wabbitsign in a long time and I'm not sure if that is the issue. I generally use spasm and I've got it configured to automatically sign apps.

I know Wabbitemu is very generous with loading apps (it bypasses the calc's security which is great for streamlining development, but it hides signing issues).

I'm not much help with this stuff these ays .__.

I'll try to check the 8xk integrity after work.
It could also be that DJ Omni encountered the infamous bug that prevents more apps to be sent.

Rabbitsign did indeed say the file had a poor signature.  You can try this newly signed one.  However, I'm not 100% sure it will work, because I "resigned" the app rather than starting from a freshly generated .bin file -- again, the new .bin file will have to wait until my reoptimizing is done.

Quote from: Hot_Dog on November 25, 2021, 11:17:40 pm

Rabbitsign did indeed say the file had a poor signature.  You can try this newly signed one.  However, I'm not 100% sure it will work, because I "resigned" the app rather than starting from a freshly generated .bin file -- again, the new .bin file will have to wait until my reoptimizing is done.

It appears the resign was properly done.
However, attempting to create a new game causes a RAM clear (TI-84+SE).
Thanks to wabbitemu, it's due to an execution violation on bank 3 (RAM page 0) at address $C0C9.
Not sure if PC is supposed to go there, but if yes, you'll need to expand RAM execution range first.

  *facepalm  I totally forgot about that!  Yes, there is some RAM code there.  I put my uncompressed tile data and map data at $9D95, when instead I should have put my RAM code there.  Again, sadly, that's a fix I can't quickly implement, but I'm glad you caught that. 

A very special thanks for everyone wanted to test this! I'll try as quickly as possible to get this problem fixed in about 5 days!

For people who can't wait 5 days, i coded a quick fix.
Just run UNLOCK.8xp once, it makes all RAM executable, so the app won't crash when creating a new game anymore.
In case you want the RAM execution permission back to its system default configuration, LOCK.8xp basically cancels what UNLOCK.8xp did.
Happy testing!

Hey, thanks!!  Speaking of which, once these bugs are fixed and everything optimized, your old saved games will still work, so it's okay to start testing!