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

Challenge restart timing inconsistency #329

Open
ChallengeSY opened this issue Feb 25, 2023 · 6 comments
Open

Challenge restart timing inconsistency #329

ChallengeSY opened this issue Feb 25, 2023 · 6 comments
Labels

Comments

@ChallengeSY
Copy link
Contributor

An inconsistency was discovered with respect to Challenge mode runs.

Time outs and fall outs do correctly count against the set time, but restarts of successful attempts do not; making them possible to abuse, especially on easier sets.

@parasti
Copy link
Member

parasti commented Feb 25, 2023

This is by design. If Neverforum was still around, I could probably find the link where this was discussed. I don't really understand what you mean by abuse. You can improve your whole-set run, but that's not really abuse IMO.

@ChallengeSY
Copy link
Contributor Author

ChallengeSY commented Feb 27, 2023

You can improve your whole-set run, but that's not really abuse IMO.

That is true, but improving a set run as a whole means starting fresh from the beginning.

Rather, it is restarting a single level to improve its time which "incorrectly" reduces the time of the whole set. For example, if I finish a "Level 10" with 0'15''99, but then improve it to 0'14''49 in the same run, the final set time factors in only the 0'14''49.

(Given that the Web Archive only seems to support the latest 4 pages worth of posts per forum, I have a feeling this piece has been lost to time.)

@parasti
Copy link
Member

parasti commented Feb 27, 2023

Yes, what you're describing is the intended behavior. Only the last playthrough of the level is included in the set time.

If you don't want that, you can set a personal, arbitrary rule of never restarting previous levels.

Maybe I'm missing something but I believe this is working as intended.

@ChallengeSY
Copy link
Contributor Author

ChallengeSY commented Mar 1, 2023

There was a discussion in the updated Nevercord's neverball-talk on Feb 25; resulted in a Medium speedrun being rejected because it included a "voluntary restart". Existing users can instantly jump to this link.

Ideally, such a run should one-shot each of the regular levels anyway; the rejected run had 4 fall outs throughout the set anyway.

@parasti
Copy link
Member

parasti commented Mar 1, 2023

Well, if a speedrun competition sets a rule that you can't restart completed levels, that warrants a disqualification.

On the other hand, restarting the level and getting a better result (without a fall-out or time-out in between) seems like a worthy achievement to me.

Do you get infinite restarts even if you fall out after the first restart?

@ChallengeSY
Copy link
Contributor Author

Do you get infinite restarts even if you fall out after the first restart?

Nope, regardless of the outcome of the first try, a fall out (or a time out) on any subsequent attempt will still deduct a ball from the available stock. This makes the harder sets, well, harder to "abuse".

Anyhow, as far as this issue is concerned, I can't think of anything else. I might play around with the code sometime; just not at present.

@Neverball Neverball deleted a comment from ersohnstyne Mar 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants