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

Add a Finish button to Collector #17428

Merged
merged 5 commits into from
Sep 7, 2017
Merged

Add a Finish button to Collector #17428

merged 5 commits into from
Sep 7, 2017

Conversation

Hamms
Copy link
Contributor

@Hamms Hamms commented Aug 30, 2017

Also slightly tweak the Collector successs workflow. We now want to no longer automatically send you on to the next level with a congrats dialog when you pass the level with fewer than all of the gems; we now only do that if you collect all gems on the level.

If you collect enough gems to pass the level but not all of them, we give you the congrats message in the top instructions and enable the "finish" button:

finish

You can then move on either by continuing to iterate and eventually perfecting the level, or simply by hitting the "finish" button at any time:

final

@Hamms Hamms merged commit f4bc6a9 into staging Sep 7, 2017
Hamms added a commit that referenced this pull request Sep 14, 2017
Previously, Maze levels were assuming that any kind of non-optimal
result implied a non-passing result; this is because we were formerly
not using the `APP_SPECIFIC_ACCEPTABLE_FAIL` result for any Maze levels.

I thought I had caught all the places where Maze was making this
assumption in #17428,
but it turns out I was missing one in the milestone report, the results
of which are used by the "continue" button in the success dialog to
determine whether or not clicking it will advance us on to the next
level.
@Hamms Hamms deleted the collector-finish-button branch November 3, 2017 23:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants