-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tri Force Heroes stuck on triforce glitch #50
Comments
Some precisions on this, I was able to match in a working room with challenges by selecting no challenge (and the triforce worked). So I think this happens when a player has not unlocked special challenges yet (from a save file before beating the first world, the woodlands) matches in a challenge room. |
Same thing happens when my friends select the same thing ("Slow and steady"), so I don't think it has to do with that. The game was working fine before today, we even got some challenges for woodlands in, but it just seems to have stopped working suddenly. |
Yes, that's what I also found out. Maybe this is the reasol it happens? |
Me and my friends all completed the same missions together (we did full resets so we could do it all together), so it wouldn't be that either. All of us have the challenges unlocked, so I'm unsure what's causing this. It does seem to be related to challenges though. I haven't seen it happening with anything else. |
I have found a glitch and the steps to reproduce it in Tri Force Heroes.
What should happen :
What happens :
Why this happens :
I suspect it's because filters don't get applied (for example slow and steady or fast, or with/without challenge) and people still get matched together. For "Slow and steady" or "Fast game" it shouldn't cause issues and allow to find more players which is cool, but the game doesn't know which level select (with or without challenge) it should load when people with different challenge preferences match up.Edit : This does not seem to bethe right reason, see this instead
The text was updated successfully, but these errors were encountered: