Edit history

Earlier versions of Gateway does not accept the "Bot" prefix, newest first.

Current version | Edited by Rex
Changes
2. Get an authentication failureRemoved: ### Environment (optional)Removed: Removed: _No response_Removed: Removed: ### Logs or screenshots (optional)Removed: Removed: _No response_Removed: Removed: ### ChecksRemoved: Removed: - ☑ I searched for existing issues and didn't find a duplicate.Removed:
Show

Gateway does not accept the "Bot" prefix

Summary

A lot of Discord bot libraries expect bot tokens to be prefixed with "Bot " and will yield a validation error client-side if you do not prefix your tokens with "Bot". While Fluxer doesn't aim to be 1:1 compatible with Discord's API, supporting both would at least make it somewhat easier to port existing bots from libraries that do validation. (see: oceanic.js)

Steps to reproduce

  1. Attempt to authenticate with "Bot <TOKEN>"
  2. Get an authentication failure
Original by Rex
Show

Gateway does not accept the "Bot" prefix

Summary

A lot of Discord bot libraries expect bot tokens to be prefixed with "Bot " and will yield a validation error client-side if you do not prefix your tokens with "Bot". While Fluxer doesn't aim to be 1:1 compatible with Discord's API, supporting both would at least make it somewhat easier to port existing bots from libraries that do validation. (see: oceanic.js)

Steps to reproduce

  1. Attempt to authenticate with "Bot <TOKEN>"
  2. Get an authentication failure

Environment (optional)

No response

Logs or screenshots (optional)

No response

Checks

  • ☑ I searched for existing issues and didn't find a duplicate.