1 Download the right build

Schedule I has two versions on Steam: IL2CPP (the default one you get when you install the game) and Mono (on the "alternate" beta branch). The S1DedicatedServers mod ships a separate client zip for each. The zip you install on your PC has to match the build your server is running.

Solace runs IL2CPP by default, so unless you specifically asked us for a Mono server, grab the IL2CPP client zip and you're set.

Open the releases page on GitHub: github.com/ifBars/S1DedicatedServers/releases

On the latest release, scroll to the Assets list and grab the file with Client and Il2cpp in the name (e.g. Il2cpp-Client.zip).

Use this

IL2CPP — Client

The default Solace build. Matches Schedule I's default Steam install — most players need this.

Only if asked

Mono — Client

For Mono servers. Requires switching Steam to the alternate beta branch first. See the callout below.

Tip: If you can't tell which is which, check the filename. The IL2CPP client asset will have Il2cpp or IL2CPP somewhere in the name. When in doubt, ask in our Discord and we'll point you at the correct file for the current release.
Running a Mono server? Two extra things to do before the rest of this guide:
  1. In Steam, right-click Schedule I → Properties → Betas → pick alternate from the dropdown. Let it re-download.
  2. Download the Mono client zip (not the IL2CPP one) from the releases page.
Skipping step 1 is the most common reason Mono players can't connect — your game is on the IL2CPP branch but your mod is built for Mono, so it fails silently.

2 Find your Schedule I install folder

The cleanest way is through Steam:

  1. Open Steam and go to your Library.
  2. Right-click Schedule I → Manage → Browse local files.
  3. A File Explorer window opens to your Schedule I install folder. Leave it open — this is where the mod files go.

If you prefer to navigate manually, the default path on Windows is:

C:\Program Files (x86)\Steam\steamapps\common\Schedule I
Heads up: if you installed Steam to a different drive (or on a Steam Library on a second drive), the path will be different — always use Browse local files to be sure.

3 Extract the mod into the game folder

  1. Open the .zip you downloaded in step 1.
  2. Select all files inside the zip and extract them directly into the Schedule I install folder you opened in step 2.
  3. If Windows asks whether to merge or replace any files, choose Yes / Replace. The mod intentionally overwrites a few game files so the multiplayer client can talk to the server.

You should now see new folders and DLLs (typically MelonLoader, Mods, and a handful of related files) sitting inside your Schedule I directory.

Antivirus note: some antivirus tools flag MelonLoader because it injects into a Unity game. This is a known false positive — the source is open on GitHub. If your AV deletes the file on extract, whitelist the Schedule I folder and re-extract.

4 Launch the game and connect

  1. Launch Schedule I from Steam normally.
  2. You should see a console window pop up briefly while MelonLoader initializes — this is expected.
  3. Once you're at the main menu, open the multiplayer / connect screen exposed by the mod.
  4. Paste your Solace server's IP and port (you'll find these on your server overview page in the Solace panel) and connect.

You're in. Anyone else joining your server needs to repeat steps 1–3 once on their machine; after that, they just launch and connect.

5 Troubleshooting

"Failed to connect" or instant disconnect

  • Wrong client build. Most Solace plans run IL2CPP — if you installed the Mono client zip by mistake, re-download the IL2CPP client and re-extract. (And vice versa for Mono-configured plans.)
  • Wrong Steam branch (Mono path only). If your server is Mono and your Schedule I is still on the default Steam branch, the client mod won't load against the IL2CPP game build. Right-click Schedule I in Steam → Properties → Betas → select alternate, let it re-download, then re-launch.
  • Version mismatch. Make sure your client mod version matches the server's mod version. If we just pushed a server-side update, you may need the matching new client zip.

Game crashes on launch after install

  • Verify game files in Steam (Right-click Schedule I → Properties → Installed Files → Verify integrity), then re-extract the mod.
  • Check that you extracted into the Schedule I folder, not a subfolder. The DLL files should sit right next to Schedule I.exe (or whatever the executable is called for your version).

Can't find the multiplayer / connect screen

  • Confirm MelonLoader actually loaded — the console window in step 4 should briefly show. If it doesn't, the mod files aren't in the right place.

Still stuck?

Open a ticket from your billing panel or hop into our Discord — include the mod release version you downloaded and any error text. We'll get you online.

Important: Schedule I doesn't have an official dedicated server option yet. The S1DedicatedServers mod is community-built and the developers (Solace included) aren't affiliated with TVGS, the game's developer. When the official server tooling ships, we'll migrate plans onto it automatically.

Need a server first?

Spin up a Schedule I server on Solace in under a minute — the S1DedicatedServers mod (IL2CPP by default) is pre-installed.

View Schedule I Plans

Related Articles