Feedback and Discord

Send playtest feedback to the studio Discord first. Both the 10 November and the 12 November 2026 posts say that is the best place, and that a dedicated playtest section is there. If you do not want Discord, the 12 November post says to use their feedback form or the bug and feedback subforums on the Steam community hub. Pick one channel and include what they asked for. Do not scatter the same crash across all three and call it triple confirmation.

What to include

The post is specific about desync and bad spawns. For desync, say whether the host and the client disagree about the terrain or about objects on the terrain, such as stones, and admit when you cannot tell. For a Väsen who spawns in a strange place, attach a screenshot of the location and a screenshot of the map view. For a failed join, say that you could not connect, and say whether a solo launch worked. Known issues is the menu of bugs they already expect, so you can name the bullet instead of writing a novel.

For a save that lost character textures, say that you quit during a save, if that is what happened. That pairing is how they described the bug. Saves is the habit that avoids a second report.

Cuts are not bugs. Missing befriending, a stop before Birch Trees, and absent stations are listed as playtest limits on playtest. You can still say you missed them. Mark the note as a request for Early Access, not as a broken install. The 14 October post says they want to build the game with players through Early Access and beyond. A clear request helps. A duplicate of their own cut list does not.

Where the links live

The Discord invite printed on the news posts is the one on official links. The Trollheim site, X, TikTok and Instagram are the social row on those same posts. The Steam community hub for app 4139890 is the place those bug subforums live. This wiki's own contact address, on terms, is for corrections to the guide, not for build crashes. The studio will not see a note that only reaches the fan site.

The NDA is not a reason to stay quiet anymore. It covered the closed test. The 12 November post lifted it. You may talk about the game and file bugs in public channels. You still should not present a theory as a studio statement. Updates is for what they actually posted.

A useful report

1. Build context: open playtest, Windows, solo or host plus a number of clients.
2. What you did, and what the host saw versus what the client saw.
3. The two screenshots if a Väsen spawned wrong.
4. Whether a clean save still works.

That is enough. Then go back to the shelter. Beginner guide is a better use of the rest of the night than a second essay.

Tip: Discord first, one report per bug, screenshots for bad spawns, and a clear note when you are asking for a cut feature rather than reporting a break.

FAQ