Yes, I'm still working on this project. After suffering something that essentially killed any and all motivation on all projects, I struggled to keep pushing forward and getting things done. Sadly, I ran into some things programming wise that is going to be difficult to get programmed in correctly.

I'm most certainly not looking forward to getting this portion written, but it needs to be done before the next beta can be released. And once I get the pokeball bit done, it would be a matter of copying this code for the other pokeball types, and merely making the necessary adjustments to the equations.

Upon further review this morning, I've noticed I'll have to make additions to the battle program, along with the items system, to handle pokeballs properly. Ugh.

I think the worst part of this coding is going to make it so it does all the returns properly, since you can miss, the ball will fail, or the ball actually does the catch properly.

So this is what I'm working on. And hopefully will have done by this time February. :|

So far, what code I've written for the pokeball is untested, and could definitely be modified in a big way to shrink it. The code for catching a pokemon has not been added, and the program is over 6KB. I have an idea on how to properly shrink this, just need to take the few minutes to accomplish it. Or, I'll do it now, actually.

I'm going to need to re-read the information I am using to see what else might trigger a ball catch, or if that part is already programmed in and if I need to add it. I really don't know, at this point, as I don't remember what it is that the sheets said.

I didn't even know we had a new topic already! Welcome to the new year!

I haven't looked at calculator programming in years, but decided to take a look today. I'm glad to see you're still working on Pokemon Purple. You and your work were always an inspiration to me.

That's great to hear! Please continue to encourage TIFreak8x to continue working hard on this project; he's a busy man in real life and often has difficulty self-motivating himself for it with everything else going on. In addition, please don't hesitate to Introduce Yourself, let us know about any projects you're thinking of working on, and tell us something about your programming experience.

Wow, thanks! I am indeed still working on this, and plan to finish this current game. One way or another, it will be finished!

So, here is what I had started with the pokeball catching code:


Code:


And this is what I've managed to shave it down to:


Code:


I still need to add in the code for the catch itself to occur. I've got an idea and I've began implementation for it.

Code:
Can become:
Code:


For your delay-For loop, you should use the rand(nnn) trick instead

For the long set of stores to Str4 followed by draw and erase, I think I can optimize that all into a long loop, but I'm not sure it would actually be that much smaller.

Thanks for pointing out my error there, I'll try to get that fixed in the source here afterwhile, when I get a chance to catch my breath.

And yeah, no matter what I do with all that hex sprite data, it doesn't seem like something that will get smaller, or be any faster, so I just left it. At least it's not in triplicate, anymore :p

Edit:

Hmm, I need to get someone to draw up a sprite that would indicate a pokemon is caught. Either the 2 stars, or maybe something else..

Edit2:

http://www.youtube.com/watch?list=SP8969C90AD562B1C0&v=XbJtRFcbgUc&feature=player_detailpage#t=82s

According to that, it just stopped wiggling. I might just go with that and that will make me happy And make this go much easier in regards to that!

I prefer the just-stop-wiggling thing. As close to older games as possible is good with me

Woo! I think I'll go with that as well. Hopefully everyone else will agree to that thought

I find your lack of [Prizm] tags disturbing.

Heh, sadly the prizm couldn't handle that level of awesome in BASIC, it'd have to be done in C :<

I second (or third, or whatever) that, especially if it will make your programming job easier.

Yeah, programming that would be far easier, and I've gotten started on it.

I just now have to program in the text for "All right! <name> was caught!", then do a check in the pokedex list to verify that the pokemon has not been caught before, then go through the ceremony of showing the pokedex data, and if it has been caught before, have it either sent to the PC for storage, or added to the on hand pokemon list. That's not going to be fun to code.. lol

honestly (not speaking as an experienced programmer) graphics are normally one of my last priorities.
i normally make all parts of the engine first, and then have my little bro (who is an artist) help me with graphics.
since i know pretty much everyone is better than me at this, you probably shouldn't take my advice.
KEEP UP THE GOOD WORK!!!
you are a great model of what a hard working programmer should be.

Heh, thanks.

And I only work on graphics on an as-needed basis. I'm currently working on finishing up all aspects of the items system so I can begin working on the attacks to complete the battle system. I don't even know what I need to work on after that, truthfully. I think I have the maps to edit and fix, and add a few more events before I can even consider releasing a testing beta before public release.

Edit:

So, sitting here, looking at possibilities.

1) I can have the pokedex information stored into a list, 1 for each pokemon for ease of calling on and editing the list. This method for the list is around 1400 bytes of storage that I will need to keep open in RAM to use.

2) Create an appvar with 151 lines of 0. The start of a new game for pokemon would also have to create the 151 lines of 0 for a new game, which wouldn't really be that hard. The appvar would be 315ish bytes in size, and take a little more code to access and use, but be smaller when recalling into RAM to modify.

I'm almost liking the idea for the appvar, but I'd still have to modify some programs (only god knows which ones) to look at the new system.

So should I change over to appvars, or just be happy I can use lists? :p

If you use lists, people who have dabbled the slightest bit into TI-BASIC will be able to hack the game.
Anyone who does that is killing the sanctity of the game, and will probably reset their own RAM , so for the sake of security, I suggest appvars.

The only thing they'd be able to do is trick the pokedex into thinking they had all the pokemon, when they didn't, and it wouldn't help them in the slightest. So it's not something I'm overly worried about.

Instead of lines, couldn't you just do, like, a single string on the first line and then use a sub( to get that index in the string? That way it's only, like, 152 bytes of data in the actual appvar.