Skip to main content

​
What are Packs?

Packs are complete automation bundles that include everything needed for a specific feature. Unlike simple automations, packs contain multiple components working together to provide comprehensive functionality.

Complete Bundles

Multiple automations, commands, variables, and assets working together as a cohesive system.

Visual Identity System

Color-coded categories with auto-detection, custom branding, and consistent theming.

One-Click Installation

Automated setup with conflict resolution and configuration wizard.

Marketplace Integration

Browse, install, and manage community-created packs with ratings and reviews.

​
Pack Components

​
What’s Inside a Pack

Related workflows that work together
  • Welcome system + Auto-role assignment
  • Moderation logging + Appeal handling
  • Economy commands + Leaderboard display
Custom Discord commands linked to automations
  • /kick [user] [reason] → Moderation automation
  • /balance [user] → Economy lookup automation
  • /ticket create → Support ticket automation
Shared data storage across pack components
  • User balances, warning counts, XP levels
  • Server settings and configuration
  • Pack-specific preferences
Discord resources created automatically
  • Roles: “Muted”, “VIP”, “Level 10”
  • Channels: “mod-log”, “welcome”, “tickets”
  • Categories for organization

​
Visual Identity System

​
Pack Categories

Packs are organized into visual categories with consistent colors and icons:
CategoryColorIconUse Cases
🛡️ ModerationRed (#dc2626)ShieldKick, ban, timeout, warnings
💰 EconomyYellow (#eab308)CoinsCurrency, shop, work commands
🎮 Fun & GamesGreen (#10b981)GamepadMini-games, entertainment
🔧 UtilityIndigo (#6366f1)WrenchTools, management helpers
🎵 MusicPurple (#8b5cf6)MusicAudio playback, playlists
👋 WelcomeGreen (#22c55e)UserCheckMember onboarding, greetings
📈 LevelingOrange (#d97706)AwardXP systems, ranks, rewards
👑 Server ManagementViolet (#7c3aed)CrownAdmin tools, configuration

​
Automatic Category Detection

The system automatically detects pack categories based on content: 
// Examples of automatic detection
"Moderation Pack" → 🛡️ Moderation (Red)
"Economy Bot" → 💰 Economy (Yellow)
"Welcome System" → 👋 Welcome (Green)

​
Custom Visual Identity

Pack creators can customize the visual appearance:
  • Custom Colors: Override category colors with brand colors
  • Custom Icons: Choose from 100+ Lucide icons
  • Display Mode: Emoji, icon, or auto-detection
  • Branding: Consistent visual identity across dashboard

​
Pack Examples

​
Moderation Pack

Complete server moderation system Components:
  • Commands: /kick, /ban, /timeout, /warn, /appeal
  • Automations: Auto-moderation, escalation system, appeal handling
  • Variables: Warning counts, mute history, ban appeals
  • Assets: “Muted” role, mod-log channel
Features:
  • Automatic spam detection and action
  • Warning system with escalation (warn → timeout → kick → ban)
  • Appeal system with admin approval workflow
  • Comprehensive moderation logging

​
Economy Pack

Virtual currency and rewards system Components:
  • Commands: /balance, /work, /daily, /shop, /rob, /give
  • Automations: Income generation, shop purchases, leaderboards
  • Variables: User balances, work cooldowns, shop inventory
  • Assets: Economy channels, leaderboard displays
Features:
  • Daily income and work commands
  • Virtual shop with purchasable items
  • Leaderboards and wealth tracking
  • Anti-cheat and rate limiting

​
Welcome Pack

Member onboarding and engagement Components:
  • Commands: /welcome setup, /autorole config
  • Automations: Welcome messages, auto-role assignment, member tracking
  • Variables: Join counts, welcome settings, role configurations
  • Assets: Welcome channel, member-count displays
Features:
  • Customizable welcome messages with embeds
  • Automatic role assignment based on criteria
  • Member milestone celebrations
  • Join/leave logging and analytics

​
Pack Installation Process

​
1. Discovery & Preview

  • Browse marketplace by category
  • View pack screenshots and descriptions
  • Read user reviews and ratings
  • Check required permissions

​
2. Configuration Wizard

Required Inputs: Pack-specific settings you must configure
  • Welcome channel selection
  • Moderator role assignment
  • Currency name and starting balance
  • Log channel designation
Optional Settings: Customize pack behavior
  • Enable/disable specific features
  • Adjust cooldowns and limits
  • Choose notification preferences

​
3. Conflict Resolution

Command Conflicts: If commands already exist
  • Auto-rename with prefixes (mod_kick, econ_daily)
  • Manual rename during installation
  • User choice to replace or skip
Asset Conflicts: If roles/channels exist
  • Reuse existing assets
  • Create with pack prefix
  • Manual mapping during setup

​
4. Installation Verification

  • Test all commands work correctly
  • Verify permissions are sufficient
  • Check automation triggers properly
  • Validate variable storage

​
Pack Management

​
Dashboard Integration

Installed Packs View:
  • Visual pack cards with category colors and icons
  • Enable/disable toggle for entire packs
  • Quick access to pack configuration
  • Update notifications and changelog
Pack Configuration:
  • Individual command enable/disable
  • Automation settings adjustment
  • Variable value management
  • Asset configuration
Performance Monitoring:
  • Pack usage statistics
  • Command execution counts
  • Automation success rates
  • Error tracking and resolution

​
Pack Updates

Version Management:
  • Semantic versioning (1.0.0 → 1.1.0)
  • Changelog viewing
  • Selective update installation
  • Rollback capability
Migration Handling:
  • Automatic configuration migration
  • Variable schema updates
  • New feature enablement
  • Backward compatibility

​
Creating Custom Packs

​
Pack Creation Process

1

Design Components

Plan your automations, commands, and variables that work together.
2

Build Automations

Create the workflows using the visual automation builder.
3

Define Commands

Set up slash commands that trigger your automations.
4

Configure Variables

Define shared data storage and default values.
5

Set Visual Identity

Choose category, colors, and icons for your pack.
6

Test Installation

Verify the pack installs and works correctly.
7

Publish to Marketplace

Submit for community use with documentation.

​
Best Practices

Pack Design:
  • Single Purpose: Focus on one main feature area
  • Complete Solution: Include all necessary components
  • User-Friendly: Clear configuration and documentation
  • Tested: Thoroughly test in multiple server environments
Visual Identity:
  • Consistent Theme: Use category colors appropriately
  • Clear Icons: Choose recognizable, relevant icons
  • Good Naming: Descriptive pack and command names
  • Professional Appearance: Polished visual presentation

​
Security & Safety

​
Pack Validation

  • Permission Auditing: All required permissions clearly listed
  • Rate Limiting: Built-in protection against abuse
  • Code Review: Public packs reviewed before approval
  • Version Control: Immutable version history

​
Installation Safety

  • Dry Run Preview: See all changes before installation
  • Rollback Support: Automated rollback on failure
  • Conflict Detection: Identify and resolve conflicts
  • Permission Preflight: Validate permissions before install
Packs are designed to be safe and reversible. You can always uninstall a pack to return your server to its previous state.
Always review pack permissions and configuration before installation. Some packs may require administrative Discord permissions.

​
Next Steps