-• Make links to puzzle and channel within sheet be actual links
-
-• Make /solved report to the main hunt channel
-
-• Make /solved rename the puzzle's sheet to indicate its solved status
-
• Make /solved clear the state string for a puzzle.
• Implement an /archive command to allow for easy archiving of a
channel for a solved puzzle
-• Implement code to close out an entire hunt after the face
+• Implement code to close out an entire hunt after the fact
• Implement a /hunt command for giving an overview of the entire hunt,
(like the Turbot "home" view but available in any channel)
string that will search through puzzle names, puzzle IDs, puzzle
URLs, and state strings.
+• Add an (optional) drop-down at puzzle creation for selecting a known
+ round for a puzzle, (or creating a new round). Ensure this mechanism
+ allows for puzzles to exist in multiple rounds.
+
+• Consider putting a round prefix into the channel name to group a
+ round's puzzles in the channel list.
+
• Figure out a good mechanism for linking puzzles to a meta-puzzle
- that they feed into.
+ that they feed into. Is this different or the same than the round
+ mechanism described above?
• Implement a command to display the status of the current puzzle
within the channel. Need a name for this command.
• Decide a good plan for audio/video calls for puzzles and integrate
that into Turbot.
-• Inspect the CloudWatch logs for our Turbot AW Lambda during the time
+• Inspect the CloudWatch logs for our Turbot AWS Lambda during the time
period of the active hunt, (October 24-31), find and diagnose any
errors that occurred during that period. Users reported seeing
"Trouble connecting" (probably during new-puzzle dialog submission)
• Come up with a better sheet template
+• Put the puzzle's name into the primary tab of the sheet
+
• When copying tabs from the spreadsheet template, don't leave the
default "Copy of " text in place.
has created during the hunt. (Perhaps color the reference tabs
differently.)
+• Think about some way to express solve priority