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