Recent content by Marin

Let's say v20 is out and the save structure has changed again. Will a v18 save go through the v19 conversion and then the v20 conversion, or only the v20 conversion?

damn congratulations

Any fangame can get shut down. Multiplayer has no big influence on that. You'll be hard-pressed finding someone interested in making proper online multiplayer functionality, because that's not easy. It's also not necessary for a game to be fun, and you can still play alongside each other in...

self.z = z is identical to self.z = (z) which is identical to self.z=(z). All you're doing is introducing spaces and parentheses, which don't change anything about it. z= is the method name, so that couldn't be a problem. Proof: self.method(:z=).call(z)

From this point forward, bug reports in v17 are no longer permitted in this thread. The latest version is now v18, and as such, only bugs from this version should be reported here.

Any type of manifest/icon hacking will probably leave a trojan warning or similar when downloading. But I don't have experience with that to know.

I would also suggest saving $PokemonTemp, $game_temp, $game_system and $PokemonSystem to the savestate file, as these contain important information that will otherwise be reset upon loading the savestate. For instance, flash sprites, fly data, surf data, whether the save is or isn't a new game...

You'll still have to manually check if a script does or doesn't use your Auto-Crediting System, and manually add the author to your credits if it doesn't, though.

Big no-no. Using an automated program completely ruins any thought or creativity, and will certainly make the maps feel completely soulless. I'm sure it's a good program, but I highly discourage anyone from using it in their project.

That's not related to this script.

Debug can be accessed through a more convenient F9 button already, so I omitted it to keep the menu shorter and cleaner, in favor of the F9 shortcut.

Updated the script to fix an issue with no dexes showing up upon opening the Pokédex.

The issue is solved by adding pbSetViableDexes below def initialize ~line 54. I've just updated the script and thread to include this fix.

Updated to v1.6: Offset property works again

Updated to v1.5: Stair progress/data is now cleared upon map transfer, which means it's also usable for, say, stairs that lead up to a second floor via a transfer event.