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

Improve buzzer: fair tiebreaks and quantization #62

Merged
merged 1 commit into from
Jul 8, 2024

Conversation

neilmovva
Copy link
Collaborator

Buzzer ties are now broken randomly, independently for each clue.
Buzzer times are rounded to the nearest 100ms to slightly deweight buzzer racing as a game mechanic.

Copy link

vercel bot commented Feb 17, 2024

Someone is attempting to deploy a commit to a Personal Account owned by @cmnord on Vercel.

@cmnord first needs to authorize it.

Copy link

vercel bot commented Feb 17, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
jep ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 8, 2024 2:30am

app/engine/engine.ts Outdated Show resolved Hide resolved
app/engine/engine.ts Outdated Show resolved Hide resolved
app/engine/engine.ts Outdated Show resolved Hide resolved
@menonsamir
Copy link
Collaborator

One (possibly sad) consequence of this PR - almost every prior game will become impossible to review, since the tiebreak rules will resolve ties differently, so the state will get 'stuck' at the first tie that resolves differently.

The main mitigation I can think of would be versioning the game engine, add a column to 'rooms' that holds the engine version at time of creation, and then applying these new tiebreak rules only for the new engine version. It's sadly a bit complicated, though.

Buzzer ties are now broken randomly, independently for each clue. Buzzer times
are rounded to the nearest 200ms to slightly deweight buzzer racing as a game
mechanic. Lockouts should still carry a penalty, otherwise buzz-spamming
becomes optional.
@cmnord cmnord merged commit 155476c into cmnord:main Jul 8, 2024
3 of 4 checks passed
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