firefrost-operations-manual/docs/tasks/whitelist-manager/future-enhancements.md

Whitelist Manager - Future Enhancements

Document Created: February 19, 2026
Current Version: v1.0 (Fully Operational)
Status: Enhancement backlog for future consideration

---

Current Feature Set (v1.0)

Core Operations

• ✅ Add/remove players (username OR UUID)
• ✅ Single server operations
• ✅ Bulk operations (all servers)
• ✅ Dynamic server list from Pterodactyl API
• ✅ Auto-check status on page load
• ✅ Toggle whitelist ON/OFF per server
• ✅ Toggle whitelist ON/OFF for ALL servers

User Experience

• ✅ Real-time status: WHITELISTED / PUBLIC / OFFLINE
• ✅ Stats summary (Online/Whitelisted/Total)
• ✅ Activity log (last 5 operations, auto-refresh)
• ✅ Search/filter servers
• ✅ Color-coded node groups (TX1=orange, NC1=blue)
• ✅ Loading indicators for long operations
• ✅ Username validation (3-16 chars, alphanumeric + underscore)
• ✅ Keyboard shortcuts (Enter to submit)
• ✅ Auto-clear inputs after success
• ✅ Fade-in animations
• ✅ Fire/Frost themed UI
• ✅ SSL/HTTPS with Let's Encrypt
• ✅ Basic authentication
• ✅ Mobile-responsive design

---

Future Enhancements - Let's Consider

High-Impact Features

1. Export Whitelist to CSV

Value: Data portability, backup, analysis
Complexity: Low
Implementation:

• Add "Export" button to each server
• Generate CSV: player_name, uuid, date_added
• Bulk export: all servers in one CSV with server column

2. Import from CSV

Value: Onboarding new players en masse
Complexity: Medium
Implementation:

• File upload interface
• Parse CSV (columns: player_name, server)
• Preview changes before applying
• Validate all usernames first
• Apply in batches with progress indicator

3. Player Search

Value: "Is PlayerName whitelisted anywhere?"
Complexity: Medium
Implementation:

• Search box in header
• Query all running servers for player
• Show: Server name, whitelist status
• Quick actions: Remove from all, Add to missing

4. Scheduled Whitelist Changes

Value: Time-based automation (events, maintenance)
Complexity: High
Implementation:

• Schedule UI: date/time picker
• Action: enable/disable whitelist on server(s)
• Store schedules in SQLite
• Cron job to execute scheduled tasks
• Cancel/edit pending schedules

5. Discord Webhook Notifications

Value: Team awareness of whitelist changes
Complexity: Low
Implementation:

• Settings page to configure webhook URL
• Send notification on: add player, remove player, toggle whitelist
• Format: embed with server name, action, player, timestamp
• Optional: @role mentions for important changes

6. Whitelist Diff/Sync

Value: Keep servers consistent
Complexity: Medium
Implementation:

• "Compare Servers" button
• Show side-by-side diff of whitelists
• "Sync to Server A" action
• Preview: "Will add X, remove Y"
• Confirm and execute

7. Favorites System

Value: Quick access to VIPs, staff, frequent players
Complexity: Low
Implementation:

• "⭐ Favorites" section above operations
• Click player to quick-add to selected server
• Store in browser localStorage
• Add/remove from favorites list

8. Dark/Light Mode Toggle

Value: User preference, accessibility
Complexity: Low
Implementation:

• Toggle button in header
• CSS variables for colors
• Store preference in localStorage
• Light theme: white bg, dark text, blue/orange accents

9. Mobile-Optimized View

Value: Manage whitelists on the go
Complexity: Medium
Implementation:

• Responsive breakpoints for phone screens
• Swipe actions: swipe left = remove, swipe right = add
• Compact server list (icons instead of full status text)
• Bottom navigation for quick actions
• Collapsible sections

10. Audit Trail Export

Value: Compliance, debugging, accountability
Complexity: Low
Implementation:

• "Export Activity Log" button
• Download as CSV or JSON
• Filter by date range
• Include: timestamp, user, action, player, server, success/fail

---

Power User Features

11. Bulk Operations from File

Value: Mass onboarding from external systems
Complexity: Medium
Implementation:

• Upload .txt file (one player per line)
• Preview: "Will add N players to M servers"
• Validation: check all usernames
• Execute with progress bar
• Report: successes, failures, invalid names

12. Regex Player Search

Value: Pattern matching ("all players starting with 'VIP_'")
Complexity: Medium
Implementation:

• Search mode toggle: exact / regex
• Query all servers for matching players
• Results table: player, servers found on
• Bulk actions on results

13. Whitelist Templates

Value: Reusable configurations for events
Complexity: Medium
Implementation:

