RPG Theory: Immunity

[DigiTan]

The final optimization is about half done. Now I'm rethinking all the remaining features to eliminate anything that isn't necessary.

The code on the chopping block this month is the immunity system in the battle engine. Removing all or part of this code would free up no less than 300 bytes, but first, this is it how works as of today:

• Both players have up to 3 bots on their team
  
• If a bot becomes sabotaged (burn, force, stasis, etc.) you can "pack" it into safe storage where it cannot be seen or harmed
  
• Unpacking does the opposite. If the bot was sabotaged before, it will emerge renewed but it will have the same HP
  
• Your opponent can counteract this with either Teleport or Force, but it requires a lot of luck
  

All of this sounds good, but I played the game twice and I was never really motivated to use this. Also, the menus required for this complicate several parts of the program.

Also, the AI has no packing capability because the code to detect when it was a good strategy was to large and sometimes made it easier to defeat instead of harder.

I think I want to leave the system 'as is' for 2P mode, but for story mode it will most likely be removed. But if anybody objects, I'll leave all or part of the current system intact. Any suggestions?

[DarkerLine]

[leofox]

[DigiTan]

Yeah, the 82 has a little over 28K, and the shell I'm using is 1K. I'm trying to get the full version down to 25K so it will have ~just enough room to work with the newer ACE shell that is 3K.

Anyway, I was hoping this immunity state would introduce some new strategy but it seems to slow the pace of the game too much. There were other features in the game like shields that had the same effect and didn't need any crazy menus.

For 2-player I was going to change things and have all the bots start the match in the stored state. Then each player chooses 1 bot to withdraw; chooses to attack or withdraw again; and so on. This seems to work nicer.