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

reset response interval #982

Merged
merged 1 commit into from
Apr 30, 2024
Merged

Conversation

Evert-R
Copy link
Contributor

@Evert-R Evert-R commented Apr 30, 2024

reset response interval for first card, in case the card already has a value from a previous turn

@Evert-R Evert-R merged commit 09c2b6a into develop Apr 30, 2024
11 checks passed
@Evert-R Evert-R deleted the bugfix-er/mp-response-interval-first-move branch April 30, 2024 15:44
Comment on lines +119 to +121
currentCard.timestamp = performance.now();
// reset response interval in case this card has a value from a previous turn
currentCard.response_interval_ms = '';
Copy link
Contributor

@drikusroor drikusroor Apr 30, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't a null or 0 value be better though instead of an empty string since performance.now() returns a number?

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.

2 participants