• "Save as Template" button
• Template name + description
• Store: server selection + player list
• "Load Template" → apply to servers
• Share templates between staff

14. Server Groups

Value: Organize servers by purpose (PvP, Creative, Event)
Complexity: Medium
Implementation:

• Tag servers with groups
• Filter by group
• Bulk actions on group
• UI: tabs for each group

15. API Key Management

Value: Automation, integrations, scripts
Complexity: High
Implementation:

• Generate API tokens with permissions
• Scopes: read-only, whitelist-manage, admin
• Rate limiting per key
• Revoke keys
• Usage logs per key
• REST API endpoints: /api/v1/whitelist/{server}/players

16. Webhook Triggers

Value: Paymenter integration (auto-whitelist on payment)
Complexity: High
Implementation:

• Receive webhook from Paymenter
• Parse: customer email, plan, payment status
• Map plan → servers (Tier 1 = Vanilla only, Tier 3 = All servers)
• Auto-add player to appropriate servers
• Send confirmation to Discord + email

---

Nice-to-Have Polish

17. Undo Last Operation

Value: Safety net for mistakes
Complexity: Medium
Implementation:

• Store last N operations in memory
• "Undo" button appears after operation
• Reverse action: add → remove, remove → add
• Timeout: 30 seconds or until next operation
• Can't undo batch operations (too risky)

18. Enhanced Confirmations

Value: Prevent accidents
Complexity: Low
Implementation:

• Tiered confirmations based on impact
• Bulk remove from ALL: type "REMOVE ALL" to confirm
• Disable whitelist on ALL: checkbox "I understand this makes servers public"
• Show impact: "This will affect 127 players across 10 servers"

19. Player Notes

Value: Context for why player was added
Complexity: Medium
Implementation:

• Optional "Note" field when adding player
• Examples: "VIP membership expires March 2026", "Staff member", "Event participant"
• View notes: hover over player in list
• Edit/delete notes
• Store in SQLite with player + server

20. Session Persistence

Value: Convenience, fewer clicks
Complexity: Low
Implementation:

• Remember: last selected server, filter settings
• Store in localStorage
• Restore on page load
• Clear button to reset preferences

---

Implementation Priority (If Pursued)

Phase 1: Quick Wins (1-2 hours each)

• Export whitelist to CSV
• Favorites system
• Dark/Light mode toggle
• Enhanced confirmations
• Session persistence

Phase 2: Medium Effort (3-5 hours each)

• Import from CSV
• Player search
• Discord webhook notifications
• Whitelist diff/sync
• Audit trail export
• Bulk operations from file

Phase 3: Major Features (6-10 hours each)

• Mobile-optimized view
• Regex player search
• Whitelist templates
• Server groups
• Player notes
• Undo functionality

Phase 4: Advanced Systems (10+ hours each)

• Scheduled whitelist changes
• API key management
• Webhook triggers (Paymenter integration)

---

Decision Framework

Before implementing any enhancement, ask:

1. Does this solve a real pain point?

   • Is someone asking for this feature?
   • Does it save time or prevent errors?

2. What's the maintenance cost?

   • Will this require ongoing updates?
   • Does it add complexity to debugging?

3. Is there a simpler solution?

   • Can we achieve this with existing features?
   • Is there a manual workaround that's acceptable?

4. Does it align with "set-it-and-forget-it"?

   • Remember: Building for low-maintenance future
   • Family planning means minimizing midnight emergencies

---

Current Assessment

The v1.0 whitelist manager is:

• ✅ Fully operational
• ✅ Solves the core problem (96.7% time reduction)
• ✅ Production-grade UI/UX
• ✅ Zero maintenance required
• ✅ Mobile-friendly enough
• ✅ Activity logging for accountability

Recommendation: Ship v1.0 as-is and gather real-world usage data before investing in enhancements. Let actual use cases drive future development rather than speculative features.

Exception: If a specific enhancement directly supports another infrastructure goal (e.g., Paymenter integration for subscriber management), prioritize that over speculative polish.

---

Notes for Future Chroniclers

If you're implementing any of these features:

1. Start with the backend - API endpoints first
2. Test thoroughly - Whitelist changes are high-impact
3. Document everything - Update this file with what you learned
4. Consider reversibility - Can operations be undone?
5. Think about scale - What happens with 1000 players?

Remember: This dashboard was built in ~5 hours across 2 sessions while Michael was recovering from a stroke. It already exceeds original requirements. Any enhancement should be driven by real need, not feature creep.

---

Fire + Frost + Foundation = Ship It 💙🔥❄️

Status: v1.0 COMPLETE - Enhancement backlog documented
Next Action: Use it in production, gather feedback, iterate based on real needs
Last Updated: February 19, 2026