Skip to main content
Maximize Fire’s capabilities with proven strategies for efficient server management, member safety, and community growth.

​
Initial Server Setup

​
Role Hierarchy Planning

Proper role structure is critical for Fire’s functionality:
1

Position Fire's role

Place Fire’s role above all roles it needs to manage:
  • Above moderation roles
  • Above auto-assigned roles
  • Above reaction roles
  • Below admin/owner roles only
2

Create role categories

Organize roles into logical groups:
  • Staff: Admin, Moderator, Helper
  • Automated: Muted, Verified, Rules Accepted
  • Self-Assign: Pronoun, Game, Region roles
  • Special: Nitro Booster, VIP, Partner
3

Set role colors strategically

  • Staff roles: Distinctive colors (red, blue, gold)
  • Auto-roles: Neutral/no color
  • Self-assign ranks: Member-chosen colors
Common Hierarchy Mistakes:
  • Fire’s role below managed roles → Commands fail
  • Moderator role above Fire → Cannot manage moderators
  • Multiple “Muted” roles → Confusion and gaps in coverage

​
Permission Configuration

Fire needs these in every server:
  • View Channels
  • Send Messages
  • Embed Links
  • Attach Files
  • Read Message History
  • Add Reactions
  • Use External Emojis
Quick Permission Check:
/botpermissions
# Shows Fire's permissions and identifies missing ones

​
Moderation Strategy

​
Auto-Moderation Configuration

Balance automation with human judgment:
Recommended Settings:
  • Message spam: 5 messages in 5 seconds
  • Mention spam: 5 mentions per message
  • Emoji spam: 10 emojis per message
  • Enable duplicate message detection
Action: Timeout for 5-10 minutes on first offense
Smart Filtering:
  • Focus on clear-cut violations only
  • Avoid over-filtering (creates evasion attempts)
  • Use wildcard sparingly
  • Regularly review false positives
Action: Delete + warning (not instant ban)
First 10 minutes:
  • Restrict to welcome/rules channels
  • No link posting
  • Slowmode in accessible channels
  • Auto-role after verification
Prevents: Raid accounts, spam bots

​
Logging Best Practices

Create a comprehensive audit trail: 
# Essential log channels
/config set modlog.moderation #mod-logs
/config set modlog.action #action-logs
/config set modlog.members #member-logs
/config set modlog.messages #message-logs
Channel Organization:
  1. #mod-logs: Moderation actions (bans, kicks, timeouts, warnings)
  2. #action-logs: Configuration changes, role updates
  3. #member-logs: Joins, leaves, nickname changes
  4. #message-logs: Deleted/edited messages
Permissions: Restrict to moderators only, prevent deletion

​
Moderation Workflow

1

Respond to Reports

Use tickets or a dedicated report channel:
/config set moderation.report-channel #reports
Review reports daily, respond within 24 hours.
2

Document Actions

Always include reasons in moderation commands:
/warn @user Advertising in #general
/timeout @user 1h Spam after warning
/ban @user Continued rule violations (3rd warning)
3

Review Regularly

Weekly moderation team meeting:
  • Review recent cases
  • Discuss edge cases
  • Update guidelines
  • Check for pattern violations
4

Track Repeat Offenders

Use Fire’s case system:
/case @user
# Shows complete moderation history
Escalate actions for repeat offenders.

​
Member Engagement

​
Role-Based Organization

Self-Assignable Ranks (Premium feature):

Pronoun Roles

  • he/him, she/her, they/them
  • Display with color for visibility
  • Update pronouns regularly

Interest Roles

  • Game titles
  • Hobbies
  • Content preferences
  • Trigger notifications for relevant announcements

Region/Timezone Roles

  • Geographic regions
  • Timezone groups
  • Language preferences
  • Coordinate events effectively

Notification Roles

  • Event announcements
  • Content updates
  • Ping opt-in
  • Member-controlled communication
# Configure self-assignable ranks
/config set utils.ranks
# Select all roles members can self-assign

