Dumb Ways to Build Wiki

Decide who will create the session and confirm which friends are joining. Keeping the group size and platform setup clear makes the connection process easier.

• Use a single host for the session.
• Confirm that everyone is ready before launching a Crisis Job.
• For groups of four, assign responsibilities before construction begins.

The host creates an online room, while other players join through the available friend or room-code flow. Share the room code directly with the intended players.

• Double-check the code before sending it.
• Do not begin a job while a teammate is still connecting.
• If a player cannot join, return to the room screen and retry the join flow.

Use the game's cross-platform multiplayer support when teammates are playing on different supported platforms. Make sure every player is using the same intended online session.

• Confirm each player's platform and account connection before troubleshooting the room.
• Invite players through the supported friend or room-code method.
• If the party separates, have everyone rejoin the host's room rather than creating several parallel rooms.

Use proximity voice to communicate while players are near one another, and establish short callouts for building, testing, hazards, crossing, and retreating.

• Say 'building' before changing a shared structure.
• Say 'testing' before placing weight on a new route.
• Say 'crossing' so the team knows not to modify the structure.

Give each player a clear responsibility so multiple people do not attempt incompatible actions at the same time.

• Scout: checks the route and identifies hazards.
• Builder: places and adjusts the main structure.
• Tester: observes stability and checks whether the route is ready.
• Objective player: prepares to complete the required interaction.

Complete the route one section at a time. Keep non-builders out of the active placement area and wait for a clear confirmation before moving to the next section.

• Avoid changing a structure while another player is crossing it.
• Keep at least one player in a safe position who can observe the whole route.
• Reserve resources for repairs instead of spending everything on the first attempt.

Move through the finished route in a controlled order, then complete the Crisis Job objective once the team is positioned safely.

• Send players across one at a time when stability is uncertain.
• Keep a retreat route open until the objective is complete.
• Wait for all players before triggering a coordinated action.

When a session fails, identify whether the issue is room access, platform connection, voice communication, conflicting construction, or premature movement through the route.

• If a player cannot join, have them re-enter the room code and confirm the host is still online.
• If voice communication is unclear, use short text or voice callouts and pause construction.
• If the build becomes chaotic, stop, return to safe ground, and assign one player as the primary builder.