Troubleshooting Guide¶
Having issues with Spruce Bot? This comprehensive troubleshooting guide covers the most common problems and their solutions.
Quick Diagnostics¶
Start with these basic checks:
Quick Fixes¶
- Check bot status - Is Spruce online? (Green indicator)
- Verify permissions - Does bot have required permissions?
- Test basic command - Try
&pingto confirm functionality - Check role hierarchy - Is bot role positioned correctly?
Common Issues¶
Bot Not Responding¶
Symptoms: Commands don't work, no response from bot
- Bot shows online (green status)
- Bot has "Send Messages" permission
- Channel isn't muted for bot
- Try slash commands:
/help
- Use
&syncto refresh slash commands - Check if bot is rate limited
- Verify bot isn't banned/restricted
- Restart Discord client
If still not working: Join support server for assistance.
Permission Errors¶
Error Messages: - "Missing permissions" - "I don't have permission" - "Role is higher than mine"
Problem: "Role is higher than mine"
Solution: 1. Go to Server Settings → Roles 2. Drag bot's role above target role 3. Save changes 4. Try command again
Problem: Bot lacks specific permissions
Check Required Permissions:
| Feature | Required Permission |
|---|---|
| AutoRole | Manage Roles |
| Moderation | Manage Messages, Kick/Ban Members |
| Channels | Manage Channels |
| Tournaments | Manage Channels, Manage Roles |
Problem: Bot can't access specific channels
Solution: 1. Right-click channel → Edit Channel 2. Go to Permissions tab 3. Add bot role with required permissions 4. Save changes
Slash Commands Issues¶
Symptoms: Slash commands don't appear in autocomplete
AutoRole Not Working¶
Problem: New members not receiving roles automatically
- Bot has "Manage Roles" permission
- Bot role is above target roles
- Target roles exist and aren't deleted
- Roles aren't managed by other bots
- Have a friend leave and rejoin
- Create a test alt account
- Monitor role assignment
- Check for error messages in logs
Command Errors¶
Error: "Rate limited" or "Try again later"
Solutions: - Wait specified time period - Reduce bulk operations - Avoid rapid command usage - Use smaller batches for bulk actions
Error: "Invalid role/user/channel"
Common Causes: - Typos in mentions - Deleted roles/users/channels - Incorrect ID format - Missing @ symbol for mentions
Error: Command takes too long
Solutions: - Break large operations into smaller chunks - Wait for current operation to complete - Check server boost level (affects limits) - Report persistent timeouts
Feature-Specific Issues¶
Tournament Problems¶
Problem: Tournament setup command fails
Checklist: - [ ] Have @tourney-mod role or Manage Channels - [ ] Server has enough channel slots - [ ] Bot has Manage Channels permission - [ ] Tournament name is appropriate length
Problem: Users can't register for tournaments
Solutions: - Check if registration is open (/tourney info) - Verify proper team format - Ensure registration channel permissions - Check if fake tag detection is enabled
Scrim Issues¶
Problem: Wrong registration times
Solution:
Common Timezones: - Asia/Kolkata (IST) - America/New_York (EST) - Europe/London (GMT)
Performance Issues¶
Slow Response Times¶
Causes and Solutions:
Symptoms: All commands slow
Solutions: - Check server boost level - Reduce concurrent operations - Monitor during peak hours - Consider premium features
Symptoms: Intermittent slowness
Check: - Your internet connection - Discord server status - Bot hosting status
Memory/Resource Issues¶
Symptoms: Bot becomes unresponsive or crashes
Solutions: - Report to support server - Provide server size and usage details - Note what commands were being used
Error Code Reference¶
| Code | Description | Solution |
|---|---|---|
50013 | Missing Permissions | Grant required permissions |
50001 | Missing Access | Add bot to channel/server |
50035 | Invalid Form Body | Check command syntax |
50007 | Cannot send messages to user | User has DMs disabled |
10011 | Unknown Role | Role was deleted |
10003 | Unknown Channel | Channel was deleted |
10013 | Unknown User | User left server or doesn't exist |
Diagnostic Commands¶
Use these commands to gather information for support:
&botinfo # Bot statistics and status
&serverinfo # Server information
&ping # Latency and response time
&help <command> # Specific command help
Getting Help¶
Self-Service Resources¶
- Common Issues - Most frequent problems
- Permission Guide - Permission-related issues
- Performance Guide - Speed and reliability issues
Community Support¶
- Discord Support Server - Live community help
- GitHub Issues - Bug reports
- Discussions - General questions
When Reporting Issues¶
Include this information:
Report Template
**Issue Description:** Brief description of the problem
**Steps to Reproduce:**
1. Step one
2. Step two
3. Step three
**Expected Behavior:** What should happen
**Actual Behavior:** What actually happened
**Error Messages:** Exact error text (if any)
**Server Info:**
- Member count: ~X members
- Boost level: Level X
- Bot permissions: Administrator/Custom
**Additional Context:** Any other relevant information
Emergency Contact¶
For critical issues affecting many users:
- Priority Support: Available for premium users
- Email: support@nexinlabs.com
- Discord: Direct message @support in support server
Related Guides: - Permission Setup Guide - Command Reference - Feature Guides