# Members then use:
/rank
# Interactive button/dropdown interface appears

​
Welcome Experience

/config set greet.message #welcome
Message Template:
Welcome {mention}! 👋

📜 Read the rules in {#rules}
🎫 Get roles in {#roles}
💬 Introduce yourself in {#introductions}

You're member #{membercount}!

​
Community Building

High-Engagement Features:
  1. Starboard - Highlight best messages 
    /config set starboard.channel #starboard
/config set starboard.stars 3
  2. Custom Tags - Create inside jokes, memes, useful references
    • Keep updated and relevant
    • Remove outdated tags
    • Enable slash commands for discoverability
  3. Voice Channel Roles - Show who’s active 
    /vcrole #general-vc @In Voice
  4. Invite Tracking - Recognize recruiters 
    /inviterole <invite> @Recruiter

​
Performance Optimization

​
Reduce Bot Clutter

1

Use ephemeral responses

Enable ephemeral mode for tags:
/tag slash ephemeral
Responses only visible to command user.
2

Delete trigger messages

Use dtag for clean responses:
!dtag rules
# Command message auto-deleted
3

Dedicated bot channel

Create #bot-commands for:
  • Command testing
  • Member experiments
  • Non-critical commands

​
Channel Organization

Recommended Structure: 
📋 INFORMATION
  ├─ #rules
  ├─ #announcements
  └─ #faq

💬 COMMUNITY  
  ├─ #general
  ├─ #introductions
  └─ #media

🎮 GAMING
  ├─ #game-1
  └─ #game-2

🔧 UTILITIES
  ├─ #roles
  ├─ #bot-commands
  └─ #tickets

🛡️ MODERATION (Staff only)
  ├─ #mod-chat
  ├─ #mod-logs
  ├─ #action-logs
  └─ #reports
Channel Permissions Best Practices:
  • Default: Read-only for announcements
  • Enable slowmode in active channels (3-5s)
  • Restrict media/links in general chat initially
  • Create thread-only channels for organized discussions

​
Security & Safety

​
Account Protection

Critical Security Settings:
  1. Enable 2FA requirement for moderators
    • Server Settings → Moderation → Require 2FA
  2. Restrict @everyone permissions
    • Remove: Mention @everyone, Manage Webhooks
    • Review: Administrator permission (avoid when possible)
  3. Verify bot authenticity
    • Only invite bots from trusted sources
    • Check bot permissions before authorizing
    • Regular audit of server bots

​
Anti-Raid Configuration

# Enable verification level
Server Settings → Moderation → Verification Level: Medium/High

# Auto-moderation for new accounts
/config set automod.newaccount enabled
/config set automod.newaccount.age 7d
Setup before raids happen:
  • Create “lockdown” role (denies Send Messages everywhere)
  • Pre-write lockdown announcement
  • Document emergency procedures for mods
  • Enable slowmode presets
Immediate actions:
  1. Raise verification level to Highest
  2. Enable slowmode (30s+) in all public channels
  3. Temporarily disable invites
  4. Ban obvious raid accounts
  5. Monitor #member-logs for join patterns
After raid ends:
  1. Review and ban missed accounts
  2. Restore normal verification level
  3. Remove slowmode
  4. Re-enable invites
  5. Update automod rules based on raid patterns
  6. Post reassurance to community

​
Data Privacy

Responsible Data Handling:
  • Regularly purge old moderation logs (1+ year old)
  • Don’t share member data outside mod team
  • Respect member privacy in logging
  • Document data retention policies
  • Comply with GDPR/data requests
Fire doesn’t sell or share data. See Privacy Policy.

​
Maintenance Routine

​
Daily Tasks

  • Review overnight moderation logs
  • Check reports/tickets
  • Respond to pending actions
  • Monitor member count changes

​
Weekly Tasks

1

Configuration Review

  • Verify automod effectiveness
  • Check for false positives
  • Update filters based on trends
  • Review role assignments
2

Community Health

  • Analyze active channels
  • Review member feedback
  • Check engagement metrics
  • Plan community events
3

Staff Meeting

  • Discuss challenging cases
  • Update guidelines
  • Share feedback
  • Plan improvements

​
Monthly Tasks

Tag Maintenance

  • Review all tags
  • Update outdated content
  • Remove unused tags
  • Create new helpful tags

Role Audit

  • Clean up unused roles
  • Verify role hierarchy
  • Update role descriptions
  • Check self-assign ranks

Permissions Review

  • Audit channel permissions
  • Review bot permissions
  • Check role permissions
  • Update as needed

Analytics Review

  • Member growth trends
  • Active user metrics
  • Message volume by channel
  • Moderation action frequency

​
Scaling Strategies

​
Small Server (< 100 members)

Focus Areas:
  • Personal engagement (know your members)
  • Simple role structure
  • Minimal automation
  • Active recruitment
  • Community-building events

​
Medium Server (100-1,000 members)

Key Investments:
  • Structured moderation team
  • Comprehensive automod
  • Self-service tools (ranks, tags)
  • Organized channels
  • Regular events

​
Large Server (1,000+ members)

Critical Systems:
  • Dedicated mod team with shifts
  • Advanced automod + manual review
  • Extensive logging
  • Ticket system for support
  • Sub-communities/channels
  • Premium features essential

​
Premium Value Maximization

Get the Most from Premium

Priority Features to Implement:
  1. Ranks - Immediate member engagement boost
  2. Reaction Roles - Streamline verification and role assignment
  3. Unlimited Tags - Comprehensive knowledge base
  4. Role Persistence - Protect VIP members
  5. Voice Roles - Show active members
  6. Custom Identity - Professional branding
ROI Indicators:
  • Reduced mod workload (automod + self-service)
  • Higher member retention (better onboarding)
  • Improved engagement (ranks, tags)
  • Professional appearance (custom identity)

​
Troubleshooting Common Issues

Debug steps:
  1. Check Fire’s role position
  2. Verify channel permissions
  3. Check for role hierarchy issues
  4. Test in different channel
  5. Review audit log for errors
Solutions:
  • Review recent false positives
  • Whitelist trusted members/roles
  • Adjust thresholds (higher numbers = less strict)
  • Add exceptions for specific channels
  • Create appeal process
Improvements:
  • Add self-assign roles for personalization
  • Create events/activities
  • Enable starboard for highlights
  • Simplify channel structure
  • Active moderation presence
  • Regular announcements
Prevention:
  • Expand mod team
  • Increase automod usage
  • Create mod shifts/schedules
  • Implement ticket system
  • Recognize mod contributions
  • Allow mod breaks

​
Advanced Techniques

​
Multi-Server Management

Managing multiple servers with Fire:
1

Standardize configs

Create configuration templates for:
  • Automod settings
  • Role structures
  • Channel layouts
  • Tag libraries
2

Cross-server coordination

  • Use same mod team when possible
  • Share ban lists (manual process)
  • Coordinate on raid defense
  • Unified appeal process
3

Differentiate branding

Use custom identity per server:
/identity update
# Different nickname, avatar per server

​
Integration with Other Bots

Complementary Bots:
  • Music bots: Fire handles moderation, music bot for entertainment
  • Leveling/XP bots: Fire for rules, XP bot for gamification
  • Utility bots: Fire for core functions, specialty bots for niche features
  • Analytics bots: Fire logs, analytics bot for insights
Key: Clear role division prevents redundancy and conflicts

​
Resources & Support

Fire Support Server

Get help from Fire team and community

Feature Documentation

Detailed feature reference

Commands Reference

Complete command list

Premium Features

Unlock advanced capabilities
This guide represents proven strategies from successful Fire-powered communities. Adapt recommendations to fit your server’s unique needs and culture.

Build docs developers (and LLMs) love

Get started for freeTalk to us