December 08, 2019, 09:14:02 am
0 Members and 1 Guest are viewing this topic.
Sherkel Last Saturday at 8:00 PM@luckytyphlosion Raven has been documenting stats/sprites/dex entries/etc. of Pokemon with invalid index numbersSo like, "classic" glitch research so to speakluckytyphlosion Last Saturday at 8:00 PMempiricalis he dumping them from the ROMSherkel Last Saturday at 8:00 PMI don't knowRavenfreak Last Saturday at 8:59 PMI’m actually just documenting them manually using gameshark codes to encounter each glitch Pokémon. :V I’m taking the names, types and glitch moves from my save file. It’s not the quickest way to get the information but it works. :stuck_out_tongue:ShinySkitty Last Saturday at 9:00 PMin which game?bbbbbbbbba Last Saturday at 9:01 PMHow could you know they are not coming from the RAM?luckytyphlosion Last Saturday at 9:10 PMsad:morphoff:Sherkel Last Saturday at 9:40 PMIt's just how it was done in the olden daysluckytyphlosion Last Saturday at 9:41 PMOLDENyeah, back when glitching was actually fun :morphon3d:Sherkel Last Saturday at 9:42 PMNow we know that keeping the current enemy mon byte set throughout the battle/dex appearing can have other effects as those read from RAM, but keep in mind when this whole thing started and how the views of relevance of changedluckytyphlosion Last Saturday at 9:42 PMhey maybe I can convince @bbbbbbbbba to do what I'm too bothered to do and actually dump glitch mon info by reading the ROMSherkel Last Saturday at 9:42 PMIf we ever had some sort of "GlitchDex 3.0" it would be pulled straight from the ROMActually, @Melodic Evie the Bird Mother ❤ 🦉 may have done that when revising the English RBY entries, but idk for sureluckytyphlosion Last Saturday at 9:44 PMyou mean the literal glitchdex entries?waitSherkel Last Saturday at 9:44 PMNo, what the site calls the GlitchDexIt dates back to before GCL, I thinkluckytyphlosion Last Saturday at 9:44 PMhow does missingno's pokedex entry have that long-ass crywaitis that missingno's cryor are those sounds generated from the pokedex entrybecause that shouldn't be possiblefor the sounds to be generated from the pokedex entrySherkel Last Saturday at 9:46 PMI don't mean to dismiss what @Ravenfreak is doing, in fact my point is that doing this sort of thing without obsessive precision is fine for this purposeUhh, lemme see that pageluckytyphlosion Last Saturday at 9:46 PMwhat even is the purpose of the glitchdexSherkel Last Saturday at 9:46 PMI doubt it has the 30 minute Yellow VC cry with the 20khz beepluckytyphlosion Last Saturday at 9:46 PMkekyellow missingno cry is superficial at bestSherkel Last Saturday at 9:46 PM> what even is the purpose of the glitchdexAs far as "glitching" today goes, nothingluckytyphlosion Last Saturday at 9:46 PMit's the result of random corruptionbased on the corrupted audio bankwhen its sprite is decompressedSherkel Last Saturday at 9:47 PMAny that execute arbitrary code are referenced on the pages with the exploits that use that callThat's basically all glitch criesluckytyphlosion Last Saturday at 9:47 PMthe reason it's so long on yellow VC is because the cry somehow ends up pointing to OAM (on both console and VC)Sherkel Last Saturday at 9:47 PMI mean, some are consistent, but consistently reading from somewhere that isn't meant to be a cry nonethelessluckytyphlosion Last Saturday at 9:48 PMbecause of inaccessible OAM the cry eventually ends when it reads an $ffbut VC doesn't have inaccessible OAMso it actually reads a lot more non-zero entrieswith that adding 8 more minutes to its so-called crySherkel Last Saturday at 9:50 PMWhat were you referring to earlier, by the way? I think the links to cries in the GlitchDex for the most part got brokenAnd I see none in MissingNo.'sAnyway, the pret/PSR perspective is very different from what's in the GCL databasesluckytyphlosion Last Saturday at 9:52 PMuh this is neither of those perspectivesthis is my perspectiveSherkel Last Saturday at 9:52 PMI mean the pragmatic oneluckytyphlosion Last Saturday at 9:52 PMpret and PSR care even less about documenting glitches/behaviour than I doahSherkel Last Saturday at 9:52 PMGCL wants to incorporate that but keep in mind but also dates back to before 2005When the perspective was "huh, what does this do? Oh, cool."And I have a lot of sympathy for that oneluckytyphlosion Last Saturday at 9:53 PM"glitches r kewl"Sherkel Last Saturday at 9:55 PMYes, you do care more about documenting from what I can tell. I don't know exactly what PSR thinks of that, but based on how hard it is to find their actual findings I can guess they don't care that muchAnd pret is just focused on the purpose that's in the nameluckytyphlosion Last Saturday at 9:56 PMwell the research PSR does is mainly focused around speedrunningyou can really see the appliedness of it with manipsextracting all the relevant info of how the game ticks to a cycle towards manipsSherkel Last Saturday at 9:57 PMOf courseI'd say they've done more for glitchology than any other groupluckytyphlosion Last Saturday at 9:57 PMpokecrystal's maintainers are more focused around making it a usable base for hackingwhile still keeping it matchingSherkel Last Saturday at 9:57 PMBut all they seem to publish are dumbed-down descriptions of routesluckytyphlosion Last Saturday at 9:58 PMyes, because the people who use the routes don't know how to glitchthey just executeit's not necessary to know how the glitches work in most cases (although 151 is an exception, you do need to at least know the techniques behind some of the glitches)Sherkel Last Saturday at 9:58 PMHence why I want GCL to do thatluckytyphlosion Last Saturday at 9:58 PMGCL to do whatSherkel Last Saturday at 9:59 PMDocument stuff properlyluckytyphlosion Last Saturday at 9:59 PMwell I think a good way to motivate research is to tie that research in with a meaningful purpose that can unite people togetherspeedrunning is oneSherkel Last Saturday at 9:59 PMThe problem is that with the obvious exceptions, the people involved/trusted/active/etc are very out of touchMyself includedluckytyphlosion Last Saturday at 10:00 PMfor pret the common cause is improving the disassemblies/decompilationsalso, a button challenge for sm64so if you can find some common cause that can unite people together then you can get your research donebecause right now it's not really defined what the research is forSherkel Last Saturday at 10:00 PMThat's a good pointluckytyphlosion Last Saturday at 10:01 PMit doesn't seem like anyone wants to document for the intrinsic value of doing soSherkel Last Saturday at 10:01 PMAnd full disclosure, GCL's still is (as far as I know) "glitches r kewl"So that could be why we've fallen behind
well. I too get it done by manually using gameshark codes to encounter each glitch Pokémon, cause i don't know how to do it in any other way.If that is the case, then ALL the pages for the international glitchdex's also have roots in being generated thay way. infact, all the name strings for all the pages are directly from me encountering them all and slowly write down each name of them all. and then slowly adding each to a new page entry.So if there is a "proper" way to do things, then the reason why i haven't done it personally is because i don't know how to do it. and i can only do as much as i can do. :0
So if there is a "proper" way to do things, then the reason why i haven't done it personally is because i don't know how to do it. and i can only do as much as i can do. :0
honestly glitches aren't fun anymore because everyone has a huge, raging hate boner for empirical testing.
But, like I said, I have no problem with doing them "the old way". I gave you your current rank for it. The data is still there and most likely correct. Is that a polite way of saying I don't especially care? Maybe, but it doesn't mean others can't and that it isn't still work done for the site. The whole Decamark thing made me realize how needless it was to go too far with documenting glitch Pokémon species (aside from ????? (000) and MissingNo./'M, their functionality is fairly nonexistent), but others are free to disagree.
Basically, I have trouble seeing the point in documenting glitch species just for its own sake, but also respect what kicked this site off originally, the idea of tearing into these games with whatever means are available and reporting what happens.
Let's just write a script or smth that does the testing and documentation for us, then? If we're gonna be systematic about it, let's just do it with some helper program for a (hacked) console or emulator and take human error out entirely?Seriously.