Skip to content

Updating channel region kills VNext #981

@VelvetToroyashi

Description

@VelvetToroyashi

Discord "recently" shifted from guild region to per-channel regions, however updating this does not send requisite data that VNext expects to successfully reconnect to the session, which causes a null-ref to propagate up the call stack and through the AsyncEvent that fires when this happens. I don't know enough about VNext to handle this myself, though, hence the issue vs a PR.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Effort

    None yet

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions