Ore Factory Squad v1.0.3 Patch Notes
Ore Factory Squad v1.0.3 from July 20, 2026: emergency invite-only security, Steam invites only, lobby codes disabled, hidden rooms in Server Browser.
Overview — Emergency Security Response
threeW released Ore Factory Squad v1.0.3 on July 20, 2026 as an emergency multiplayer security response after reports of external access to invite-only lobbies, griefing, unauthorized item selling, and impersonation. The patch temporarily restricted invite-only sessions to Steam invites from the pause menu, disabled lobby codes, and hid invite-only rooms from the Server Browser.
v1.0.4 followed the same day with authentication, bans, and additional Steam data protection. v1.0.5 on July 25 rebuilt lobby security comprehensively and restored codes, friend join, and Server Browser visibility for invite-only rooms. Read v1.0.4 and v1.0.5 for the full arc.
This page preserves the first emergency measures so squads understand why July 20 sessions felt different from launch-week co-op.
Invite-Only via Steam Invites Only
During v1.0.3, invite-only multiplayer meant Steam invites from the pause menu — not lobby codes, not casual Server Browser joins. Hosts sent invites to friends on their Steam list; guests accepted through Steam overlay or friends panel.
Public lobbies remained possible but carried higher risk until v1.0.5 Role & Permission System limited default Employee actions. Squads with sensitive factory layouts should have switched to invite-only during this window.
Our co-op guide join section was effectively Steam-invite-first for several days — update your squad playbook if you still reference disabled code sharing from July 20.
Watch Video Guide
Lobby Codes Temporarily Disabled
Lobby codes were disabled because external tools reportedly exploited code entry to reach hidden sessions. Sharing ten-digit codes in Discord or stream chat was unsafe until v1.0.5 implemented a protected handshake.
Groups accustomed to code-based joins needed to add each other on Steam temporarily or have the host send direct invites each session. Code culture returned in v1.0.5 — see patch notes for 10-digit format details.
If a stranger joined during v1.0.3 despite invite-only settings, report through official Discord channels — that feedback drove v1.0.4 and v1.0.5 hardening.
Server Browser Visibility Changes
Invite-only rooms no longer appeared in the Server Browser during v1.0.3 — even when searching — so unauthorized browse clients could not discover hidden sessions. Friends found games through Steam social join instead of scrolling public lists.
v1.0.5 restored invite-only visibility in the browser while keeping authentication layers — a compromise between July emergency hiding and launch-week discoverability. Check current behavior on v1.0.5 notes before planning public stream sessions.
Private versus public lobby mislabel bugs from v1.0.2 are separate from this security change — hosts should still verify lobby type when creating sessions.
What Squads Should Do Now
Update all clients to v1.0.5 — do not remain on v1.0.3 or v1.0.4 unless you have a specific compatibility reason. Current multiplayer includes text chat, restored codes, friend join, roles, and server-side protection.
Review factory permissions before reopening public lobbies. Default Employee role in v1.0.5 limits griefing vectors that motivated July hotfixes. Custom roles let trusted friends build while strangers haul.
No single-player or factory automation changes shipped in v1.0.3 — mining, conveyors, and contracts behaved as v1.0.2 except when griefers disrupted shared saves in compromised lobbies.
Frequently Asked Questions
Why was v1.0.3 released?
Emergency response to external access, griefing, item selling, and impersonation in invite-only lobbies.
Could I use lobby codes on v1.0.3?
No — codes were temporarily disabled until v1.0.5 restored them with protected handshake.
How did friends join invite-only games?
Steam invites from the pause menu only during v1.0.3 and v1.0.4.
Were invite-only rooms in the Server Browser?
No — hidden from browse during v1.0.3. v1.0.5 made them visible again with security layers.
Is v1.0.3 still recommended?
No — update to v1.0.5 for Phase 0 features and the final lobby security rebuild.