Well, here they are, I made 3 to show how, just by manipulating the PRTY list, you can set up the pokemon in the order you want. Of course, that will work within the game, I just have to program that.
This is of course set for 25 pixels to be max, and will mess up only if HP>HPMax.
And theoretically, you could just change the .25 to anything less than .96 to get the amount for the line going across...
I was only wondering because I am planning to make a game where the strength of our tower is represented by how tall it is. I guess I could modify the code a bit to use an 8x1 sprite instead of a line and make it vertical. Woops, there I go again, talking off topic.
Anyway, about how much of the game is done (percent wise)?
it's great to come back and see that you're still working on this.
As far as the data that needs to be added, I'm not sure if I suggested this before, but would it be possible to make a simple data entry program for the computer, so the community can work together to enter the data? I'd be willing to help out some.
I dunno, I am still uncertain on how some of the data will need to be dealt with. I also have plans on completely rewriting the walking engine, to allow for scrolling, and deal with entire sections of map at one time, which will require me to remake the maps to show more at one time. It kinda sucks, since I had that all done already, but what ever, if it makes the game that much better, than so be it.
Whoa.
(@)=(@) <- Glasses, ha ha.
That is in Pure BASIC? That is awesome, dude. It looks good.
"Python has dynamic typing, and dynamic binding, which means that not only does it make a great secretary, it is also pretty damn kinky." --Henry the Adequate