-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Timeout on trying to claim another box after reveal sequence #19
Comments
That is a known issue scopely introduced when they add the extra button and did some weird behind the scenes stuff.... |
Does it make sense to just remove that entire thing in the patch again, the functionality is in the game now, no? @netniV |
It's the skip reveal that would be lost. I love not having to waste time watching that. I just don't use that new button ever, but that's me. |
Wait. Really? I thought the issue was with the stay in bundle code? |
No, I tested this and found that only when you turn off Reveal skip does it work as intended by scopely. I also put in debug code to check that the stack of scenes was the same and being replaced and then returned to the same values during an initial call and via the extra button. There was no difference on both ways of collecting. I have multiple ideas on why, but hitting escape makes it work so my primary one is this suggests there is a scene being dismissed that's not visible, which then makes the rest carry on. So skipping the reveal sequence, maybe a visibility value is being missed and thus causes the issue? Because it's not visible, no transition/timing functions are kicking in? Note, it doesn't call the doSkipReveal function when the extra button is pressed. |
Great. Scopely not even implementing things correctly according to their internal functions. Fun if someone ever decides to do skipreveal which is a feature in their whole UI thing...bunch of rubbish |
I'm on Version 0.5.4 and happens since update.
The text was updated successfully, but these errors were encountered: