Recent content by ☆Rei☆

Okay, if you look at this section of the error message: Exception: RuntimeError Message: BitmapCache:394:in `load_bitmap'Failed to load the bitmap located at: Graphics/Pictures/GenderSelection/Background You'll see that it cannot find a bitmap image located in the...

Although I used to be attracted to girls, nowadays I'm just not attracted to anyone at all, which I'm fine with.

change any instance of $PokemonMap.bridge to $PokemonGlobal.bridge problem solved.

Or you could do this: Input.triggerex?("A"[0]) Where it says "A" you can use any number, upper case letter, or symbol that doesn't require you to hold in Shift to access it. (which in itself isn't a problem because a shifted character isn't a unique key) The only other keys left would be...

12 when I first joined, now I'm going to be hitting 21 this year.

That's such a waste though. Starving kids in Africa would eat that hatred.

It's too hot for me in Antarctica.

Hey, I've been away from electronics for 4 months, I forget things xD

Shoot, I almost asked who you are. It's been a long while.

That's why I told you to fix the "status" and "statusCount" variables. Also, the input for the "mail" variable needs to be a form of "PokemonMail" otherwise it will also crash when looking at the Summary. Well, you could use these functions instead: def pbPokemonToString(gift)...

From what I can gather, the script works fine in loading and unloading the Pokemon. I only get the error when trying to load the Pokemon twice in a row without resetting the text file. Also, as another note: You left a few fields "status" and "statusCount" as raw strings. As well as "mail" is...

You're trying to turn a string "MEW" into an integer. Ruby doesn't know that "MEW" (in string format) is the same as "150" Edit: It appears as if that was actually not the case. I made an assumption without looking at the code. I will look further into it.

Did you go through the intro scene, or did you do anything to bypass it?

Retry it on a clean version of 1.6, without trying to patch. If the problem is gone, then you patched it incorrectly.

And, did you run version 1.6 WITHOUT trying to patch it? If so, then did you make sure that everything extracted properly before you tried to test it?