20xx hack pack melee skins 4.0 mod#
as a general UX thing, players can't tell what skin mod (metal/etc) they have once they pick SD Remix/Pal versions of a character, as the purple w/ red accent panel/yellow with cyan have priority in the portrait background.spamming SD remix/PAL selectors (with the dpad) and rapidly selecting master/crazyhand and tapping Z freezes the console.For example, if I change Pichu to Masterhand, then tap X to change the character color, it cycles through the actual pichu skins, through golden roy, then seemingly endless waves of light blue yoshi. However, unlike the stock glitch, the stocks in-game are still those belonging to the appropriate character, so only the character portrait seems to change. if I perform the stock glitch as pikachu, I can get the stocks & portraits of green peach, and b&w kirby if I switch to crazyhand and mash x, these are the portraits the game cycles through, followed by seemingly endless portraits of azure yoshi). This allows a player to pick a portrait in a similar way to what one would be able to pick using the non-z form characters via the already known vanilla melee Stock Glitch (ie. character color selection for all the z-alternates (except for sheik) don't bound the skin selection properly, which results in the player possibly being able to iterate through arbitrary memory locations (to an unknown end).The Hyrule Castle ai's recovery glitching can be reproduced fairly easily by throwing an AI player off the left side of the stage repeatedly, with random DI on. Using the same technique on Hyrule Castle, the AI will inconsistently lose any notion to recover properly (the objective marking orb, while it properly displays the light gray indicator showing the AI intends to recover, seems to remain at the feet of the AI character itself as it falls, so the AI never attempts to return to the stage), or sometimes loses any objective, when knocked off the left side of the stage. By looking at the AI objective (the colored orb that shows where they're going to) in debug mode, the AI gets no objectve on Mount Olympus while the player is standing on either of the side platforms (during singles, 1 player vs 1 cpu), and therefore doesn't move. The AI glitches out on two hacked stages, Mount Olympus and Hyrule Castle.All of these spawn the stage that would be in the slot on the standard stage select screen. the 3rd page's stage previews are incorrect for the following stages: Green Greens, Hyrule Temple, Great Bay, 'Custom Platform Battlefield' which is Brinstar, and Fourside.item spawn locations aren't set or are offstage for most of the hacked stages.Pokemon Stadium (No Transformations) isn't light blue as advertised.These are minor and aren't really issues in as much as they're notes. This is not meant to be an exhaustive list, just things I've jotted down in the past few days, based on what I've encountered in the past. I also deleted all previous 20XX saves from the memory card used before running beta 4.Ĭertain things I'm going to point out were also reproduced or observed on other people's hardware/images of beta 4 while at Genesis 3. If needed, I can reproduce all this on a plain 20XX image. Note the md5 will be different because I changed the file header from GALE01 to GALEXX, and changed the game description string.
20xx hack pack melee skins 4.0 iso#
The md5 of the iso I built and tested all of this is: af6324fd0be4805b2ec1475e04dac269. Everything noted was discovered or reproduced using 20XX 4.0 beta 4, on a Wii, with the game loaded using Dios Mios. Also, I'm trying to avoid things you guys have seen XX times, like 'where are the cpu codes' and the wavedash color overlays menu crashing the game. Everything I've tested and have notes on I've put in spoiler tags to avoid creating a massive tl dr post. I met DRGN at G3 and he convinced me to sign up on smashboards and post about all the things I've noticed in the latest 20XX betas, so here goes.
0 kommentar(er)
