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