Skip to content

Latest commit

 

History

History
84 lines (68 loc) · 4.04 KB

TODO.md

File metadata and controls

84 lines (68 loc) · 4.04 KB
Raw

Necrobot TODO

Current version: 0.13

Current TODO

General

  • Make .caw next do something reasonable
  • Add useful role functionality, maybe w/reaction roles, for challenge roles
  • Add functionality for automatic role assignment (for, e.g., league roles)
  • Delete or erase unmade matches file when it is used
  • Better code for managing non-unique username issues
  • Replace NoneType returns with exceptions where appropriate
  • More efficient database requests (especially on Condorbot startup)
  • Do assignment into leagues via role assignment
  • Link cawmentator on matches that are past their alert notice when the command is fired
  • Convenience commands giving one's schedule and maybe link to all one's race rooms? Callable in PM only ofc
  • Immediate race alerts for races that are scheduled for within the next 5 minutes
  • A way to view your most recent results in a big list? Talk to elad/cancel
  • A way to get links to all your matchrooms? Probably only useful for admin
  • A refresh cache command so that manual DB updates can be made without reboots
  • Don't weirdly overwrite config file on shutdown
  • Deal with 504 errors on matchmaking

Grudgedor stuff

  • A way to mark matches with names/custom tags so people in .next can see what's up
  • A way to allow racers to set rules
  • Matches with more than two people (big!)

GSheet

  • Drastically simplify GSheet interaction (full overwrite updates, no reading from sheet)

Match

  • Make bot say races awaiting review in match score announcement when contested races
  • Remove or notify commentator on match reschedule
  • Combine MatchRaceData and Match in a friendly way
  • Better failure messages for cawmentate command when more than one match is identified
  • Allow cawmentators to react inside the race room

Util

  • util.level.py and util.racetime.py might work better as classes, when wanting to generalize to other games

Parsing

  • Allow specifying a match ID in .vod and .cawmentate, and make match IDs easier to see publically
  • More consistent/flexible command-line syntax
  • Better public-facing command-line documentation (i.e. .help command)
  • Deal with duplicated Discord names in commands like .add (allow for discriminator)
  • More friendly parsing of spaces in command arguments
  • Parse the word 'noon' as a time

Testing

  • Make more small/unit tests (may wish to use a mock DB and/or a mock discord client)

Bugs

  • .d 2-3 responds with ' has forfeit the race' twice
  • .register-condor-event should do more to set up convenient views in database
  • Necrobot and Condorbot should not attempt to write to the same log file
  • Fix identical times causing a racer to be listed twice on .fastest
  • Get rid of .dailyalert command

Unclear issues

  • .forcecancel doesn't seem to work as intended; racerooms can get stuck
  • Various issues with raceroom topic not updating properly (e.g. on .r without .e)
  • .forcecancel is kind of unintuitive when input pre-race, since it's not clear if you want to cancel the race just finished or the race that people are currently entering. It maybe also doesn't work after a race?

Possible features (no concrete plans to implement these)

  • Raceroom-specific voice chat, with an audio countdown and some other audio support (e.g. "Please pause.").
  • Configuration of .racealert for character-specific, etc

Different race modes

  • Score
  • Time limits, with an auto-ping when the time expires

Stream support / Twitch integration

  • Allow for users to tag certain races as "streamed". For such races, generate a multitwitch or kadgar link upon asking. As an even bigger project, make the bot able to check whether said users are actually streaming. Also, make the bot able to report in your twitch chat when people in your race have finished or forfeit (and who won, etc.)

Daily improvements

  • A weekly that's intended for optimizing a seed.
  • Make the daily more like an asynchronous race: You're allowed to die, and the bot tracks your time between a .begin and .done sent via PM. (This could be made alongside an "individual run module" for practicing?)