Achilles1515
[/USER]
I've put together a list of known bugs; it can either be linked from the main post and I'll maintain it or just added to the main post and maintained by you.
Troubleshooting/Known Issues
For problems pertaining to the in-game toggles, refer to the relevant code's section in the original post for known issues and workarounds; it is very likely your issue is documented there.
• Missing features such as PAL characters and alternate costumes, debug mode/in-game toggles, or alternate stages.
◦ Caused by using an outdated version of the 20XX hack pack; download the most recent version from the original post.
◦ The current version number is indicated in the original post at the top of the page. Post-3.00 versions indicate the version number ingame in the debug menu (at the top of the screen).
◦ Pre-3.00 versions have a blue debug menu with white text, which easily distinguishes them from more recent versions (which have a grey debug menu with yellow/white text).
If you installed the version linked in the description of Beanwolf's installation tutorial video on YouTube (https://www.youtube.com/watch?v=NbglwFv5PmA), then you will have installed v2.06 (which is outdated). Again, download the most recent version from the original post.
• When playing on Dolphin, the game freezes upon pressing start at the start menu.
◦ Disable global netplay codes.
• Some text, mainly punctuation, contains artefacts ("pixels"/"static"). This is visible in places such as the name entry screen and the TV in the background of Pokémon Stadium.
• Certain codes do not work in Dolphin.
◦ This will be fixed in the next update.
• The Sheik CPU will occasionally teleport to the ground.
◦ This is a side effect of the method used to prevent the CPU transforming into Zelda. There is currently no solution to this problem.
• Blue Pokémon Stadium texture and Red Caption Falcon alternate costume textures do not display.
◦ This will be fixed in the next update.
• The camera on the no transformations version of Pokémon Stadium does not work correctly; it always acts the way the camera on vanilla Pokémon Stadium does during a transformation.
• Activating the hitbubble display on Dreamland causes the characters to become invisible. This also happens occasionally on Pokémon Stadium (depending on the camera angle), and possibly other stages too.
◦ This is a bug with the hitbubble display in vanilla Melee. There is currently no known solution to this issue.
• Playing single player modes, viewing trophies, or playing with Japanese language settings can cause the game to freeze.
◦ This is caused by trophy textures/Japanese-specific files being overwritten so that new elements (such as PAL character DAT files) can be added in their place. When the game tries to load the overwritten files it crashes. Avoid using these modes until the issue is resolved.
• Being unable to change the CPU to Sheik/SoPo/Giga Bowser/Fighting Wire Frames on the character select screen.
◦ You cannot toggle the character while holding the CPU's character selection token; you can only toggle the character while holding a player's character select token.
◦ Hover the player's token over the character, press the Z button, put down the player's token, and then place the CPU's token on the character. The characters remain toggled universally, so toggling the character for one player will also toggle it for all other players and CPUs.
• CPUs mash out of Donkey Kong's Cargo Throw abnormally quickly.
◦ This is caused by the CPU's repeated DI/tech inputs combined with the low number of inputs required to mash out of Cargo throw. There is currently no solution to this problem.
• When using the satly runback feature (L+R+A+B+Start) to reset a match, the match will be restarted with the default stage music even if the random stage music toggle is on. There is currently no solution to this problem.
• There have been reports of miscellaneous issues (such as the analogue stick and triggers being read incorrectly) which have no clear cause; in many cases, there is no change made in the 20XX hack pack that should logically cause these issue.
It is not clear whether they are caused by the 20XX hack pack or if they are a result of other issues such as bugs in the USB loader being used (Nintendont is a possible cause). Some issues are mentioned here:
http://www.reddit.com/r/SSBM/comments/2rew8b/psa_regarding_20xx/
Remember that some issues may be caused by accidental toggling of codes (people have complained of things like "increased chances of phantom hits" because they've accidentally toggled invulnerability); if 20XX is being used for a tournament, be sure to change the settings to match vanilla Melee in all relevant areas (disable all in-game toggles, enable Dream Land wind, etc.).