1
edit
Talk:Mew glitch: Difference between revisions
→Details on removable object side effect: new section
(→Details on removable object side effect: new section) |
|||
| Line 413: | Line 413: | ||
::In your example, the message for the PokéMart shopkeeper has a text ID of 01. This shares the same ID for the Rocket at the end of Nugget Bridge. --[[User:Chickasaurus|Chickasaurus]] ([[User talk:Chickasaurus|talk]]) 19:31, 3 September 2013 (UTC) | ::In your example, the message for the PokéMart shopkeeper has a text ID of 01. This shares the same ID for the Rocket at the end of Nugget Bridge. --[[User:Chickasaurus|Chickasaurus]] ([[User talk:Chickasaurus|talk]]) 19:31, 3 September 2013 (UTC) | ||
== Details on removable object side effect == | |||
I couldn't find these details elsewhere, but I'm not really sure where they belong in the article as it is currently organized (it seems wrong to put it all under the Snorlax glitch heading), so I'm leaving them here instead for anyone who cares. I should note that I've only actually gone through the motions to verify the side effect for the Route 25 method. Everything about the Route 8 method is conjecture based on a quick look at the lists for those areas, so someone should make sure it holds up during gameplay. | |||
The article mentions a list of removable objects that gets updated whenever you move between areas. This list is located at memory address D5CE. Its elements are two bytes apiece, and it is always terminated by a special element that begins with "FF". The list is only rewritten up to the first byte of terminal element when it is updated, so the second byte of the terminal element comes from the last area you visited that has at least one more object than the current area. This part of memory persists through a save, but it is zeroed out for a new game. | |||
After a special encounter, the second byte of the terminal element is used as an index into the removable object visibility bit field (located nearby, starting at memory address D5A6). The corresponding bit is set, which makes an object disappear from the world, if it was visible before. Aside: it follows that the code that updates the object list should have a special case to write the second byte of the terminal element when entering an area with a one-time encounter, although I did not verify this. | |||
So, what all does this mean for the two methods for capturing Mew mentioned in the article? | |||
The first method, which has you returning to Route 8, has different outcomes depending on how you get there. If you fly to Fuchsia City right after fighting the youngster, then the TM19 nearby disappears. That's because Route 8 and Fuchsia City both have zero removable objects, which leaves all but the very first byte of the list from Route 25 in memory. Flying to Fuchsia City from other areas has different results. If you walk through Saffron City instead, then the Rocket in front of Copycat's house goes away. | |||
The second method, which has you returning to Route 25 from Cerulean City, has only one outcome. When you first arrive in Cerulean City, there is a policeman guarding the door to a house that has been broken into. If you talk to Bill, this policeman is hidden to let you through the door, and an identical policeman (who had been hidden from the start of the game) shows up one tile to the east. After you fight Mew, this second policeman is hidden once more, leaving no one by the door. This side effect can be avoided entirely by fighting Mew before talking to Bill. | |||
[[User:Ocean|Ocean]] ([[User talk:Ocean|talk]]) 05:44, 14 September 2015 (UTC) | |||