-
Notifications
You must be signed in to change notification settings - Fork 6
Troubleshooting
This page shows some well known problems and their solutions, workaround or explanations.
A common reason is, that your Caps Lock key is activated. Sadly gord can't differentiate between Shift an Caps Lock, so make sure you aren't activating it by accident.
Another common reason is, that your terminal emulator is capturing specific key combinations instead of forwarding those to gord. On top of that, some systems have some shortcuts pre-defined, therefore gord can't use them. Since I am working on Linux, it might happen that I chose defaults that don't work for you.
This can be solved by doing one of the following:
- Changing the shortcuts in gord
- Reconfiguring your terminal emulator to not register the shortcuts that you need for gord
- Getting a different terminal emulator
If you want to log in as a bot, you need to provide the characters Bot infront of your token, since this is a Discord API requirement and there is no way to differentiate between a normal token and a bot token.
It can happen that Discord invalidates your token. There are certain events that always trigger invalidation. Such as changing your password or activating / deactivating two-factor-authentication on your account. You can work around this by doing such actions via gord instead of the official client. Changing your e-mail address might also invalidate your token.
Sadly, emojis aren't support by all terminals. On Windows you'll generally not be able to see emojis and even have some rendering issues, since it doesn't support UTF-8. There's really not much you can do about it. Microsoft is currently working on a new terminal over at https://github.com/Microsoft/Terminal. Maybe this is gonna help you when it's done.
For the Linux and MacOS users, I can only recommend to try out which terminal works best for you.
See https://github.com/cainy-a/gord/wiki/What-Terminal-should-you-use%3F