gmishkin / jeopardy Goto Github PK

The new week command should check the stitch value not the previous week's host (i.e. it can't use the same assertion regular handlers use).

Also any assertion that's async needs to be awaited before creating the new game.

This may be needed to determine the winner

Run command after the winner has been determined (or to determine a winner if someone is not responding) by the time the next game starts the following week.

In addition to marking people who haven't responded to the final as incorrect, record the actual effective wager of the always all-in people on the scorecard for charting purposes of historical data.

@joannac- would this cover what you were asking for the other day?

I'm not sure what's going on, but I'm not able to submit a wager this week.

If it's helpful, this week I played:
200: no response
600: no response
1000: correct
400: correct
1200: correct
2000: pass

So I have 2600 points.

However, trying both /jeopardy wager 2600 and \jeopardy wager 2599 gives me an "illegal wager" response.

Or bot access token needs permission to read DMs which presumably would not be granted.

For now only pre-existing collaborators on the Slack app will have user access tokens. Once the app is correctly re-installed in the workspace, it may not be necessary for hosts to also be collaborators.

Then the host would need to be a collaborator on the Realm app in order to update the secret.

Peter this week

It’d need to prevent them from changing their wager even if it’s not locked for everyone.

The host will have to have a command to store the clue in the games collection or something.

Need to handle ties

For the always all in people set it to their subtotal. For all others set it to zero. This will save a $lookup later and let people change their always all in setting (for future weeks) even after wagers are locked.

Right now if someone tries to wager, for example 'all', that value will be blindly stored, leading to a NaN score. Instead, an error message should be displayed to the user, and the input should be ignored.