Ore Factory Squad Co-op: Fix Invites & Lobby Codes

Ore Factory Squad supports solo play and online co-op for up to four players. The game does not assign fixed classes. Every role on this page is a suggested team agreement, not a locked profession or official “best build.”

STATUSv1.0.5 Invite Changes

The July 25 update rebuilt parts of lobby security and restored several join paths:

• Lobby Codes are enabled again and now use a protected 10-digit handshake;
• invite-only rooms are visible in the Server Browser again;
• direct Steam friend joining and invites from outside the game are enabled again;
• the multiplayer flow uses additional server-side protection and multi-step authentication.

If a friend cannot join, first confirm that every player is on the same current version and that the host selected the intended room visibility.

Recommended join sequence

1. confirm that every player runs the full game, not a mix of demo and release versions;
2. update every client to the same current version;
3. let the host create the session;
4. open the pause menu;
5. use a direct Steam invite, the Steam friends list, or the current 10-digit Lobby Code;
6. have the guest confirm the correct host and room;
7. if one method fails, retry with a fresh room before changing unrelated network settings.

SHAREDWhat Is Shared?

The official game describes the squad as one operation. A documented launch-week two-player session reported shared:

• progress;
• cash;
• unlocked Licenses;
• Contracts and deadlines;
• property purchases.

That session also reported individual backpack capacity, meaning one player could carry more after a personal capacity upgrade.

The v1.0.5 update added Roles & Permissions through the computer application. The default Employee role has more limited permissions for public-lobby protection, and hosts can edit roles or create custom roles.

Before the first expensive action, confirm:

• who can accept a Contract;
• who can buy a property or vehicle;
• who can place or remove a machine;
• who can use End Day;
• which upgrades are personal and which are shared.

Record the current behavior instead of relying on another group’s launch-week save.

COMMSCurrent Communication Tools

Voice Chat

Voice Chat is current. An official demo patch added input and output device selection.

Use short, specific calls:

• “Contract 208 selected.”
• “Need 15 Clay Bricks.”
• “Pallet Packer output blocked.”
• “Dynamite thrown. Clear the tunnel.”
• “Ending day after delivery.”

Emote System

The Emote System is current and intended for expression while playing with friends. Use the actions visible in the current Emote wheel for:

• confirming a handoff;
• marking a direction;
• signaling that an area is clear;
• celebrating a completed delivery.

The public announcement does not list every current Emote. Open the current wheel in your own build to see the available set.

Text Chat and permissions

Text Chat is current in v1.0.5. Hosts can also use the Roles & Permissions interface to restrict what public-lobby participants can do. The official screenshot shows where this interface lives; open it in the current build for the available permissions and defaults.

ROLESSuggested Roles by Squad Size

Two players

Switch when one side becomes idle. A fixed role is less useful than keeping the next complete production cycle moving.

Three players

This split works well when one person can continue mining while another completes the slowest product and the third clears delivery outputs.

Four players

These are coordination zones, not exclusive permissions. The fourth player should help the current bottleneck rather than waiting beside an empty loading dock.

FLOWAccurate Team Workflow

    [ Contract and Stock Check ]
                  │
                  ▼
       [ Choose Exact Products ]
                  │
        ┌─────────┴─────────┐
        ▼                   ▼
    [ Mining Team ]    [ Factory Team ]
        │                   │
        ▼                   ▼
    Pack Mining Boxes   Select Correct Recipe
        │                   │
        ▼                   ▼
    Mining Lift         Finished Product Pallet
        │                   │
        └─────────┬─────────┘
                  ▼
           [ Pallet Packer ]
                  │
                  ▼
      [ Forklift → Vehicle → Delivery Gate ]

This flow does not require:

• an Automatic Pallet System;
• a Merger;
• underground filter Splitters;
• Lift conveyor ports;
• generators or power cables;
• fixed morning and afternoon shifts.

SESSIONStep-by-Step Co-op Session

Step 1: Agree on one complete objective

Before players spread across the map:

1. check current cash;
2. inspect active Contracts;
3. identify the exact finished products;
4. check tracked stock;
5. choose one order or upgrade;
6. agree before anyone spends shared money.

Avoid accepting several attractive orders when the factory cannot make their slowest products.

Step 2: Divide the current bottleneck

If a raw resource is missing:

• one player checks Remaining Resources;
• one prepares or extends the Mining Lift route;
• another protects factory cash and prepares the correct machine;
• the delivery player clears old pallets and outputs.

If all raw materials already exist:

• keep most players in the factory and delivery flow;
• do not send everyone underground out of habit.

Step 3: Use exact handoff language

Call out finished stages:

• say Clay Block or Clay Brick, not “Clay”;
• say Limestone Block or Cement, not “Limestone stuff”;
• say Contract Output or Excess Output, not “the red pallet.”

Precise labels prevent one player from converting or selling an intermediate another player reserved.

Step 4: Protect the Pallet Packer area

Keep clear space for:

• input product pallet;
• Contract Output;
• Excess Output;
• Forklift approach;
• cargo-vehicle loading.

One player should own the active packing sequence until the delivery load appears. That is a team convention, not a game permission.

Step 5: Confirm before End Day

A tested Contract with one day remaining expired when the player used End Day. Active machines could continue after dark in the same launch-week test.

Before advancing:

1. read every active deadline;
2. check whether a queue can finish during the current night;
3. verify that no completed load remains at the warehouse;
4. announce the action to the squad.

SAFETYDynamite Safety in Co-op

A close blast caused a visible player hit reaction in solo testing. Current evidence does not establish:

• a three-second universal fuse call;
• a fixed safe distance;
• guaranteed team kills;
• guaranteed destruction of machines, pallets, or vehicles.

Use a conservative team procedure:

1. announce the target in Voice Chat;
2. confirm the tunnel behind the thrower is clear;
3. throw one stick;
4. have every player remain away until the blast finishes;
5. inspect before throwing another.

This is a safety convention, not a measured damage formula.

AVOIDCommon Co-op Mistakes

New squads can follow the first-hour progression guide before dividing work. For a shared production objective, use the Contracts and Pallet Packer guide; for a clean underground handoff, use the Mining Lift guide.

FAQFrequently Asked Questions