Skip to content

Cap players at 5 and spend the headroom on view distance - #74

Merged
OpenSource-For-Freedom merged 1 commit into
mainfrom
chore/five-player-cap-view-distance
Oct 11, 2026
Merged

OpenSource-For-Freedom merged 1 commit into
mainfrom
chore/five-player-cap-view-distance

Conversation

@OpenSource-For-Freedom

Copy link
Copy Markdown
Owner

What

setting was now
MAX_PLAYERS 20 5
VIEW_DISTANCE 12 16
SIMULATION_DISTANCE 8 10

Resource limits and the droplet plan are untouched (s-4vcpu-8gb, $48).

Why

Five is the real population: known family members on an enforced whitelist.
20 was typed, never measured and never tested. A slot only costs memory while
someone is in it, so the worst case is what the box has to be sized for, and
capping at the real population cuts that worst case by three quarters on the
same hardware.

That headroom is spent on how the world looks. Loaded chunks scale with the
square of view distance: 20 players at 12 was up to 12,500 chunks, 5 players
at 16 is at most 5,445, still under half the old worst case. 16 is where
Terralith's terrain reads as scenery instead of fog. Simulation 10 is the
vanilla default, so farms and Create contraptions tick at normal range.

Cost and how to see it

Worldgen bursts while someone explores new terrain, visible in spark as tick
spikes. The fix for that is chunk pre-generation against a stopped world, not
lowering this again.

Validation

docker compose config validates; test_world_not_tracked,
test_world_no_player_data, test_client_server_mods, test_custom_mods_reviewed,
test_kubejs_script_hazards, test_security_alerts and test_design_role.js pass.
Touches no data/world/ path.

Note: merging restarts the container, so merge when nobody is playing.

MAX_PLAYERS 20 -> 5. Five is the real population: known family members on an
enforced whitelist. 20 was typed, never measured and never tested. A slot only
costs memory while someone is in it, so the worst case is what the box has to
be sized for, and capping at the real population cuts that worst case by three
quarters on the same 4 vCPU / 8 GB droplet.

That headroom is spent on how the world looks. VIEW_DISTANCE 12 -> 16 and
SIMULATION_DISTANCE 8 -> 10. Loaded chunks scale with the square of view
distance: 20 players at 12 was up to 12,500 chunks, 5 players at 16 is at
most 5,445, still under half the old worst case. 16 is where Terralith's
terrain reads as scenery instead of fog. Simulation 10 is the vanilla
default, so farms and Create contraptions tick at normal range.

Resource limits (cpus 3.5, mem_limit 6.5g, 5G heap) are untouched: the
droplet stays s-4vcpu-8gb. Every cheaper plan either halves RAM, which this
pack cannot take, or costs more than $48 for 4 vCPU.

The known cost is worldgen bursts while someone explores new terrain, which
spark will show as tick spikes. The fix for that is chunk pre-generation
against a stopped world, not lowering this again.
@OpenSource-For-Freedom
OpenSource-For-Freedom merged commit 4286cf1 into main Oct 11, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant