Add task: Game server startup script audit & optimization (recurring issue source)
This commit is contained in:
@@ -172,6 +172,30 @@
|
||||
|
||||
---
|
||||
|
||||
### Game Server Startup Script Audit & Optimization
|
||||
**Status:** New — identified Feb 13, 2026
|
||||
**Priority:** MEDIUM (recurring issue source)
|
||||
**Scope:** All 12 game servers (6 TX1, 6 NC1)
|
||||
|
||||
**The Problem:** Multiple issues have traced back to startup scripts. These need a systematic audit and optimization pass to prevent recurring problems.
|
||||
|
||||
**Plan:**
|
||||
1. Pull and review every game server startup script via Pterodactyl panel
|
||||
2. Identify common issues (memory allocation, JVM flags, mod loading order, timeout settings)
|
||||
3. Establish a baseline "good" startup template per modpack type
|
||||
4. Optimize each server's startup script individually
|
||||
5. Document the optimized scripts in the repo (new file: `docs/reference/game-server-startups.md`)
|
||||
6. Test each server after changes
|
||||
7. Monitor via Uptime Kuma for stability post-optimization
|
||||
|
||||
**Servers to audit:**
|
||||
- **TX1 Dallas:** Stoneblock 4, Reclamation, Society: Sunlit Valley, Vanilla 1.21.11, All The Mons, FoundryVTT
|
||||
- **NC1 Charlotte:** The Ember Project, Minecolonies: Create and Conquer, All The Mods 10, EMC Subterra Tech, Homestead, Hytale
|
||||
|
||||
**Notes:** This is hands-on work — needs a session where Michael can access the panel and we review together.
|
||||
|
||||
---
|
||||
|
||||
## 🟢 LOW PRIORITY
|
||||
|
||||
### Workflow Guide Review & Trim
|
||||
|
||||
Reference in New Issue
Block a user