Glitch City Laboratories Archives

glitching with savestates

glitching with savestates

Topic nulled.

Loading a savestate from one game to another or whatever is NOT a "glitch." That's unexpected behavior as a result of loading RAM from one game over another. It does not imply an error in programming in any way whatsoever, which is what a "glitch" entails.

I told you this multiple times when you PMed me about it, so to come here once in a blue moon and still see it is quite annoying…

there are some in the Pokemon glitch community that feel that anything that looks messed up can be categorized as a "glitch", regardless of the means used to create said mess-up. I've always said that the term "glitch" strictly refers to programming errors in the actual game, and that fucking with the ROM, RAM or a savestate doesn't count because that isn't an error in the game (any program will react badly to corrupted data or code). Hence why I've said, to the people who think they "discover" something every time they change a few bytes of RAM and create an unintended side-effect, and to the guy who apparently "discovered" Boean (a "glitch pokemon" in some 3rd gen game that doesn't actually have data in-game and is created with a mass of action replay codes), it seems that all you've done is change Sonic's sprite.

While I personally don't feel I'm in the right to decide what constitutes a "glitch" in the Pokemon community, even though I refuse to allow "glitches" created by RAM or savestate manipulation onto GCL, there seems to be a divide. The Sonic community, however, seems to be in agreement about what constitutes a "finding", and that seems to exclude "findings" involving memory alterations or debug mode.

I don't want to stick my nose in Caspar, after all I'm used to the Pokemon stuff. Personally though, if the best "glitches" we can come up with involve changing Sonic's sprite, it'll just seem pathetic to outsiders (and to the "established" sonic forums who regard that as "hacking" moreso than glitch-finding).

I can understand, though, that Pokemon glitches are much easier to find than Sonic ones, so severly limiting the definition might resolve in nothing being found at all.

I've always said that the term "glitch" strictly refers to programming errors in the actual game, and that fucking with the ROM, RAM or a savestate doesn't count because that isn't an error in the game (any program will react badly to corrupted data or code).

I've always said that the term "glitch" strictly refers to programming errors in the actual game, and that fucking with the ROM, RAM or a savestate doesn't count because that isn't an error in the game (any program will react badly to corrupted data or code).

Well then, why did you work so hard on the Glitchdex, Itemdex, Attackdex, etc?

I've always said that the term "glitch" strictly refers to programming errors in the actual game, and that fucking with the ROM, RAM or a savestate doesn't count because that isn't an error in the game (any program will react badly to corrupted data or code).

Well then, why did you work so hard on the Glitchdex, Itemdex, Attackdex, etc?

Because those are actually accessable though ways without gameshark and are in the ROM's coding.  Some need Gameshark but they are still there.

I've always said that the term "glitch" strictly refers to programming errors in the actual game, and that fucking with the ROM, RAM or a savestate doesn't count because that isn't an error in the game (any program will react badly to corrupted data or code).

Well then, why did you work so hard on the Glitchdex, Itemdex, Attackdex, etc?

Because those are actually accessable though ways without gameshark and are in the ROM's coding.  Some need Gameshark but they are still there.

I don't really agree with that logic. So, you say that inaccessible variables that are alongside inaccessible unusual variables can be allowed to be called glitches. But I don't see a real reason to do so, if you're not allowing the calling of results from changing a byte in RAM, that cannot be changed using a programming glitch, to unusual variables a glitch.

I've always said that the term "glitch" strictly refers to programming errors in the actual game, and that fucking with the ROM, RAM or a savestate doesn't count because that isn't an error in the game (any program will react badly to corrupted data or code).

Well then, why did you work so hard on the Glitchdex, Itemdex, Attackdex, etc?

Because those are actually accessable though ways without gameshark and are in the ROM's coding.  Some need Gameshark but they are still there.

I don't really agree with that logic. So, you say that inaccessible variables that are alongside inaccessible unusual variables can be allowed to be called glitches. But I don't see a real reason to do so, if you're not allowing the calling of results from changing a byte in RAM, that cannot be changed using a programming glitch, to unusual variables a glitch.

Kyouki, you can access near all glitch pokemon with the ditto trick and you can see the others via Old Man glitch trainers and glitch HOF.  It's in the game code.

I've always said that the term "glitch" strictly refers to programming errors in the actual game, and that fucking with the ROM, RAM or a savestate doesn't count because that isn't an error in the game (any program will react badly to corrupted data or code).

Well then, why did you work so hard on the Glitchdex, Itemdex, Attackdex, etc?

Because those are actually accessable though ways without gameshark and are in the ROM's coding.  Some need Gameshark but they are still there.

I don't really agree with that logic. So, you say that inaccessible variables that are alongside inaccessible unusual variables can be allowed to be called glitches. But I don't see a real reason to do so, if you're not allowing the calling of results from changing a byte in RAM, that cannot be changed using a programming glitch, to unusual variables a glitch.

Kyouki, you can access near all glitch pokemon with the ditto trick and you can see the others via Old Man glitch trainers and glitch HOF.  It's in the game code.

Yes, but not when it comes to glitch items. Then again, you could use glitch Pokemon to edit the items in your bag. But it doesn't seem to be well-known, and doesn't seem to exactly work well.