Okay this is kinda annoying. Playing through adventure mode right now and I dont know whats going on. Some squares that are unlocked say I cant play it cause I havent met certain requirements and then im also trying to get to Agitha right now but her square wont unlock despite beating all the squares to the right and bottom of her.
In order to make it to Agitha you need to unlock the final character in Legend mode (this happens after you beat Cia.)
I'm assuming you're on the square to her right (east) and it's not letting you enter the battle, giving you some nebulous message about requirments :3
EDIT:
That's one of the most annoying things about testing games. It's easy to crash the things but the real challenge is working out what causes them. Particularly if you're not lucky enough to get a crash dump for the dev team to have a look at. And it gets even worse if you can't repeat it lol.
At the end of every project you've got a load of Once Only crash bugs that have to be 'Closed As Not Seen'.
I managed to break Netflix the other day which also broke the Wii U OS too lol. Netflix crapped out on me, the TV display went black. I was forced to quit the app with the Home button but after I returned to the Wii U Menu screen the TV display was still black, no Plaza lol. Had to switch the console off and on again twice, the first time the GamePad couldn't connect to the console and the second time everything was okay.
I haven't managed to break Hyrule Warriors yet though which is surprising for me, I tend to break software pretty easily which is why I made such a good tester. Not well enough to work at the moment though and haven't been for some time, would love to get back to testing when I'm able to get back to things though. It's the only job I've done in my life that I've enjoyed doing.
Heh, yeah. I hate those bugs that only happen once in a blue moon and you can't find reliable reproduction steps for or the ones that you work on for ages without it seeming to have any pattern only to be head-slappingly obvious when you find the trigger.
When Crackdown's DLC came out there was a bug that wiped the player's entire save data that had us baffled until I realised that during most tests we tended to go into single player first : turns out, the bug would only manifest if you immediately jumped into multiplayer after downloading the patch :3
Also, I feel like when you work in QA you gain the 'QA touch' which means even games that used to work fine for you will now break on you. I feel it's weakened for me since I moved on from testing to other roles but stuff still goes haywire more than the days before I worked in Quality Assurance