#3 Auto Thread Creation/Deletion Based on Schedules

[Plazmafield]

# Auto Thread Creation/Deletion Based on Schedules
-General Scope:
Tournament can control and modify defaults and permissions to edit in a flexible way
Players can override tournament defaults to be pinged. But a failed ping/DM results in alternative action
Auto thread creation based on each tournament/group, etc. Auto thread deletion (or hiding if log should somehow be maintained)
Auto reminder pings and verification; auto waitlist ping and DMs
Auto setup defaults based on tournament settings history extracted from documentation. E.g. 15 minutes, 5 minutes, etc.
Auto posts to provide introductory statement with statement of game time:
UTC: ...
Your Time Zone: Unix time extracted from players registered for group

• Should Allow for a default introductory Statement. Automatically switch out the round reference by increment and by checking time for validation (with X variance). Auto Pings players at thread creation, 24 hour mark, 1 hour before game time as reminders. Reminder ping defaults can be modified such that only certain ping reminders are on by default.
  Consider including a default 10 minute before game post w/ ping to players in group thread requesting verification of playing. Anyone who doesn't react to the check-mark by (default) 5 min before game time result in a DM to the player if settings is not turned off by the player. /myDMs <on off=""> <type1: optional="" didn't="" verify="" presence="" to="" play=""> <type2: optional="" waiting="" list="" dm=""> <type3: optional="" ...="" any="" others="" we="" think="" of="">.
  Tournament can control how they want these settings for players by default. At 5 minutes, if someone doesn't react to check_mark or reacts to X, the bot by default executes a waitinglist ping (and or set of DMs within bounds of Discord terms of service), if waiting list length > 0. The waiting list role name is provided by the tournament as a loaded default role. </type3:></type2:></type1:></on>

/set_defaults <some way of providing intra server options for setting separate tournament events... perhaps with<min role="" for="" editing:="" optional=""> <vector of discord ID codes with editing permissions</min>

tired of typing every bit of this. But we can figure out some details. Functions off of Discord ID not @ name.