-
Notifications
You must be signed in to change notification settings - Fork 1
Errors
[00:00:00] One or multiple JSON files are missing, check the wiki for more info:
- You may not have
config.jsonortickets.json, if so run thesdtb-setup.exeand type Y → j - They may be in the wrong place, the
config.jsonfile should be next tobot.pyand thetickets.jsonfile should be next totickets.py
[00:00:00] Your bot token is invalid, check the wiki for more info:
- You may not have entered the bot token correctly, or it incorrectly, ensure the token is 59 characters long exactly
[00:00:00] Your bot prefix is invalid, check the wiki for more info:
- You may have set your prefix as "" or " ", make sure it's one or more characters
[00:00:00] User#0000 tried using 'command' but the command didn't exist. Maybe add it as an alias in config.json?:
- This error can be ignored if the command isn't remotely similar to
setup,openorclose - Check that every new command alias is separated by a comma (check the example config.json)
[00:00:00] User#0000 tried using 'command' but they were lacking permissions.:
- This error can be ignored if the user isn't meant to have the appropriate permissions to execute the command
- Check that the user has the correct permissions within their roles
- Check that the user has the correct roles
[00:00:00] I don't have sufficient permissions. Make sure I have administrator!:
- Check that the bot has administrator
- Check that the bot has the correct permissions within its roles
- Check that the bot has the correct roles
[00:00:00] The support role ID is invalid, try reconfiguring the ID using 'setup':
- Redo the setup command and make sure the ID is of the correct type and valid
[00:00:00] The category ID is invalid, try reconfiguring the ID using 'setup':
- Redo the setup command and make sure the ID is of the correct type and valid
[00:00:00] config.json file not found:
- This will generate a new
config.jsonfile which you should edit accordingly (check the example config.json)
[00:00:00] tickets.json file not found:
- This will generate a new
tickets.jsonfile which you should edit accordingly using+setup(+ referring to the default prefix)
[00:00:00] Your version is outdated '1.0' the newest version is '1.1':
- Update the bot by downloading the latest sdtb-setup.exe from the releases page and copying the old configuration into the new
config.jsonfile that will be generated - Please report this issue to the developers if it persists even after updating to the latest version