BiggerLobbies

Friends join any time, rejoin after a crash, and nobody loses progress. Only the host installs it.

Schedule I's co-op stops at 4 players, and one crash can end the night. BiggerLobbies takes those limits away, and everyone else joins with the normal game.

What you get

• Room for everyone. 20 players by default, and anything up to 250 if your PC and connection can carry it.

• Invite whenever you like. Your game goes online as your save loads, so friends can accept an invite or use Steam's Join Game at any point in the session.

• Crashes don't end the session. A player whose game crashes can come straight back in, without you restarting.

• Nobody loses progress. The world saves every 5 minutes, each player every 30 seconds, and everything saves the moment someone drops.

• Everyone sees the same plants. Water levels and growth stay in step for every player, so a watered pot never shows as dry.

• On your Discord profile. Shows "Hosting a lobby, Friends only (3 of 20)" under Playing Schedule I. Each part can be turned off.

Run the room

Host settings sits under Settings in the main menu and the pause menu, or press F6 while you host. Changes apply straight away, without a restart.

• Players. See everyone's ping. Kick lets them rejoin; Ban keeps them out for an hour, a day, a week or for good. Players who also have BiggerLobbies are told why they were removed, and removed players drop off your lobby screen.
• Take items. Someone grabbed the product and left? Move their items and cash into your inventory, and they don't get them back if they rejoin. Every take is logged, with a copy of what they had. Changed your mind? Give back returns it to the player, only what you still carry.
• Ban reasons and mod check. Type a reason when you ban; players with the mod see it. The Players tab shows each modded player's version and any mods they're missing.
• Access. Build a whitelist from your Steam friends, save it as a crew, and load it next session in one click. Bans are saved between games and end on their own.
• Lobby. Private, Friends only or Open, and the lobby size, even while friends are in.
• Saving. How often the world and each player save, plus a Save now button.

Install

You need Schedule I 0.4.7, the default Steam branch.

1. Click Install with Mod Manager above, or search for SCHEDULE1-BiggerLobbies in r2modman or Thunderstore Mod Manager. MelonLoader v0.7.3 installs with it.
2. Launch with Start modded, not from Steam.
3. Load a save and invite your friends.

Updating? Your settings, bans and crews carry over.

Coming from the original ifBars-BiggerLobbies? Disable or uninstall it first. Two copies in one profile conflict.

Settings

Everything is on by default, and most of it is easier to change in Host settings. To edit the file instead, open r2modman's Config editor, file MelonPreferences.cfg, section [BiggerLobbies], then restart the game.

Good to know

• Friends don't need the mod. If they run MelonLoader for other mods, it must be v0.7.3 or later.
• Every player needs the same content mods as the host. A mod that adds new items or objects on the host but not on a friend's game breaks their world.
• It's built for the Il2Cpp game, the default Steam branch. The Mono (alternate) branch isn't supported on 0.4.7.
• MelonLoader won't load it alongside ModManager & PhoneApp.
• Going past 20 players? Your frame rate and upload speed set the real limit. The hosting guide explains what to expect.

Losing leaves, petrol or deliveries?

That's a bug in the base game, not the lobby. The companion mod ItemSafety catches it on the host. It's in alpha, so back up your saves first.

Something broke?

Open an issue on GitHub and attach the host's MelonLoader\Latest.log (turn on DiagnosticLog first for more detail). In r2modman, find it under Settings, Browse profile folder. The troubleshooting page covers load errors, friends who can't join, and lost progress.

Credits

BiggerLobbies was created by Bars (ifBars/BiggerLobbies). This fork, with the 0.4.7 update and everything since, is by mdoodm, with AI assistance, and published here under the SCHEDULE1 team. Source on GitHub, MIT licence.