Talk:Second type glitch: Difference between revisions

no edit summary
(Created page with "==Pokémon #"152"== This article says "''it appears as either Scyther or Farfetch'd in the English localizations''"... how is this possible, since the glitch can't be done in ...")
 
No edit summary
Line 3: Line 3:


Also, this mentions "''corrupting the player's item pack''"... would it be worth noting that by doing this glitch, a player can see the dummied out items (such as the Pokédex, ?????, and Coin) this way?  I just thought it was an interesting side-effect, since as far as I know, those items are otherwise never viewable without GameShark. [[User:Dannyjenn|Dannyjenn]] 17:48, 18 March 2012 (UTC)
Also, this mentions "''corrupting the player's item pack''"... would it be worth noting that by doing this glitch, a player can see the dummied out items (such as the Pokédex, ?????, and Coin) this way?  I just thought it was an interesting side-effect, since as far as I know, those items are otherwise never viewable without GameShark. [[User:Dannyjenn|Dannyjenn]] 17:48, 18 March 2012 (UTC)
:Hi, I'm sorry for the late response. Yes, I meant in general that in the English localisations, if you force a #152 entry in to the Pokédex it will appear as either {{p|Scyther}} or {{p|Farfetch'd}}. It seems to depends on the version (i.e. Scyther is the "#152" in {{game|Yellow}}, and Farfetch'd is the #152 in English [at least] {{2v2|Red|Blue}}). This is the same result when progress in both games are exactly the same. Registering #152 is possible on a real cartridge in both {{2v2|Red|Blue}} and {{game|Yellow}} via a [http://tasvideos.org/1860M.html save exploit] found by speedrunner Chamale, and expanded by both gia257 and 1337p4wn3r that works in {{2v2|Red|Blue}} as well as {{game|Yellow}}.
===How seeing #152 without cheating is possible in the English versions===
Here's an explanation of the save exploit as mentioned above, in as few words I could adequately describe it (mind you, I suck at electronics and maths and gia257 and 1337p4wn3r [http://tasvideos.org/3256S.html explain] this way better than I can). The trick is to reset the game after pressing 'save' before the save menu appears, which replaces many values in the game's WRAM with 255 values including the total number of Pokémon and relevant details. The relevant individual Pokémon bytes (beginning at WRAM:616B or WRAM:D16A in Yellow) which get changed here are 66 bytes each, and since you have over '6' Pokémon, it allows a massive [[wikipedia:stack overflow|stack overflow]] for placing wrong values into other areas of the game where they shouldn't be, which related to why select button glitches and other memory corruption tricks work because you're swapping post-6 Pokémon you don't have. This means that it's possible to do something like switch the first Pokémon (individual Pokémon data in the WRAM is over 270 bytes long) with the tenth, to cause a stack overflow in which you corrupt all your 18*2 'see' 'own' Pokédex data (beginning at WRAM:D2F7 or WRAM:D2F6 in Yellow) and item data (beginning at WRAM:D31E or WRAM:D31D) which immediately follows. In order to beat the game in under a minutes' game time, he had to work out mathematically how to alter map event data (in which changing to the map number to a certain [[List of locations by index number (Generation I)|glitch map]]) without having all the map data load triggered the Hall of Fame sequence in someway I don't understand).
Note the below is a tool-assisted video, it's a popular way in which people play the game one-frame at a time to beat the game in the fastest way possible, and then generally have another person upload a high quality video for them, not something I'd personally like to spend my time in doing. Unfortunately, nobody has uploaded a slower video of the glitch in real time.
{{youtubevid|EowXU9cZ_S4|BrandMan211|Poison}}
--[[User:Chickasaurus|Chickasaurus]] 19:33, 25 March 2012 (UTC)
2,073

edits