Skip to content
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

Open
70B43r opened this issue Feb 12, 2024 · 6 comments
Open

Timeout on trying to claim another box after reveal sequence #19

70B43r opened this issue Feb 12, 2024 · 6 comments

Comments

@70B43r
Copy link

70B43r commented Feb 12, 2024

2024-02-12 21_46_22-STFC
2024-02-12 21_46_53-STFC 2
2024-02-12 21_48_46-STFC 3

I'm on Version 0.5.4 and happens since update.

@netniV
Copy link
Owner

netniV commented Feb 24, 2024

That is a known issue scopely introduced when they add the extra button and did some weird behind the scenes stuff....

@tashcan
Copy link
Collaborator

tashcan commented Mar 15, 2024

Does it make sense to just remove that entire thing in the patch again, the functionality is in the game now, no? @netniV

@netniV
Copy link
Owner

netniV commented Mar 15, 2024

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.

@tashcan
Copy link
Collaborator

tashcan commented Mar 16, 2024

Wait. Really? I thought the issue was with the stay in bundle code?

@netniV
Copy link
Owner

netniV commented Mar 16, 2024

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.

@tashcan
Copy link
Collaborator

tashcan commented Mar 16, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants