A fix is on the way, but for now, players are advised to check Nintendo's guide to bypass this glitch.
http://www.nintendoworldreport.com/news/35773
Nintendo has acknowledged that there is a save data corruption bug in Pokémon X and Pokémon Y and is currently preparing a solution for it.
Many reports have appeared online since the game's worldwide launch on October 12 from players who were experiencing issues upon loading their file after saving their progress in Lumiose City. The glitch will cause the game to not respond to any control input once it has been reloaded.
A free application will be released on the Nintendo 3DS eShop in the near future that will allow players to recover their game data. In the meantime, Nintendo has published a detailed diagram on how the glitch can be avoided, which is shown below.
When I found out about this I had last saved in Lumiose but I had saved in the Pokémon Center so I dodged a bullet there.
Skyward Sword had an issue like this as well but I really can't say that Game Freak has slacked off on their QA. I can't specifically call them out anyway as consoles devs in general have slacked off now that they have the ability to patch their games. That functionality is nice for fixing bugs but when there was no way to fix console game bugs we didn't seem to have as many bugs to fix. Ironically the mechanism to fix bugs has made console games more buggy.
But that everyone doing it is a weak excuse. The whole industry should get better at this, Game Freak included.
When I found out about this I had last saved in Lumiose but I had saved in the Pokémon Center so I dodged a bullet there.
Skyward Sword had an issue like this as well but I really can't say that Game Freak has slacked off on their QA. I can't specifically call them out anyway as consoles devs in general have slacked off now that they have the ability to patch their games. That functionality is nice for fixing bugs but when there was no way to fix console game bugs we didn't seem to have as many bugs to fix. Ironically the mechanism to fix bugs has made console games more buggy.
But that everyone doing it is a weak excuse. The whole industry should get better at this, Game Freak included.
For the last fucking time, you are getting the wrong devs here.
What makes it worse is that by my understanding that is someplace you have to come back to multiple times. You think a tester or 20 would have ran into it.
Stand by my statement. If you know players are going to be their a lot it should get tested a lot.What makes it worse is that by my understanding that is someplace you have to come back to multiple times. You think a tester or 20 would have ran into it.
Testers don't play the game like a normal player would so they wouldn't be returning to that one area again and again and probably wouldn't save as frequently as a real player. There also might be certain conditions like what Pokémon you have or your outfit or if you're online or whatever. I don't think it's as simple as "save here and it fucks up".
What makes it worse is that by my understanding that is someplace you have to come back to multiple times. You think a tester or 20 would have ran into it.
Testers don't play the game like a normal player would so they wouldn't be returning to that one area again and again and probably wouldn't save as frequently as a real player.
What makes it worse is that by my understanding that is someplace you have to come back to multiple times. You think a tester or 20 would have ran into it.
Testers don't play the game like a normal player would so they wouldn't be returning to that one area again and again and probably wouldn't save as frequently as a real player.
AS a former tester, NO they don't save as frequently as a real player. They save more frequentlyin every area multiple times to makes sure there aren't any issues, even if there is no conceivable way a player would trigger it. I was once testing sign-ins/sign-outs in XBox Live on a title I was working on. One time, I performed a sign-in/out 50 times in a row & triggered a crash caused by a memory leak. No player would ever trigger that issue unless they literally never turned their console off. It was still found and inadvertently fixed.
Nintendo's testers are very good at what they do. I have a hard time believing this wasn't a Known Shippable.
That functionality is nice for fixing bugs but when there was no way to fix console game bugs we didn't seem to have as many bugs to fix.A statement like this completely ignores the fact that games are a whole lot more complicated to program than they were during the NES and SNES era. These days, there's so much more that can go wrong, and so much more to check, it would take such a long time for testers to find everything which would make it impossible to still release games in a timely manner. Not that I'm trying to excuse glitches like this, but this is the reality of increased technology.