We Were Here Tomorrow Reddit: What Players Say

The most common post type is a looking-for-group request, and they arrive in several languages: English, Italian, Spanish and Chinese appear in the same week. One player wrote that they bought the game that day and could not find a single player who had not already started.

That is a structural problem for a two-player game with no friend pass and no friend-list invite. The official route is a public lobby, the Steam forum or the Discord, and none of those guarantee a partner who stays for a full run.

If you are reading this before buying, plan the partner first. The game is excellent with someone who talks; it is unplayable with a lobby that empties at the first puzzle.

The most quoted complaint is that there is no saved progress per player. One post puts it plainly: you find a partner, they stop playing, you find another, and you start over from the beginning with the new person.

This is the same structural issue as the friend pass gap, seen from the other side. A forced co-op game with host-based progress punishes anyone whose schedule does not match their partner's.

The practical advice from the community is to finish a run with one person or accept that a swap costs you the chapter. There is no account-level checkpoint to hand over.

The PS5 microphone problem has a community solution: quit and close the PS5 Discord application, which appears to hold the microphone and stop the game's voice chat from working. That fix is not in the official known-issues list.

Environment loading is the second cluster, with screenshots of floors, walls and terrain popping in and out while walking. Patch 1.1.2 addressed world content failing to load, so much of this should be historical.

Other reports include a crash during shader compilation that stalls at 16%, achievements not granting for two players at once, and motion sickness from head bob with no obvious setting to disable it.

The positive posts praise atmosphere, music and pacing. One player at 40% after three hours called it a great pace; another said they loved the vibes and the aesthetics but found the puzzles extremely easy early on and hoped for harder ones later.

The negative posts are about being lost rather than bored. One thread on the cable routing puzzle admits the pair solved the first part randomly without understanding the mechanics, which is exactly the gap a rules-first guide fills.

That split is consistent with the review data: the design lands, the signposting does not, and the same puzzle can read as too easy or too obtuse depending on the pair.

It also explains why the two complaints appear in the same thread. A pair who brute-force a room with four inputs feel clever for ten minutes and then hit the next room with no method, which is where the "too hard" posts come from.

The developer posts directly in the subreddit, including the patch announcement. Patch 1.1.2 opened with an apology to everyone affected by the bugs and the unexpected voice server outage, then listed more than twenty fixes.

Checking complaints against that list is the most useful thing this page can do. Environment loading, the disappearing walkie-talkie, inventory locks after emotes and checkpoint black screens are all addressed; Chapter 7 checkpoint problems and the power-network achievement are not.

Any thread you find from launch week should be read with that list beside it, or you will spend an evening applying a workaround for a bug that no longer exists.

The pattern is worth internalising for future launches: the subreddit is fastest at diagnosing a new bug and slowest at retiring one. Official patch notes are the opposite. Read both, and date everything.

The r/Games announcement thread exists and appears in search, but Reddit's anti-scraping response blocked the body, so we can confirm the thread and not its contents. We do not quote comments we could not read.

Subscriber counts and daily activity are also unavailable to us, so this page does not print a member number. A figure without a source would age badly and mislead.

Post timestamps in this snapshot run from October 20 to October 26, 2026. If you are reading later, assume the specific threads are gone and the themes have shifted, and check the official known-issues page before acting on any workaround described here.

Three post types tell you more than any review. The first is the partner-search post that never got a reply, which is the clearest signal that the lobby experience depends on you bringing someone.

The second is the "solved it randomly" post on a routing puzzle. It describes a pair who beat a puzzle without understanding it and then could not repeat the logic, which is the exact failure mode a rules-first guide is written for.

The third is the fix thread where a player solves a problem the studio had not documented, such as the PS5 Discord microphone conflict. Those threads are the reason community pages are worth reading at all, even when the official notes are more authoritative.

Sort by new rather than by top. The useful posts here are hours old, and the highest-voted ones are usually screenshots of a bug that has already been patched.