Well, coding for the party pokemon to use items will always cause some form of brain bending :p Simply because it always has to be able to write to the lists dynamically. Coding item usage for the battling pokemon is very easy though

http://tifreakware.net/tifreak8x/pokemon/files/Pic3.8xi

Sadly, the code just errored out with a dimension error, I think. :<

I figured at this point, might be best for you to see what you need to do. As was stated before,


Code:


:< I know I must have misunderstood what you wanted me to change.

Edit:

Until we can figure out about getting this fixed (and seeing what this does, I'm still not sure what it is supposed to do :p) we shall use the firewall against pokemon for evolution. :p

I think Weregoose once lectured me that this is preferred:


Code:

My code implicitly assigns Xmin=-47, Xmax=47, Ymin=-31, and Ymax=31 – a mere geometrical translation from the window that PP uses. The only changes you would need to make is to exchange ZDecimal:ZInteger for your settings, and then to counter that by adding 47 and 31 to the respective X and Y drawing coordinates.

Code:


@Kerm: I haven't used that in ages!

Code:

This gives the same setup in five fewer bytes.

Whoa, crazy. That's a very handy trick; you never, ever cease to amaze and impress.

Now to move it into position And figure out how to do a keypress in there to interrupt it..

Wait, how is it so fast? I just realized that it's un-erasing the sprite in super-fast speed.

Your evolvetest2.gif is redirecting back to evolvetest1.gif, so I'm afraid I'm seeing the same picture as in your October 10 post. Also, given the location of your Pokémon on the screen, part of my animation will probably be drawn outside of the region unless your sprite can be moved more towards the center.

Next, unless you're sprinkling in some library wizardry, I'll assume the preservation of the sprite while lines are erased is accomplished through a RecallPic. In that case, my code should also be fitted with one after the second Pt-Off( and before the Else.

*head desk repeatedly*

I KNOW I dropped that file in the screenshot folder last night :/ Why it wasn't there, I've no clue. Anyways, reuploaded, you should see it properly now.

le-sigh..

This shows what things look like when you cancel the evolution of a pokemon when you press the Alpha key.



And this is what I have so far of the completed evolution. I know the pokemon needs to be moved over a couple more pixels. But otherwise, what do you all think? Better than the firewall, huh? :p

Thank Weregoose for that.

Code:


This is mainly to show Weregoose the changes made to his code to make it work so I could cancel the evolution process.

Also, remember, this all ends up on one line in the end. :p

Nothing huge or big or otherwise. Took some time this weekend to update http://tifreakware.net/tifreak8x/pokemon/ss.php with all the screenshots that I never linked. There are now 109 screenshots linked on that page! Enjoy!

Code:


So far, this is the code I have for the Fire Stone evolution. I added in a bit of code this morning to take it beyond the pretty animation courtesy of Weregoose, and hopefully it all works properly. I still need to add a value to the pokedex list to make the new pokemon show up. Problem is, I don't remember what value did what. I think I can get that information from the pokedex file I have hosted on ticalc/tifw.

Excellent, great to hear both about your progress and your screenshot organization. I'm sad to see that you didn't update the first post in this thread with your full set of screenies, unless I'm looking in the wrong thread.

I think anyone's connection/browser that tries to process 109 screenshots at once will most likely die and not like me anymore :p

And yes, can't wait to get done with this 'template' code so I can move on to more items being finished.

Then you should pick a few recent representative screenshots! And I agree with your latter sentiment.

Managed to get Fire Stone evolution working properly:



Now to go add some error checking to make sure it isn't just used on any pokemon to evolve.

Reduced the looping to just once, removed the need to recall the pic which sped things up. Checked and verified that exiting the loop still functions.

That looks amazing! I wonder if you could make it spiral in, then switch sprites while it's "covered", then reveal the new one as it unspirals?

Not without the assistance of ASM, since I'd have no way of storing the sprite to a pic var and recalling it as the spiraling reversed. At least, at this point, I'm not sure there's a way to do it.