minecraft-server-admin
Set up, operate, tune, and troubleshoot Minecraft Java 26.x and legacy 1.21.x servers across Paper, Purpur, Folia, Velocity, Fabric, and NeoForge. Use for infrastructure, backups, proxies, and live operations, not plugin or mod development.
Jahrome907 · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Jahrome907/minecraft-agent-skills --skill minecraft-server-admin技能说明
name: minecraft-server-admin description: "Set up, operate, tune, and troubleshoot Minecraft Java 26.x and legacy 1.21.x servers across Paper, Purpur, Folia, Velocity, Fabric, and NeoForge. Use for infrastructure, backups, proxies, and live operations, not plugin or mod development."
Minecraft Server Administration Skill
Scope and Routing Boundaries
Routing Boundaries
Use when: the task is infrastructure or live operations for Minecraft servers (deployment choice, tuning, backups, proxying, security, incident response).Do not use when: the task is writing plugin code (minecraft-plugin-dev) or writing mods/loaders (minecraft-modding,minecraft-multiloader).Do not use when: the task is WorldEdit command workflows (minecraft-worldedit-ops) or EssentialsX workflow/policy design (minecraft-essentials-ops).Do not use when: the task is datapack/resource-pack authoring (minecraft-datapack,minecraft-resource-pack).
Support Assets
- Read
references/deployment-checklists.mdwhen the task is an incident, rollout window, proxy change, or recovery drill and you need a compact checklist before acting.
Deployment Decision Matrix
Use this table first. Pick a deployment type before changing configs.
| Deployment profile | Recommended stack | Pick this when | Watch-outs |
|---|---|---|---|
| Small SMP on Paper | Paper only | Up to ~30 concurrent players, broad plugin compatibility, low ops overhead | Do not over-tune early; profile before changing many defaults |
| Larger public Paper server | Paper + Spark + stricter plugin/change control | Public server with frequent joins, moderate plugin set, uptime matters | Plugin sprawl is the top TPS risk |
| Velocity-backed network | Velocity + multiple Paper backends | Hub/minigame/factions split across servers, need shared entrypoint | Forwarding/auth mismatches can block joins |
| Purpur gameplay-heavy server | Purpur (optionally behind Velocity) | You want gameplay knobs exposed in config without custom plugin code | Extra toggles increase misconfiguration risk |
| Folia high-concurrency server | Folia + Folia-compatible plugins only | Very high concurrency with region-threading goals | Many plugins are not Folia-safe |
| Fabric/NeoForge mod server | Fabric or NeoForge server build | You require loader mods, custom content, modpack behavior | Bukkit/Paper plugins do not apply |
Deployment Type Routing
- Small SMP and most public plugin servers: use Paper baseline first.
- Use Purpur only when you explicitly need Purpur gameplay controls.
- Use Folia only when plugin compatibility has been validated for region-threading.
- Use Velocity when one process is not enough or you need separate backend roles.
- Use Fabric/NeoForge when the requirement is mod-driven, not plugin-driven.
Playbook: Performance Tuning
Step 1: Establish baseline
Collect a baseline before edits. Linux host example:
free -h
top -b -n 1 | head -n 25
Windows PowerShell host example:
Get-CimInstance Win32_OperatingSystem | Select-Object FreePhysicalMemory,TotalVisibleMemorySize
Get-Process java | Sort-Object CPU -Descending | Select-Object -First 5 Id,CPU,WorkingSet,Path
In server console:
tps
mspt
spark healthreport
Record:
- peak player count
- MSPT at idle and at peak activity
- top plugins by CPU from Spark report
Step 2: Profile the real bottleneck
Use Spark instead of guesswork:
spark profiler --timeout 180
spark tps
spark tickmonitor --interval 10
Then identify whether the issue is:
- plugin task load
- entity count / mob farm pressure
- chunk generation / disk I/O
- garbage-collection pauses
Step 3: Apply targeted fixes
Do not tune everything at once. Apply one group at a time.
- Chunk and simulation pressure:
- lower
view-distanceandsimulation-distancefirst - pre-generate worlds for survival-heavy maps
- Entity pressure:
- adjust despawn ranges and mob-spawn behavior in Paper world config
- cap problematic entities where appropriate
- Plugin pressure:
- disable or replace top offenders from Spark traces
- reduce async task frequency where plugin settings allow
Step 4: Use stable startup flags
For Java 25 on current Paper/Purpur, start with a simple measured baseline:
java -Xms4G -Xmx4G -jar server.jar --nogui
Increase heap only when profiling and player load justify it. Add collector flags only after validating them against the exact JDK and Paper version.
Step 5: Verify improvements
After each change set:
spark tps
spark healthreport
Keep the change only if MSPT/tick stability improves under representative load.
Playbook: Plugin Operations
Safe plugin change workflow
- Build a plugin inventory:
- plugin name and version
- required dependencies
- minimum server version
- Stage updates:
- apply plugin updates in staging first
- run smoke checks: joins, teleports, economy, permissions, saves
- Production rollout window:
- announce maintenance window
- stop server cleanly
- snapshot plugin jars and config
- deploy update batch
- Post-rollout verification:
- watch startup logs for API warnings
- run command and permission sanity checks
- track TPS/MSPT for 15-30 minutes
Rollback checklist
- Keep previous plugin directory snapshot.
- If severe regression occurs:
- stop server
- restore prior plugin jars/configs
- start and confirm login/world integrity
- Document failing plugin/version pair for future blocks.
Playbook: Proxy and Forwarding (Velocity)
Velocity baseline
velocity.toml essentials:
bind = "0.0.0.0:25565"
online-mode = true
player-info-forwarding-mode = "modern"
forwarding-secret-file = "forwarding.secret"
Backend server requirements
server.properties on backend:
online-mode=false
Paper backend forwarding support (config/paper-global.yml):
proxies:
velocity:
阅读完整来源 ↗