Battle GUI


Code:


This is what I have managed to get rewritten, for like the 5th time. Trying to make this work in the most efficient manner as possible.

Also, this topic will be used to post random bits of code as I work on the battle system and GUI.

That's some extremely dense code there, tifreak! Kudos.

Does this mean we will get to see at least part of what you work on so that we know for a fact things are making its way done and you are having time to work on this too?

I get the impression that he doesn't have time; he mentioned that he's been very stressed because the garage hasn't been getting much business.

Somewhat, I will try to remember to update this code as I get time to work on things. Life isn't being too nice in that regard though, but I am definitely trying.

It shows how much you are determined to finish this, no matter how hard life is getting on you. We need more people like you in this world as role models.

Forgot to make it pull from the first element of the L_EPRTY list to begin setting up the enemy pokemon list. Regardless if the pokemon is from a wild encounter or trainer fight, it will always create this list and the first element will always be occupied. That was added in before the Tmin=2 conditional.

^This, this exactly. Although it can certainly be easy to get worn down by a lack of certain recognition or respect over the years.

heh, I hear you on that, but I do get some recognition for what has been done already. Hopefully I can finish it at some point in time.

Edit:

Added a bit to having the GUI say the trainer is sending out a pokemon. Just can't seem to get my head in the game right now, hopefully I can focus tomorrow.

Just remember I can do what I can to help if you want me to, just say the magic word (in this case just tell me something to do :p) and I will see what I can do for you.

lol I know, just not really much that can be done until I can get the battle system going and integrate that into the game.

Also, updated the code, realized I didn't need the Repeat for key loop after it says the trainer sends out the pokemon. It will have long enough of a delay while it displays the pokemon and runs through the equations to generate the stats. I have some of that written out, I just don't have that notebook with me right now to update the code. I'll do that a little later.

Sounds great, tifreak; keep up the good work! I don't think we'll fault you if you don't get a chance to make further progress until next year, though.

Heh, thanks. Updated the code, added the bit I wrote this morning. Now started with the displaying of the pokemon and the gathering and displaying of the stats.

Edit:

Hmm, looks like I have over complicated things with the equation program. I need to edit it to replace L_EPA with L_2 so I don't have to worry about having a ton of extra lists. That shouldn't take too terribly long to deal with. :]

Excellent, removing extra lists is always a plus. Glad you caught that. I guess the new year is going to warrant a new Pokemon Purple Progress 2011 thread, isn't it?

Already has. It is a new sticky item, if you'll notice, with only 2 comments in it. lol

Whoops, totally missed that. I'll shortly raise the number of comments on it.

lol awesome. :p

Also, updated the code very slightly to add in the start of the equation stuff that I got written down yesterday. Nothing big, just wanted it down so it would be less to type later.

Any progress is a step in the right direction, as long as it helps you continue your momentum and avoid paging your code out of your mental cache.

Yeah, I am trying very hard to maintain even the slightest amount of momentum with coding.

Added a bit, it now should clear out the trainer sprite and display the pokemon sprite with the separator bar and HP info.

Updated the code, now it searches the party list for the first, non fainted/empty slot and sends that pokemon out. It unarchives the appropriate list by dumping the code to do so in a temp program that the game creates and runs it from there. Next bit is to add in the code to drop the sprite onto the screen and display the options, and I will be close to where I was before I decided to revise the code again.