Glitch City Laboratories closed on 1 September 2020 (announcement). This is an archived copy of a thread from Glitch City Laboratories Forums.
You can join Glitch City Research Institute to ask questions or discuss current developments.
You may also download the archive of this forum in .tar.gz, .sql.gz, or .sqlite.gz formats.
Not purely by virtue of being glitch trainers, though. Consider the ZZAZZ glitch (and Jacred inventory corruption); the effects can be game-breaking if you don't add a terminator to your name before saving, but like any other effect, they're traceable.
normally wild invalid glitch trainers crash the game.
Not purely by virtue of being glitch trainers, though. Consider the ZZAZZ glitch (and Jacred inventory corruption); the effects can be game-breaking if you don't add a terminator to your name before saving, but like any other effect, they're traceable.
normally wild invalid glitch trainers crash the game.
It's also possible your emulator doesn't handle all the possible details of invalid game states properly if it's a phone one.
Handling of invalid opcodes is the first thing that comes to mind. ZZAZZ (I mean the person this time) made a follow-up video to the famous "4 4 Hy's true cry" that explained why it was possible on the ever-maligned VBA that might have more to add, though, if you're interested.Not purely by virtue of being glitch trainers, though. Consider the ZZAZZ glitch (and Jacred inventory corruption); the effects can be game-breaking if you don't add a terminator to your name before saving, but like any other effect, they're traceable.
normally wild invalid glitch trainers crash the game.
It's also possible your emulator doesn't handle all the possible details of invalid game states properly if it's a phone one.
"Possible details of invalid game states", does that mean game crashes?
Handling of invalid opcodes is the first thing that comes to mind. ZZAZZ (I mean the person this time) made a follow-up video to the famous "4 4 Hy's true cry" that explained why it was possible on the ever-maligned VBA that might have more to add, though, if you're interested.Not purely by virtue of being glitch trainers, though. Consider the ZZAZZ glitch (and Jacred inventory corruption); the effects can be game-breaking if you don't add a terminator to your name before saving, but like any other effect, they're traceable.
normally wild invalid glitch trainers crash the game.
It's also possible your emulator doesn't handle all the possible details of invalid game states properly if it's a phone one.
"Possible details of invalid game states", does that mean game crashes?
Both terms work. The possible bytes exist, but the hardware knows it's supposed to lock up if it tries to read one as an instruction. The Virtual Console interprets them all as nops, but that emulator can at least be called official. An emulator that keeps the game running after hitting one is just being inaccurate.
I may be interested in the future, occasionally (very rarely though) I use VBA on my laptop. As for my main emulator, it can run into invalid (or unknown is the term?) opcodes, it's happened with 0xDC's Pokédex entries a few times and once with 0xF1's backsprite caused the game to halt.
Just noticed you're using VBA.Handling of invalid opcodes is the first thing that comes to mind. ZZAZZ (I mean the person this time) made a follow-up video to the famous "4 4 Hy's true cry" that explained why it was possible on the ever-maligned VBA that might have more to add, though, if you're interested.Not purely by virtue of being glitch trainers, though. Consider the ZZAZZ glitch (and Jacred inventory corruption); the effects can be game-breaking if you don't add a terminator to your name before saving, but like any other effect, they're traceable.
normally wild invalid glitch trainers crash the game.
It's also possible your emulator doesn't handle all the possible details of invalid game states properly if it's a phone one.
"Possible details of invalid game states", does that mean game crashes?
I may be interested in the future, occasionally (very rarely though) I use VBA on my laptop. As for my main emulator, it can run into invalid (or unknown is the term?) opcodes, it's happened with 0xDC's Pokédex entries a few times and once with 0xF1's backsprite caused the game to halt.
Just noticed you're using VBA.Handling of invalid opcodes is the first thing that comes to mind. ZZAZZ (I mean the person this time) made a follow-up video to the famous "4 4 Hy's true cry" that explained why it was possible on the ever-maligned VBA that might have more to add, though, if you're interested.Not purely by virtue of being glitch trainers, though. Consider the ZZAZZ glitch (and Jacred inventory corruption); the effects can be game-breaking if you don't add a terminator to your name before saving, but like any other effect, they're traceable.
normally wild invalid glitch trainers crash the game.
It's also possible your emulator doesn't handle all the possible details of invalid game states properly if it's a phone one.
"Possible details of invalid game states", does that mean game crashes?
I may be interested in the future, occasionally (very rarely though) I use VBA on my laptop. As for my main emulator, it can run into invalid (or unknown is the term?) opcodes, it's happened with 0xDC's Pokédex entries a few times and once with 0xF1's backsprite caused the game to halt.
No.
http://bgb.bircd.org/