sapphire-arches / abyss-inhouse Goto Github PK

Allow manual association of twitch username so we're not relying on the sketchy discord sync.

Right now this works if you /join_abyss again, but it presents a nonsense message ("you're already in the queue"). It should either say you joined, or specifically call out that you've moved from skrub to non-skrub status.

The bot should have a concept of a "game", where you can add people to the game (adding someone to a game should pop them from the queue).

__main__.py is getting busy.

Depends on #3 and #4.

The system needs a new component, (bikeshed name: dota2-game-mgr) , which:

• listens for requests from the bot
• creates dota2 lobbies with random password, kicking password back to a bot-admin channel?
• automatically adds all the players in the bot's game to the lobby.

To support automatic lobby management, the bot should request/require steamIDs from players.

Requires adding a new nullable column to the users table, BigInt steam_id.

People can queue but then realize they can't play, they should be allowed to remove themselves

Syntax:

/leave_abyss

Allow people to queue, but state that they won't be ready for the current game.

Some implementation options:

• tweak the queue time
• make the queue / bot aware of games
• add a "ready check" we can use pre end of the last game, and don't set it by default for entries past 10/ on player control.

This can help prioritize so we don't automatically let subs requeue ahead of nonsubs.

Depends on #5 .

The discord bot should query the game management service (or pick up events from a messagequeue bus?) and assign people to ephemeral channels+roles.

Unit tests would be nice.

/list_abyss should present an action row that allows paging through users, probably limiting to ~15 at a time so we don't have to deal with dynamic sizing of the iterator?

Alternatively, we could implement something like twitter's cursor system where cursors are actually persisted to the database but that sounds complicated.