Setup Guild Management

After completing the initial setup with /setup start, you have access to additional commands for managing and maintaining your guild configuration. This guide covers the management commands that help you verify, update, and reset your bot settings.

📖 Table of Contents

• Check Configuration
• Update Settings
• Reset Configuration
• Best Practices
• Troubleshooting

🔍 Check Current Configuration

The /setup check command allows you to view your current bot configuration without making any changes.

Command Usage

/setup check

What It Shows

The command displays a comprehensive overview of your current setup:

When to Use

• Verification: Confirm your setup is correct after initial configuration
• Troubleshooting: Debug role assignment issues by checking mappings
• Auditing: Review current settings before making changes
• Documentation: Reference current configuration for team members

🔄 Update Settings

To modify your current configuration, you simply re-run the /setup start command with new parameters.

How Updates Work

• Non-Destructive: Existing data is preserved, only configuration changes
• Selective Updates: You can change individual role mappings without affecting others
• Immediate Effect: Changes take effect immediately for new registrations
• Member Data Preserved: Existing member registrations remain intact

Common Update Scenarios

Changing Role Mappings

If you rename Discord roles or want to map different roles:

/setup start
server: Europe
target-name: MyGuildName
type: Guild
member-role: @New-Members-Role
management-role: @Guild Officers
booster-role: @Server Boosters
log-channel: #bot-logs
[... continue with all role mappings using new roles ...]

Updating Log Channel

Change where the bot sends log messages:

/setup start
[... same parameters as before ...]
log-channel: #new-log-channel
[... continue with all other parameters ...]

Switching Guild or Server

Change the target guild or Albion server:

/setup start
server: Americas  
target-name: DifferentGuild  
type: Guild
[... continue with all other parameters ...]

🔄 Reset Configuration

The /setup reset command completely removes your guild configuration, returning the bot to an unconfigured state.

Command Usage

/setup reset

What Reset Does

• Removes Guild Config: Deletes all configuration from the database
• Clears Role Mappings: All role assignments are removed
• Disables Dashboard: Web dashboard access is deactivated
• Stops Role Assignment: New registrations won't assign Discord roles
• Preserves Member Data: Existing member registrations are NOT deleted

When to Use Reset

• Major Restructuring: Complete role system overhaul
• Server Migration: Moving to a different Discord server
• Testing: Clean slate for testing new configurations
• Troubleshooting: Last resort for configuration issues

Reset Recovery Process

After running /setup reset:

1. Immediate: All bot features become unavailable
2. Dashboard: Web interface shows "Setup Required" message
3. Commands: Registration and management commands will fail
4. Recovery: Run /setup start with complete configuration
5. Verification: Use /setup check to confirm new settings

💡 Best Practices

Configuration Management

• Document Changes: Keep a record of role mappings and configuration changes
• Test Updates: Use /setup check before and after changes
• Communicate Changes: Inform team members about role mapping updates
• Backup Strategy: Note current configuration before major changes

Role Management

• Consistent Naming: Use clear, descriptive role names
• Role Hierarchy: Ensure bot role is above managed roles
• Permission Check: Verify bot has "Manage Roles" permission
• Member Impact: Consider how changes affect existing members

Maintenance Schedule

• Monthly Check: Run /setup check to verify configuration
• Role Audit: Ensure all mapped Discord roles still exist
• Permission Review: Confirm bot permissions are intact
• Update Planning: Schedule configuration changes during low activity

🔧 Troubleshooting

Common Issues

Setup Check Shows Wrong Information

Symptoms: Configuration display doesn't match expected settings

Solutions:

• Run /setup start again with correct parameters
• Verify all Discord roles still exist
• Check for role name changes in Discord
• Ensure bot has proper permissions

Cannot Update Configuration

Symptoms: Setup command fails when trying to update

Solutions:

• Verify you have Administrator permissions
• Ensure all required parameters are provided
• Check that new role mappings are valid Discord roles
• Try /setup reset then /setup start if persistent

Reset Command Not Working

Symptoms: Reset command fails or doesn't complete

Solutions:

• Confirm Administrator permissions
• Check database connectivity
• Retry the command
• Contact support if database issues persist

Roles Not Updating After Configuration Change

Symptoms: Member role assignments don't reflect new configuration

Solutions:

• New registrations will use updated settings immediately
• Existing members keep their current roles until re-registration
• Use /remove and /register to update individual members
• Consider announcing configuration changes to guild members

Emergency Procedures

Complete System Failure

If the bot becomes completely non-functional:

1. Run /setup check to diagnose configuration issues
2. Use /setup reset to clear corrupted configuration
3. Run /setup start with known good configuration
4. Verify functionality with /setup check
5. Test member registration to confirm operation

Role System Corruption

If role assignments stop working properly:

1. Check Discord role hierarchy and permissions
2. Verify bot role position above managed roles
3. Run /setup check to review role mappings
4. Update configuration with /setup start using correct roles
5. Test with a new member registration