Windrose Tutorial Required for Multiplayer: Silent Kick Fix
One of the most frustrating Windrose connection failures at Early Access launch is also one of the least obvious. You spin up a dedicated server, hand the invite code to a friend, and they type it in. Windrose thinks for a second, the join attempt fails, and they get no meaningful error message. The host sees nothing abnormal on their side either. The game behaves as if the server simply is not there, or as if the invite code is wrong, or as if the network path is blocked. In almost every community thread about this symptom, the first response is to suspect DNS, firewall, or ISP interference. Those are real problems, but they are not the full story. A large share of the "player cannot join" reports since the April 14, 2026 launch actually come from a completely different cause: one player in the crew has not yet completed the singleplayer tutorial. That single missing step silently gates them out of every multiplayer mode, including dedicated servers, with no clear in-game notification that the tutorial is the problem.
This is a hosting-critical issue because no amount of port tuning, router configuration, or backend fiddling will ever fix it. The server is healthy. The invite code is correct. The network is clean. The friend's account simply has not crossed the gate that Windrose uses to decide whether it is safe to throw a real player into a shared world. Until the developers change the behavior or add a clearer warning, the only durable fix is knowing the rule and applying it before everyone sits down to play. The goal of this guide is to document the gate, show how to detect it, and explain how to avoid having a crew's entire session ruined by something that nobody thinks to check.
Why this matters for hosting
If a brand-new Windrose player joins your dedicated server without ever finishing the singleplayer tutorial, the game will reject their connection silently. The host-side logs and the player-side UI will look normal. There is no "you must complete the tutorial" error.
Why the tutorial is really a gate
The singleplayer tutorial in Windrose is framed as a learning experience. You create a character, pick a starting archetype, go through the initial story beats, learn basic movement, learn the crafting and survival loops, and eventually progress far enough that the game "unlocks" the rest of its modes. In most survival games that gate either does not exist at all or is cosmetic. In Windrose it is functional. Until the tutorial is marked as complete, the player's profile sits in a state where it cannot participate in multiplayer sessions. Discord and Steam reports from the first 48 hours of Early Access describe exactly this: players installing the game, launching it for the first time, and bouncing straight into "Join a Game" using an invite code. The attempt fails with no explanation. Once the same player clears the singleplayer prologue, the invite code works first try. Nothing about the server changed between attempts.
From the developer's perspective this probably exists to prevent brand-new accounts from joining at character zero without any of the progression or item assumptions the world expects. From the player's perspective it looks like a broken server. Both perspectives are accurate. The gate is real, it is enforced, and it is currently not being surfaced to the player in the form of a readable error message.
Symptom checklist
| Observation | Tutorial-gate fingerprint |
|---|---|
| First-time launch, immediate multiplayer attempt | Very high likelihood |
| Host is on the main menu, another friend joins fine, one person fails | Characteristic — that one person skipped the tutorial |
| The failing player has the Windrose icon for the first time | Very likely |
| Other network-dependent games (Steam downloads, voice, Steam friends list) work fine | Consistent — network is healthy |
| Same failing player succeeds after about 30–60 minutes of unrelated "trying fixes" | Often — because they ran the tutorial in between without realizing it was the fix |
| Invite code works the instant they reach the tutorial's "you can now play multiplayer" moment | Definitive |
How to quickly tell whether the tutorial gate is the cause
There is no log line to check and the game does not emit a useful error. The fastest diagnostic is behavioral: ask the failing player how long they have had Windrose installed, whether the first session was a straight attempt at multiplayer, and whether they ever created a singleplayer character and walked through the opening story beats. If the answer is "I just installed it twenty minutes ago and went right to 'Join,'" you are almost certainly seeing the gate. If the answer is "I have played solo for a few hours and I can join some servers but not yours," something else is wrong and you should move on to the standard connection troubleshooting steps covered in the host/join error guide.
Good test: have the failing player return to the main menu, start a new singleplayer game, and play until the game explicitly drops them out of the tutorial experience. Then retry the invite code. If it works first try, that was the gate. If it still fails, move on to DNS, firewall, or version checks.
Why "just finish the tutorial" is harder than it sounds
There are a few reasons the fix is not as obvious as it seems:
- The tutorial takes a meaningful amount of real time. Players who were expecting to immediately join their friends feel like the game is wasting them.
- Some players interpret the tutorial as skippable UI instruction and expect to be able to quit it and go to multiplayer anyway.
- The gate is invisible. Nothing in the join error tells the player they are gated.
- The failing player usually blames the host, the ISP, or the server. They spend time changing settings that were never broken.
- The host usually blames their server configuration and spends time tweaking invite codes, restart flows, and port behavior that were never broken either.
The end result is a crew that loses an entire evening of play to a gate that is not even a real bug in the hosting layer.
What a host should do about it
Short of upstream changes, the highest-leverage thing a host can do is make the rule visible before people sit down to play. Paste the rule into the crew's planning chat. Put it on the Discord server's pinned welcome message. Put it into the Windrose FAQ section of whatever private wiki your crew uses. Put it on the invite code message so everyone hears it at least once.
A short, copy-pasteable version you can use:
Windrose multiplayer note:
Before you try the invite code, finish the singleplayer tutorial at least once.
The game does NOT show an error if you skip it.
Tutorial takes roughly 15-30 minutes.
Then come back and join us.That one paragraph, shared in advance, prevents more "server broken" tickets than any actual server-side tuning.
What a dedicated-server operator can do about it
You cannot disable the gate from the server side. Windrose enforces it client-side per account. That means your options are:
- Make the tutorial requirement visible in your server description, panel page, or welcome message.
- If you run a managed service, surface this rule in the hosting FAQ so customers do not open support tickets for something the server cannot fix.
- If you operate a panel, consider adding a lightweight knowledge-base card with the copy-pasteable snippet above, positioned next to the invite code display.
If you are a host running Windrose for paying customers on Supercraft, this matters operationally. Customers will open support tickets that look like "my server is broken" when the actual problem is a tutorial gate on their friend's account. Making the rule visible in-panel pays for itself.
Differentiating this from other "silent" join failures
It is worth calling out that a silent connection failure in Windrose can also be caused by:
- The host not being fully inside the world yet when someone tries to join (brief race condition after a restart).
- One side loading the save in Solo or Offline instead of Host a Game.
- ISP-side blocking of the coordination domain (
windrose.support) or port 3478. - A NAT configuration that prevents the dynamic punch-through from completing.
- A mismatched client and server version after a hotfix.
Each of those has its own triage path. The tutorial gate is distinct because the host is completely healthy and the other players can join fine. If only one person in a crew cannot join, that is a strong fingerprint for the gate. If everyone fails simultaneously, you are probably looking at one of the other classes and should consult the ISP/DNS/port-3478 guide or the version mismatch after Steam auto-update guide.
Why this is likely to get better in future patches
The developers have explicitly acknowledged on Discord that most bug reports they have been receiving are connection-related. That category almost certainly includes a large share of tutorial-gate complaints misfiled as "can't connect." Because the fix on the developer side is conceptually small — either surface a clear error message, let the player choose to skip the gate, or auto-complete the tutorial when they accept an invite — it is very plausible that one of these will land within a few hotfixes of launch. Until that happens, the most efficient thing a crew or hosting operator can do is share the rule in writing before the first play session.
Decision flow
| Scenario | Next step |
|---|---|
| Brand-new player cannot join, everyone else can | Ask them to complete the singleplayer tutorial, then retry |
| Everyone in the crew fails simultaneously | Move to DNS, firewall, ISP, or version-mismatch checks |
| One player could join yesterday and cannot today | Check for a hotfix both sides may not have applied yet |
| Invite code works for a new throwaway world but not the main one | Suspect the world save's state, not the account |
| The failing player has never launched Windrose before this session | Assume tutorial gate by default and retry only after they finish it |
Does the tutorial really block multiplayer?
Yes. Until the singleplayer tutorial has been completed at least once on a player's account, joining multiplayer reliably fails with no specific error message.
Will my dedicated server log the tutorial failure?
Usually no. The rejection happens in a way that does not surface a clear reason on the server side. The server looks healthy and the invite code looks valid.
How long does the tutorial take?
Most players report 15–30 minutes. Some skip dialog faster. The important thing is reaching the point where the game marks the tutorial as complete.
Can I disable this gate on my own server?
No. It is enforced on the client. Server operators cannot turn it off.
Is there a workaround for very quick drop-in play?
Not yet. The only currently reliable workaround is making sure every participating account has finished the tutorial at least once.
Want an easier Windrose hosting experience? Windrose server hosting on Supercraft surfaces the invite code cleanly and keeps restart and backup flows simple so your crew can focus on the real gate — the tutorial — rather than fighting the server.