Configuration Interface
Each command in the configuration panel displays:- Toggle Switch: Enable or disable the command
- Command Input: Customize the command name
- Description: Explanation of what the command does
- The toggle switch turns off
- The command input field becomes disabled
- The command will not be registered on the server
Best Practices
Command Naming
- Use clear, memorable command names
- Avoid conflicts with existing server commands
- Consider your community’s language and preferences
Security Considerations
- Disable destructive commands like
kickallunless absolutely necessary - Review permissions for each command based on staff roles
- Test commands in a development environment first
Performance Tips
- Disable unused commands to reduce server load
- Use the “Only Missing” setting to avoid command conflicts
- Regularly review and update your command configuration
Export/Import Configuration
The configuration can be exported as JSON for backup or sharing:- Backup: Save your configuration settings
- Sharing: Share configurations between servers
- Version Control: Track changes to your setup
- Migration: Move settings to new servers
Troubleshooting
Commands Not Working
- Check if “Commands Enabled” is turned on
- Verify the specific command is enabled
- Ensure no command name conflicts exist
- Review server console for error messages
Command Conflicts
- Enable “Only Missing” to skip existing commands
- Use unique command names
- Check for conflicts with other resources
Permission Issues
- Verify staff permissions in the Permissions section
- Check role assignments for command access
- Review server-side permission configurations