Well, I have managed to incorporate the code that creates the small menu list into the party menu program itself, to save the space in ZMISC.

Sadly, I have run into an issue with being able to back out of the main menu to exit the program. It works when you first activate the program and press ALPHA. When you move a pokemon, and get back to the main menu, it refuses to exit out of it. I am not sure what is going on there, got a bit more testing to do I suppose.

Not sure what I did, but it seems to be fixed. I also made the 'Back' option functional. I also saw a few slight issues with the boxes being redrawn and the placement of text; basically things were off by one column. These have been fixed as well.

The only aspects of this 'engine' is that the items system doesn't work yet (though I have code in there so it is a matter of just adding it and it should be done) and I don't have the special moves and HMs programmed in. Since the map system isn't set up for it yet, it is irrelevant.

So, it be time to start planning the battle system.

I did have the code for the display of the battle screen, I just have to figure out where I put it. lol

Then comes the fun of determining variables and clearing of portions of screens for expanded menus and blah blah blah lol

The interface is going to be soooo easy. The stuff people can't see is going to so not be easy.


Edit:

I found the code, I think, to display the battle screen. I just have to clear the unneeded programs from the testing calc and see about setting it up to get ready to start in on a battle system. And item system.. hmm..

Might be best to break out the 84+se to tackle this, not sure a normal 83+ will be up to snuff.

Anyways..

I will have to determine what all variables I will need for the next section. I know a great many will already be in use for specifics, and I need a pic var to store first when the screen is created, then after both pokemon have caused their damage or status changes. This will allow faster reload times when dealing with the sub-menus and such. Or, at least I hope it will.

The interface should be a cake walk. What has me worried-ish is the equations and all the data that I have on the 150ish attacks that are available in the game. This next bit shall take some time to get going, so might not be much in the way of screenshots and such in the mean time.

I also need to set up temporary lists for this. Well, at least one.

This way, I won't be affecting a main list with things that could cause problems, like temporary status changes, and push over any relevant data, like hp and pp data when the battle is over or the pokemon is being switched out for another. status changes like poison or paralysis persists, however confusion would not, swap it out and it is no longer confused. I believe there was another status effect that was similar to confusion, however I can't recall it at this time.

Nice to hear some progress! Good luck on your next task!

Great to hear some work!
I look forward to this with great anticipation

I have been working on organizing more of the lists and such. The user pokemon and party are going to remain the same, but I have create a similar setup for the trainers/NPCs, and allow it to be adaptable to having link battles. I believe I have this part figured out.

I have also come up with an easier way to tell if a pokemon is fainted so it does not have to go through and unarchive all the lists (which is roughly 3700 bites with all 6 of them). I plan on adding a .5 to an element in L_PRTY to indicate that said pokemon has fainted. It will start at the first slot and move through the list until it comes across the first pokemon that is not fainted, then call up that data and drop it into a temp list.

The temp list will be dumped back into the main list after the battle is completed. The things that will be affected in the returned list is HP, PP of each move, and any status changes that have been completed. I might also do the exp check at this point and level up as needed before dumping back into the main list. So that means with each passing of lists, I will have to verify that the 4 attacks are the same with each list, and if not, dump those over as well.

Once I get these aspects done I can thusly start working on the escape routines. Have to do this so I stop confusing myself <<;

Glad to see progress Good luck.

I thought of a question though when I saw the thing about status updates. When a Pokemon is poisoned do you plan to make it so every three steps, or what ever it was, will lower it's health?

Ya, that glitchy screen could be hard. An option would be to quickly run an assembly invert screen program twice real fast. I don't know how feasible that is though.