A Slack bot that lets you play full Jeopardy! games. Easy to deploy, and highly configurable to your team's style of play.
A docker image containing the bot is published and can easily be used as well. You will need to create a
SLACK_TOKEN for the bot, and provide it via an environment variable when running the container.
$ docker pull jeopardybot/bot $ docker run -e "SLACK_TOKEN=<slack-token-here>" -d jeopardybot/bot
You're good to go! Invite the bot into a channel on slack, and start a game by saying "new game"!
Deploying with Heroku is possible, however if you're using a free plan, the deployment will sleep after 30 minutes of inactivity, and you'll need to manually restart the deployment. For this reason, it is not our preferred hosting provider. If you'd like to deploy on Heroku, you can use the button below:
When in doubt, just type "help" in the channel and a message will appear to help you out.
*Games* “help” - Displays this helpful message. “new game” - Starts a new game. “end game” - Ends the current game. *Selecting Categories* “I’ll take ________ for $___” “Give me ________ for $___” “Choose ________ for $___” “________ for $___” “Same (category) for $___” “Gimme ________” *Guessing* “What [is|are] _______” “Who [is|are] ________” “Where [is|are] ______” “When [is|are] ______” *Wagering* “(I'll) wager $___” “$___” *Scores* “scores” - Shows the scores for the current game. “leaderboard” - Shows the scores for the top players. “loserboard” - Shows the scores for the bottom players. *Configuration* “config” - Shows the configuration for the current channel “config global” - Shows the global configuration
You can also ensure that the bot is awake by messaging "poke". This is useful for free Heroku dynos, which may get shut down after inactivity.
The slack bot is configured via slack commands. To explore the configuration options available, simply say "config".
Persistence works out of the box by periodically uploading a dump of the configuration to slack itself. The sync occurs every 5 minutes, and whenever the process is gracefully exited. If the process exits and is unable to sync, it may lose up to 5 minutes of data.