1 • Make links to puzzle and channel within sheet be actual links
3 • Make /solved report to the main hunt channel
5 • Make /solved rename the puzzle's sheet to indicate its solved status
7 • Make /solved rename the puzzle's channel to include a "-solved" suffix
9 • Make /solved clear the state string for a puzzle.
11 • Implement an /archive command to allow for easy archiving of a
12 channel for a solved puzzle
14 • Implement code to close out an entire hunt after the face
16 • Implement a /hunt command for giving an overview of the entire hunt,
17 (like the Turbot "home" view but available in any channel)
19 • For "/hunt" display only unsolved puzzles by default, but also allow
20 for "/hunt all" to display all puzzles
22 • On the Turbot home screen allow a dropdown for Unsolved/Solved/All
25 • For both "/hunt" and the Turbot home screen allow for a search
26 string that will search through puzzle names, puzzle IDs, puzzle
27 URLs, and state strings.
29 • Add an (optional) drop-down at puzzle creation for selecting a known
30 round for a puzzle, (or creating a new round). Ensure this mechanism
31 allows for puzzles to exist in multiple rounds.
33 • Consider putting a round prefix into the channel name to group a
34 round's puzzles in the channel list.
36 • Figure out a good mechanism for linking puzzles to a meta-puzzle
37 that they feed into. Is this different or the same than the round
38 mechanism described above?
40 • Implement a command to display the status of the current puzzle
41 within the channel. Need a name for this command.
43 • Extend the in-channel puzzle display to also allow editing of all
46 • Fix /puzzle dialog to reject a puzzle with the same URL as an
49 • Allow a per-user option to opt out of being auto-invited to all
50 newly-created puzzle channels.
52 • Figure out what we want for tagging and searching on tags (beyond
53 what's already possible with the state strings).
55 • Decide a good plan for audio/video calls for puzzles and integrate
58 • Inspect the CloudWatch logs for our Turbot AW Lambda during the time
59 period of the active hunt, (October 24-31), find and diagnose any
60 errors that occurred during that period. Users reported seeing
61 "Trouble connecting" (probably during new-puzzle dialog submission)
62 as well as "dispatch_failed during /state command (perhaps due to a
63 state string that was very long).
65 • Incorporate puzzle file uploads into the database state for each
66 puzzle. Any file uploaded to the Slack should get included
67 initially, but when editing a puzzle users can drop irrelevant files
68 or label relevant files.
70 • Figure out what tool we want to use for shared drawing on a puzzle
71 and integrate that into Turbot, (give a command that will generate a
72 new URL and will insert that URL into the Slack topic and the list
73 of links at the top of the sheet).
75 • Come up with a better sheet template
77 • Put the puzzle's name into the primary tab of the sheet
79 • When copying tabs from the spreadsheet template, don't leave the
80 default "Copy of " text in place.
82 • Do something to make it more clear which tabs exist just as
83 backup/reference from the original template vs. any new tab a user
84 has created during the hunt. (Perhaps color the reference tabs
87 • Think about some way to express solve priority