Evidence-led direction
Shape the world. Then shape the server.
Resource guidance should start with how a world behaves, how a community gathers, and how safely the operator needs to change and recover it. The recommendation must explain its reasoning.
Five dimensions
Every direction needs an understandable reason.
These dimensions are a research framework, not measured capacity or an offer. Exact recommendations wait for approved workload evidence.
- 01
Research pending
CPU
Game loop behavior, extensions, simulation density, and burst work must be measured together.
- 02
Research pending
Memory
World state, active entities, extensions, and runtime behavior all shape working headroom.
- 03
Research pending
Storage
World growth, retained saves, logs, extensions, and recovery history need separate consideration.
- 04
Planned
Change
Updates, configuration edits, extension changes, and migration intent shape operating headroom.
- 05
Planned
Recovery
Backup scope, restore rehearsal, retained history, and verification affect the complete resource picture.
Recommendation rationale
The explanation travels with the direction.
A future recommendation should remain reviewable instead of becoming an unexplained label.
Planned
Establish fit
Choose the game direction and describe the shape of the world you intend to protect.Research pending
Gather evidence
Record community rhythm, extension intent, world history, and the moments likely to create operational pressure.Planned
Show the rationale
Explain which evidence supports the suggested direction, what remains unknown, and which change would trigger review.
Non-commercial preview
Begin with a game, not a tier.
The order path remains disabled until game certification, capacity evidence, service terms, and operator review are complete.