Skip to content

Direct mode breaks when invalid client id is registered #3

@SapuSeven

Description

@SapuSeven

After switching to direct mode, if a direct client with a non-existing id is added (for example: !directs add 12345, the bot stops sending messages due to an exception when trying to message this non-existing client.
This can also happen if a direct user disconnects.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions