Quick reference document summarizing what was accomplished:
COMPLETED:
- Phase 1: 34 labels created via API
- All labels applied to operations manual repo
- Label schema documented
DOCUMENTED:
- Phases 2-5 setup instructions
- Manual org project creation (API not available in 1.21.5)
- Issue templates (YAML examples)
- n8n automation plans
NEXT ACTIONS:
- 5-minute manual setup (create org project via web UI)
- Create test issue
- Verify Kanban board works
- Then start using for real work
DECOMMISSIONED:
- Task #48 (Gitea→Plane integration) = WON'T DO
- Plane.io no longer needed
This summary provides quick reference for session accomplishments
and clear next steps for Michael to activate the system.
PHASE 1 COMPLETE: Global Label Schema
- Created 34 standardized labels via Gitea API
- 6 status labels (scoped)
- 4 priority labels (scoped)
- 6 type labels (scoped)
- 9 area labels (non-scoped)
- 3 assignment labels (for Holly/Meg/Michael)
- 3 special labels
Labels successfully applied to operations manual repository.
PHASE 2-5 DOCUMENTED:
- Organization-level project creation (manual via web UI)
- Issue creation workflow (web UI + tea CLI)
- Issue templates (YAML examples for bug reports and tasks)
- n8n automation plans (Discord notifications, auto-labeling)
COMPLETE SETUP GUIDE:
- Step-by-step instructions for creating Kanban project
- Workflow examples (Holly gets task, bug report, feature request)
- Migration plan from tasks.md to Gitea Issues
- Benefits of Gitea-native approach vs Plane.io
DECOMMISSIONED:
- Plane.io integration (Task #48 = WON'T DO)
- No external sync needed
- Single source of truth = Gitea
Related to Gemini's architectural brief and shift to stateless
Gitea-native lifecycle management.
Next: Michael to create org project via web UI, then we migrate
tasks from tasks.md to Gitea Issues.
- Created comprehensive Pterodactyl-based world backup procedure
- No SSH required - all through Panel interface
- Step-by-step archive, download, rename, upload workflow
- Troubleshooting section for common issues
- Created Holly's retirement checklist for 10 servers
- Special section for RAD2 (her build)
- 3 TX1 Dallas servers + 6 NC1 Charlotte servers
- Checkboxes for start, Nextcloud upload, deletion
- Notes section for each server
- Troubleshooting and contact info included
Related to soft launch preparation and server fleet optimization.
Supports server sunset evaluation (Task #45).
Created comprehensive procedure for configuring Simple Voice Chat mod on Minecraft servers.
Issue identified: Log shows voice chat server attempting to start on port 24454 but port may not be exposed through firewall/Pterodactyl, preventing players from using voice chat functionality.
Procedure includes:
- Discovery: Identify servers with Simple Voice Chat installed
- Port allocation strategy (24454-24464 for 11 servers)
- Pterodactyl configuration (UDP port allocation)
- Server config file updates (voicechat-server.toml)
- Firewall configuration (ufw rules for TX1/NC1)
- Client-side instructions for players
- Troubleshooting guide (connection issues, audio problems)
- Port allocation tracking table
Technical details:
- Protocol: UDP (not TCP - critical for voice chat)
- Port range: 24454-24464 (one unique port per server)
- Firewall rules for both TX1 Dallas and NC1 Charlotte
- Configuration file location: config/voicechat-server.toml
Time estimate: 4-6 hours total implementation (30 min per server)
Priority: Medium (quality of life enhancement, not critical)
Success criteria:
- Server logs show voice chat started successfully
- Players see green connection icon (not red)
- Proximity voice chat functions in-game
- No port conflicts between servers
Created by: The Blueprint
Status: Ready to implement when resources available
Created standardized testing procedure for all new server deployments.
DOCUMENT TYPE: Standard Operating Procedure
DOCUMENT ID: FFG-SOP-001
VERSION: 1.0
SCOPE:
- New server deployments
- Major modpack updates
- Server migrations
- Post-crash recovery testing
TESTING PHASES:
1. Connection (5 min) - Verify players can connect
2. Initial Spawn (10 min) - Basic world loading and interaction
3. Server-Specific Features (15-20 min) - Mod/plugin functionality
4. Exploration & Base Selection (20-30 min) - World generation, base scouting
5. Performance Check (10 min) - Sustained play under load
6. Final Report (5 min) - Documentation and assessment
STANDARD DELIVERABLES:
- Testing report (docs/testing/[server]-[date]-test-report.md)
- Base location recommendations with coordinates
- Issue prioritization (Critical/Major/Minor)
- Go/No-Go decision for public launch
CUSTOMIZATION:
- Template adaptable for vanilla, modded, skyblock, creative servers
- Server-specific feature tests (Cobblemon, tech mods, etc.)
- Automation script for checklist generation
TIME REQUIREMENTS:
- Minimum test: 30 minutes (phases 1-3)
- Standard test: 60 minutes (phases 1-5)
- Full test: 90 minutes (all phases + exploration)
BASED ON:
- Holly's All The Mons testing (2026-02-18)
- Proven to catch critical issues before public launch
PURPOSE:
- Prevent launching broken servers to players
- Standardize quality assurance
- Document base locations for new players
- Professional operations
Status: Active procedure, ready for immediate use
Fire + Frost + Foundation 💙🔥❄️
