The top subscription tier is Sovereign, not Founder.
This has been corrected multiple times across sessions — fixing at source.
FILES UPDATED:
- docs/core/tasks.md
- docs/core/project-scope.md
- docs/tasks/rank-system-deployment/rank-structure.md
- docs/tasks/paymenter-pterodactyl-integration/README.md
- docs/archive/2026-02-09-consolidation/luckperms-structure.md
- docs/planning/subscription-tiers.md
- docs/planning/awakened-gateway.md
- docs/guides/subscription-automation-guide.md
- docs/guides/holly-discord-roles-setup.md
- docs/guides/holly-wanderer-permissions-setup.md
- docs/systems/arbiter-discord-role-mappings.md
- docs/branding/trinity-leadership-artwork.md
NOTE: References to 'founders' meaning Michael/Meg/Holly as company
founders were intentionally preserved. Only tier name updated.
Signed-off-by: claude@firefrostgaming.com
UPDATED: Part 2 Step 3 - Update Role Mappings in Bot
Changed from manual-only to dual-option approach:
OPTION A (RECOMMENDED): Discord Bot Admin Panel
- Holly can update role IDs herself
- No SSH access needed
- No bot restart needed
- Instant validation and feedback
- Zero downtime
- Audit logs posted to Discord automatically
- Complete workflow documented
OPTION B (MANUAL): SSH + Manual Edit
- Requires Michael's SSH access
- Requires bot restart
- Only use if admin panel not deployed yet
- Kept for backward compatibility
Updated Prerequisites Section:
- Added admin panel access requirement
- Clarified SSH only needed for LuckPerms testing
- Not needed for Discord role management anymore
Benefits of Update:
- Makes admin panel the primary, recommended method
- Reduces Holly's dependency on Michael
- Promotes modern, self-service workflow
- Still documents manual fallback if needed
Guide now properly reflects the new admin panel infrastructure
deployed in discord-bot-admin-panel.md
Chronicler #40
Part 3 now offers TWO ways to create LuckPerms groups:
METHOD A: Web Editor (RECOMMENDED)
- 30-45 minutes instead of 2-3 hours
- Visual interface with drag-and-drop
- Color picker for chat prefixes
- Built-in validation prevents mistakes
- Better for learning the structure
- Step-by-step guide for all 13 groups
METHOD B: Console Commands (ALTERNATIVE)
- Original ~150 command approach
- Exact and reproducible
- Good for documentation
- No internet upload required
- Same functionality as Method A
Benefits:
- Holly can choose based on comfort level
- Web editor is faster and less error-prone
- Console commands still available for automation/reproducibility
- Both methods produce identical results
Chronicler #40
CRITICAL SECURITY: WorldEdit is now restricted to staff only.
Changes:
- Created Builder group (for Holly) with full WorldEdit access
- Created Owner group (for Michael) with all permissions
- Explicitly DENIED worldedit.* to ALL subscriber groups (including Sovereign)
- Added gamemode, unlimited chunks/homes to staff
- Updated both deployment guides with staff group creation
Why this matters:
- Prevents subscribers from using WorldEdit to duplicate items
- Prevents WorldEdit-based griefing and chunk bypass exploits
- Even $499 Sovereign tier does NOT get WorldEdit
- Only Holly (Builder) and Michael (Owner) have access
Commands added to LuckPerms group creation section in both guides.
Chronicler #40
Added Task 7: Set Up DNS (Cloudflare) before Nginx configuration.
Michael needs to:
1. Add A record: webhook.firefrostgaming.com → 63.143.34.217
2. Set to DNS only (proxy OFF)
3. Verify DNS propagation with dig
Renumbered subsequent tasks (Nginx is now Task 8, Holly prep is Task 9).
Chronicler #40
Step 3 of Part 2 now clearly marked as Michael's task.
Holly creates roles and copies IDs, then hands to Michael.
Michael SSHs to Command Center and updates bot.js.
Prevents confusion about who has SSH access to Command Center.
Chronicler #40
Removed confusing SSH instruction. Holly should use Pterodactyl Panel
console directly - no SSH needed for running LuckPerms commands.
All servers share MySQL database, so commands on one server sync to all.
Chronicler #40
