Emojis in async results threads; allow setting packet name for bulk playtesting; bulk playtesting reacts per-packet indexing; auto-add users to thread based on category roles; fix various other issues

[ani-per]

See the updated README for more clarifications about each of these new features.

React emojis

See the new reacts zip file.

Configuration

The configuration process is now proofed against channels being duplicated for asynchronous and bulk playtesting (i.e. no async channels can be bulk or echo channels, and vice versa).

Auto-adding category roles

Users are now auto-added to all bot-created threads based on their category roles (RMPSS, Literature, etc.).

Powermarking

Powermarked questions are now properly parsed and players are given 15 points for buzzing in at any clue phrase before the powermark is read.

Asynchronous playtesting

Question

Discussion Thread Button

There's now a "Create Discussion Thread" button that allows anyone to trigger the creation a thread if !t wasn't used in the question to auto-create the thread.

Results

Tossups

Bonuses

For pseudo-tabular display, the emojis are now placed first, followed immediately by the score and user.

Bulk playtesting

Packet name

Users can now set the packet name for bulk playtesting. See the updated README for more details.

Reacts

Indexing (echoing)

React tallying

Using the !tally A or !count A command will automatically tally the reacts for all questions in packet A and publish the tallies to the corresponding index entry in the echo channel. Using the !end command will automatically tally the reacts for all questions in whatever packet was being read until that point.

Issues Fixed

• Parse category of question and automatically tag corresponding category role once playtesting button is instantiated #3
  • Auto-adding per category role implemented, as described above
• Avg buzzpoint should include percentage and/or display total # of words #6
  • Average buzzpoint stats now reported as percentage and word count
• Allow !t/!thread in separate message to create thread for the most recent question #18
  • "Create Discussion Thread" button, as described above
• Go back to previous clue/bonus part (p) #19
  • Can now use u to go back to the previous clue on tossups and back to the previous part on bonuses (except for after directing final bonus part)
• If bonus difficulty tag markers cannot be parsed, give First/Second/Third part % instead of no stats #20
  • If bot fails to parse difficulty tag, falls back to EMH order and reports stats instead of reporting no stats at all
• Ending question early does not report "thinking of" data entered #22
  • Ending question now reports notes
• README instructions for !config are incorrect in terms of spacing #29
  • Configuration instructions clarify spacing requirements and are generally more user-friendly

[ani-per]

Updated main post to reflect fixing of #18.