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.
On that note, can we have pages on glitched speedrun routes (they are public domain, right?) with detailed analysis for the glitches? Not only would that be useful to people new to speedrun, having those detailed analysis may also help with finding alternate routes (maybe backup strats) or even improvements. Plus, for some glitches we would be able to just link to examples in the speedrun, instead of putting overcomplicated examples in the glitch page.
I feel it needs to be more verbose, maybe 5 instead of 4, due to Level 2 in the 4-tier system having some ambiguity due to varying glitch use/unintentional-damage potential/strength.
Of course there will be different "sublevels" in each level (as I mentioned, even ACE methods can be different in application), but the line can be really difficult to draw. If you can come up with a relatively clear criteria to split my level 2, then sure. Otherwise, I think it's best to keep it simple.
Oversights:
Just some random oversights left in the game, whether it be leftovers from a previous version of a map, or surfing on the statues. This can be 1A. Things in this category just doesn't do much to affect gameplay, and is there for a good chuckle.
Useful Harmless Glitches:
Basically glitches in this category can help the player and of course doesn't do harm to your save file. Speedrunning glitches can fall under this too. Going with the numbering system this can be 1B.
Advance glitches:
Glitches in this category can alter the game's code and may potentially be harmful, especially if you don't know how to perform them. ACE would definitely fit this category, perhaps other glitches can fall under this category too? This would be 2A.
Harmful glitches:
As the title states, these glitches will either destroy your save file, or simply make the game crash/freeze. Glitch moves that cause Super Glitch would fall under this category of course, even though in some occasions the move doesn't do harm. The divide by zero growth rate glitch found in Yellow can fall under this glitch category as well too. This can be 2B.
I'm glad that you chimed in! That approach is yet another viable option. I'm wondering now, for anyone from PRAMA, GCL, or both, what do you consider the difference between the two sites?
At PRAMA, we try to organize the glitches and pages in a "learn how to glitch" fashion. We present minor glitches, then split major glitches in three categories called "For a good start", "Upper-level glitches" and "Advanced techniques". These are categories solely based on the amount of knowledge required to perform the glitch (even if the glitch is very simple but has an ACE pre-requisite for example). The idea is that the newcomer starts its journey into glitching by learning the basics and then progressively moves on complicated stuff.
But that's the main purpose of PRAMA - to provide accurate but newbie-friendly information that will make them want to jump into it. GCL is something else, so those categories probably won't fit here.
The ones I've seen have all been just a few clicks away on PSR, though in the case of some newer ones they were only linked in the Discord first. I'm sure those were made public too, though. They do have the consistent "flaw" of merely being guides, for instance saying "get to Viridian Forest this way" instead of saying (or even mentioning) "this activates this meta-map script when these values have been set". However, I'm not sure if we should just copy them and expand on them, as we aren't PSR and routing isn't our particular focus…I might change my mind on that, though. I think the relevant glitches already link to examples in recorded runs, though if they aren't, they should be.
I mean… visual examples would help with understanding the steps to do the glitches/tricks for most people.
Linking to speedrun videos doesn't do much, because as I said they have the wrong focus, and some of the glitches actually need quite a bit of explaining.
After thinking about this, I think the fact routing isn't our focus is exactly why we want to have copies of the routes on our own pages, so that we can separate the glitch part from the pure routing part and properly focus on the former. We can always gloss over the parts that aren't glitch-related.While I don't particularly agree, I'll add it to Wiki tasks for now as a possibility. They would be a good example of "how to break the game and why it works", but routes are constantly receiving optimizations, and the glitches involved are already getting their own pages.
Taking back whatever I said. This is just brilliant. I'll add any articles like this to the Reference documents category, as well as their own. I think speedrun routes documented in this manner deserve a sidebar spot more than GameShark codes, but I'll wait for at least one more vote on that. (I'll help if I can, but honestly with my current level of knowledge I don't think there's much I could do.)
After thinking about this, I think the fact routing isn't our focus is exactly why we want to have copies of the routes on our own pages, so that we can separate the glitch part from the pure routing part and properly focus on the former. We can always gloss over the parts that aren't glitch-related.
Linking to speedrun videos doesn't do much, because as I said they have the wrong focus, and some of the glitches actually need quite a bit of explaining.