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

tones swapped scores: Fix ordering of scores for hotwheels.map. #371

Merged
merged 1 commit into from
Aug 5, 2024

Conversation

bairyn
Copy link
Member

@bairyn bairyn commented Jul 20, 2024

While attempting an all-hard challenge, I noticed that in the Tones level set, 2 levels seem to have 2 high scores that are swapped, rather than what seems to have been intended or better design. Normally the fast unlock hard has more time than the best times hard, although technically this doesn't need to be the case. In 2 levels, it seems they may have accidentally been swapped.

I didn't create this level set, but I think this would be a reasonable maintenance.

The first of two PRs addresses the easier of the two level changes: level 15 (hotwheels.map) has both its fast unlock values less than either best times value. Presumably these were meant to be swapped.

The second PR flips swaps just the hard value for best times and fast unlock, since the medium value is ordered as expected. It applies to level 11 (leaps.map). (I still managed to beat all hards on this level as it currently stands, but it seemed uncharacteristically difficult for this level set.) This PR only swaps hard, not both hard and medium like the first.

In case the original author wanted to provide input or do something other than swap, as he adjusted scores once before in 2014 (3fa0b2c), I'm pinging @tonesfrommars.

@MightyBurger also mentioned he might want to add a texture fix in this level set to go along with these changes.

The hard and medium scores for fast unlock both gave less time than those for
best times.
@parasti parasti merged commit 60cd9d7 into Neverball:master Aug 5, 2024
@tonesfrommars
Copy link
Contributor

Thank you @bairyn and @parasti, I approve whole heartedly.

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

Successfully merging this pull request may close these issues.

3 participants