Schedule ISchedule 1 Dedicated Server Lag Fix (Stutter, Rubberbanding, Hitches)
Fix lag on a Schedule I dedicated server: memory, the targetFrameRate setting, autosave hitches, late game saves, mods and player side problems.
Updated Oct 7, 2026 · 5 min read
On this page
Lag on a Schedule 1 dedicated server mostly comes from the server running short on memory, short save hitches from autosaves, a late game world with lots of employees and products, or a mod. The dedicated server runs the full game headless through the S1DedicatedServers mod, so it needs more memory than most game servers: about 3 GB in use on an idle server before anyone joins. Give it room, keep targetFrameRate sensible, space out autosaves, and update to the latest Schedule I version for its memory fixes.
Server lag or one player?
| What you see | Where to look |
|---|---|
| Everyone stutters at the same moment every few minutes | Autosave hitches |
| Lag builds up over hours, better after a restart | Memory filling up |
| Lag got worse as the business grew | Late game load on the server |
| Lag started after adding a mod | That mod |
| Only one player rubberbands | Their connection or PC |
| Low frame rate for one player, NPCs move smoothly | Their PC's graphics, not the server |
When only one player lags, check their ping, ask them to close downloads and streams, and try a wired connection. The server cannot fix a player's frame rate.
Fix 1: Give the server enough memory
Because the server runs the whole game, memory runs out sooner than people expect. The S1DS docs measured about 3 GB in use on an idle server with 0 to 1 players. Each player, employee, property and stored product adds to it.
Signs of a memory squeeze:
- Lag that grows the longer the server runs, and goes away after a restart.
- The server hitching hard or crashing during busy moments.
- Memory use near the limit in your host's stats.
Rough sizing:
| Group | Memory |
|---|---|
| Up to 4 players | 6 GB |
| Up to 8 players with employees and several properties | 8 GB |
| Up to 16 players, or a big late game world | 12 GB |
A daily restart also helps a long running server stay fresh.
Fix 2: Update the game
Schedule I is in early access and updates often, sometimes with performance fixes. The v0.4.7 update changed how icons for mixed products are generated and saved, and TVGS said that should save several hundred megabytes of memory on late game saves. The v0.4.7 notes for servers cover it. Keep the server and the S1DS mod current with the update guide, and back up first.
Fix 3: Set targetFrameRate
In server_config.toml, the [performance] section sets the server's tick target:
[performance]
targetFrameRate = 60
vSyncCount = 0
The docs give 30 to 60 as the normal range. 60 is smoother for players. On a busy late game world, dropping to 30 frees CPU and can stop the server falling behind, which players feel as less rubberbanding even though the tick rate is lower. Keep vSyncCount = 0. Restart after changing it.
Fix 4: Space out autosaves
If everyone stutters at the same moment on a regular beat, it is the autosave. The defaults:
[autosave]
autoSaveEnabled = true
autoSaveIntervalMinutes = 15.0
autoSaveOnPlayerJoin = true
autoSaveOnPlayerLeave = true
The docs warn that very short intervals cause save spikes on low CPU hosts. Keep the interval at 10 to 15 minutes. Do not turn autosave off to hide the hitch, and keep the join and leave saves on: they protect the world when the last player logs off. A big crew joining and leaving often does trigger more saves, which is a fair trade.
Fix 5: Pause the world when nobody is on
A world that keeps running all night with nobody connected keeps simulating employees, customers and timers. For a friends server, setting pauseGameWhenEmpty = true under [gameplay] stops that. It does not change lag while people play, but it keeps memory growth and unattended progress down between sessions. For a public server with players dropping in at all hours, leave it off. More in the server settings guide.
Fix 6: Check mods
MelonLoader mods run inside the server's game. A mod that spawns many objects, runs heavy logic every frame, or was built for an older version can cause steady lag or sudden hitches.
- Note when the lag started and which mods changed around then.
- Move the newest mod out of the server's
Modsfolder and restart. - If lag drops, update that mod or contact its author.
Keep server mods and player mods matched, since S1DS checks client mods on join. The mods guide covers which mods suit multiplayer.
Fix 7: Network basics on a self hosted server
On a home server, the upload speed of your connection limits everyone. Every player's updates go out through it. If lag only appears when someone on the same network streams or uploads, that is the cause. Wired connections for the server PC, and no heavy uploads while people play, make a real difference.
A smoother option
On a GamezServers Schedule I server, plans are sized by memory with room for the game's high baseline, you can move to a bigger plan as the business grows (prorated, world kept), server_config.toml is in the file manager, and the live console shows saves and errors as they happen. MelonLoader and S1DS are installed and updated for you. See the Schedule I game page.
FAQ
Why does my Schedule 1 server lag every 15 minutes?
That is the autosave. Keep the interval at 10 to 15 minutes and make sure the server has enough memory, which makes each save shorter.
How much RAM does a Schedule 1 dedicated server need?
About 3 GB is in use before anyone joins. Plan on 6 GB for a group of four, more for bigger crews and late game worlds.
Does lowering targetFrameRate reduce lag?
On a server that is falling behind, yes. 30 is the low end of the normal range and frees CPU for the rest of the game.
Do mods cause lag on a Schedule 1 server?
They can. Remove recently added mods one at a time to find out, and keep every mod on a version built for the current game.
Skip the setup. Your own Schedule I server.
Then $14.99/mo. Just trying it? $3.75 for 3 days