- We Were Here Tomorrow puzzles split information between two players in separated areas of the Norček Industries facility.
- Communication is the core mechanic: describe exactly what you see, then confirm before entering anything.
- Use a hint ladder: no-spoiler hint first, partial hint second, full solution only as a last resort.
- Simultaneous mechanisms need an agreed countdown and action order before either player acts.
- A reset usually means wrong order or timing, not a broken puzzle — verify and retry.
How We Were Here Tomorrow Puzzles Work
Every puzzle in We Were Here Tomorrow is built on the same principle: the two players receive complementary views instead of identical control panels. One player typically holds the clue — a symbol, a sequence, or an instruction visible only from their side — while the other player has access to the mechanism that consumes that information. Progress depends on translating observations into a shared vocabulary and executing the correct interaction in the correct order.
Released on October 20, 2026 for Steam, PlayStation 5, and Xbox Series X|S with cross-platform co-op, the game continues the series' signature asymmetric design inside a mysterious Antarctic facility run by Norček Industries. Puzzles are generally grouped into a few recognizable categories:
| Puzzle Type | What Happens | Communication Demand | Difficulty |
|---|---|---|---|
| Symbol translation | One player reads symbols, the other enters them | High — exact descriptions required | ★★★☆☆ |
| Environmental clues | Room layout, signage, or objects encode the answer | Medium — describe landmarks precisely | ★★★☆☆ |
| Synchronized mechanisms | Both players activate linked controls together | High — countdown and order needed | ★★★★☆ |
| Multi-stage locks | Several smaller steps feed one final input | Very high — note-taking recommended | ★★★★★ |
Agree on short labels for colors, shapes, directions, and numbered positions during the opening area. Teams that build this vocabulary early solve later puzzles significantly faster than teams that improvise descriptions every time.
Communication Setup That Prevents Most Stalls
Most puzzle stalls are not logic failures — they are description failures. A working microphone is strongly recommended because clues and mechanisms are split between players, and the game assumes continuous voice contact through its walkie-talkie framing.
Describe, Don't Interpret
- Report what is visible: color, orientation, position
- Mention surrounding landmarks
- Let your partner draw conclusions
Fix a Reading Order
- Always read left-to-right or top-to-bottom
- Number positions aloud ("first, second, third")
- Never skip repeating the sequence back
Assign Roles by Access
- Clue holder guides, operator inputs
- Avoid swapping control mid-puzzle
- Operator confirms each input before committing
Words like "the arrow thing" or "the weird symbol" cause most failed attempts. If your partner cannot identify the object you mean within a few seconds, describe its position, color, and what surrounds it instead of repeating the same vague label louder.
Step-by-Step Puzzle Solving Method
Follow this three-step method on every mechanism in the facility. It works because it mirrors how the game splits information between the two players.
Identify the information split
Before touching a mechanism, both players state what they can see and what is hidden from them. Do not assume a symbol visible to one player is visible to the other — the game deliberately hides complementary details across rooms and viewpoints.
Match symbols, positions, and sequences
Use your shared vocabulary to translate the clue into an ordered input. Read the relevant symbols in a fixed direction, repeat the full sequence back for confirmation, and only then let the player with mechanism access enter it.
Synchronize the final interaction
For linked mechanisms, agree on a countdown and an action order, activate the controls together, and observe the environmental change. Continue only after both players confirm the new route or mechanism is actually available.
Treat a reset as feedback, not failure. Check whether both players acted in the agreed order, whether the timing window was met, and whether any symbol was misread. Correct one variable at a time so you know which fix worked.
Recovering From a Stalled Puzzle
When progress stops completely, return to the last confirmed state instead of guessing randomly. The checklist below covers the most common missed steps, ordered by how often they resolve a stall:
Stall Recovery Checklist:
- Re-check both players' rooms and all reachable objects
- Confirm every symbol was described using the agreed vocabulary
- Verify the reading direction and sequence order before retrying
- Check whether a simultaneous action needed a countdown
- Look for an unexamined clue, document, or environmental detail
| Symptom | Likely Cause | Fix |
|---|---|---|
| Mechanism accepts input but nothing happens | Wrong sequence order | Re-read symbols in fixed direction, repeat back |
| Mechanism resets immediately | Broken timing window | Use a countdown, retry together |
| Partner can't find the described object | Vague description | State position, color, and landmarks |
| No mechanism responds at all | Earlier step incomplete | Search both areas for missed clues |
| Similar symbols confused repeatedly | No shared labels | Assign short names ("double-line", "hook") |
Multi-stage puzzles in the Norček facility can chain several symbol groups into one final input. Keeping brief written notes on repeated symbols prevents re-describing the same details across multiple attempts.
Co-op Habits That Make Puzzles Easier
Beyond individual solutions, teams that finish the campaign smoothly share a few habits. These apply from the opening area through the final coordinated sequence, and they matter more than raw puzzle-solving speed.
| Habit | Why It Matters | When to Apply |
|---|---|---|
| Confirm before entering | Prevents wasted attempts on long sequences | Every input step |
| One speaker at a time | Avoids overlapping descriptions | During any symbol reading |
| Report results immediately | Operator feedback closes the loop fast | After every interaction |
| Explore before acting | Surfaces hidden clues early | Each new room |
| Stay patient on retries | Resets are feedback, not punishment | Any failed attempt |
The game supports cross-platform play across Steam, PlayStation 5, and Xbox Series X|S, so you can pair with a partner on a different platform — but both players need a working microphone and the same game version. Verify both before inviting, per the official store and We Were Here games site.
FAQ
Q: Do We Were Here Tomorrow puzzles require voice communication?
Voice communication is strongly recommended. Clues and mechanisms are deliberately split between the two players, so continuous verbal description is the intended way to transfer information. Text chat workarounds exist but make timed and synchronized puzzles much harder.
Q: Can I solve the puzzles solo with two accounts?
The puzzles in We Were Here Tomorrow are designed around asymmetric information between two humans. Running two accounts alone is technically possible for some sections but significantly slower, and synchronized mechanisms become very difficult to coordinate alone.
Q: What should I do first when a new puzzle room opens?
Before interacting with anything, both players should describe everything visible in their own area — symbols, controls, documents, and layout. Identifying the information split first prevents wasted attempts on wrong assumptions.
Q: Why does a mechanism keep resetting?
A reset almost always means the input order, the timing window, or a described symbol was wrong — not that the puzzle is broken. Return to the last confirmed state, verify the sequence with your partner, and retry one change at a time.