Star Rupture Large-Base Build & Deconstruct Lag
Large factories can expose a client rendering limit, a server simulation problem, a save problem, or an Early Access regression. The useful fix starts by identifying which one you have; avoid universal tile thresholds and unsupported performance promises.
Separate the symptoms
- One player stutters: compare local graphics and the player's client.
- Everyone pauses together: inspect server logs, save activity, and the current build.
- Only building pauses: reproduce one placement and one deconstruction in a test copy.
- World loads slowly or reverts: follow the save/restart checks before resizing the host.
Measure before rebuilding
- Write down game build, server package, world identity, player count, and time of the pause.
- Ask whether the pause is visible to all connected players.
- Test one harmless build action and one deconstruct action, not a batch.
- Compare the production world with a fresh test world on the same machine.
- Save logs and a backup before removing anything from the main base.
If the current client exposes a performance overlay, use it to compare frame and game-thread behavior. Treat its labels as diagnostic evidence, not as proof of a specific internal subsystem unless the build documents that subsystem.
Low-risk layout improvements
- Remove unused decorative pieces only after a backup and only from a test copy first.
- Keep new production modules compact, with clear input/output hand-offs.
- Leave a walkway or service gap where the current build allows it so the next expansion is not one giant rebuild.
- Move a new line to a separate test area before joining it to the established factory.
- Schedule large changes when the fewest players are online.
Do not confuse host capacity with a game regression
More CPU or RAM can help when the machine is saturated, but it will not correct a bad save, blocked route, client-only rendering issue, or changed game behavior. Compare CPU, memory, disk, and network observations during the pause with a normal moment. Then retest after a clean restart.
Dedicated-server incident checklist
| Step | Evidence to keep |
|---|---|
| Reproduce | One build/deconstruct action and exact timestamp. |
| Compare clients | Whether the pause is shared or local. |
| Check save | Whether a clean stop, backup, and restart preserve the world. |
| Check build | Server/client versions and recent official announcements. |
| Escalate | Logs, save copy, steps, and the smallest reproducible base. |
Related guides
- Maintainable factory layouts
- Production bottleneck worksheet
- Placement rejection checks
- Server sizing
- Save and restore workflow
See managed Star Rupture hosting for current plan options and a persistent server workflow.