ZED ZONE: Six-Digit Room Code Invisible While Typing

Direct answer · Nov 7 temporary guest-input workaround; v1.0.12 Nov9 host diagnostic; v1.0.13 Nov10 direct-connection improvement

The developer warned that the co-op room-code input may accept all six digits even if the text field appears blank. Type the code anyway, then select Join; the invisible display is distinct from a real server connection failure.

Jump straight to the steps ↓

THE TASK

Six-Digit Room Code Invisible While Typing

  1. 01

    Confirm that your host provided a six-digit room code and that you are entering it into the correct co-op Join field.

  2. 02

    Enter the complete code carefully despite the missing visible characters, then select Join through the game's normal menu.

  3. 03

    If a password is required, supply it separately; if joining still fails, record the actual network error rather than assuming the invisible-input issue is the cause.

Source-checked task schematic · Decision points

Room-code text hidden versus room-code connection failure

Decision points

Source-backed editorial schematic, NOT gameplay screenshot or scale map. It is not an in-game screenshot and not a map drawn to scale.

Open the specific source evidence ↗

Prerequisite

The developer documented an invisible field that still accepts input.

Success check

The joining attempt proceeds with the entered code; connection success is a separate condition.

01

Get code

Host provides the complete six-digit room code

02

Enter

Type all six digits even if no characters visibly appear

03

Join

Press Join; add password if the session uses one

04

Separate error

If connection fails, record the network error rather than treating it as a text-field issue

IMPORTANT LIMITS

What if your result is different?

This is a documented temporary developer workaround for a display bug, not proof that every multiplayer session or region can connect.

EVIDENCE

Sources for Six-Digit Room Code Invisible While Typing

Evidence and version: Nov 7 temporary guest-input workaround; v1.0.12 Nov9 host diagnostic; v1.0.13 Nov10 direct-connection improvement

November 10 version boundary: room code visibility versus connection success

ZED ZONE developer official announcement index is the first-party source for 1.0.13; SteamDB is a third-party archived copy of the developer-authored changelog.

Developer Patch 1.0.13 (November 10) improves the success rate of direct co-op connections. This does not explicitly say it fixed the separate invisible guest room-code text field described on November 7. Even after the latest patch, treat these as distinct symptoms:

  1. Text appears blank but guest can type six digits: enter the host’s correct six digits, add a separate password if required, select Join, and check whether you actually enter the host’s session.
  2. Digits show correctly, but direct connection fails: use the actual error message to troubleshoot the direct connection and verify the 1.0.13 build; do not assume the old display-only workaround repairs a network failure.
  3. The host never receives a code: open the host-side 20-second diagnostic guide. It is not the same input-field bug.

Success is joining an active host session, not a pop-up, visible digits, or an improved statistical connection rate. Screenshots of the current build, blank-field input, and final joined lobby are still needed for a visual walkthrough; no GGClue client playtest is claimed.

November 10 v1.0.14 is not a text-field fix

The newer November 10 v1.0.14 patch addresses co-op progress rollback, distant guests failing to harvest materials and other network/collision cases. It does not identify a change to the earlier blank-looking six-digit guest room-code text field. Continue to diagnose guest can type but cannot see six digits separately from host does not receive a room code and from visible code but failed connection.

A successful check requires a guest actually joining the host’s live session. The 1.0.13 patch improved connection success rates; neither that nor 1.0.14 guarantees the old display workaround has been removed. No current-build owned video of the input field is available.