Free Windrose tool
Windrose Multiplayer Issue Router
Pick the symptom your crew can actually see, then jump to the guide that matches it. Route hidden servers, stuck loading, failed joins, timeouts, strict NAT suspicions, crashes, version mismatch, disconnects, and high-ping reports without guessing ports.
9
symptom routes
4
routing inputs
0
login gates
Multiplayer issue router
Pick the failing symptom
Four routing inputs
Symptom
Join starts but loading never finishes
The observed failure decides the first guide.
Setup
Friend invite or hosted session
Invite, self-hosted, and dedicated paths should stay separate.
Party
2-4 player baseline
Large crews should not be the first troubleshooting benchmark.
Evidence
Some players checked, not all
Current-build evidence is safer than old reports.
Recommended next guide
52
issue pressure score
Collect evidence before changing setup
The issue can be network-feeling, update-related, or host-related. Record the exact failure moment and change one variable at a time.
Route to
Stuck on Joining Server Guide
Record join source, loading point, party size, host signal, and the one variable changed.
Do not start here
Avoid exact ports, provider steps, commands, config paths, or driver fixes until the symptom points there and a current-build test confirms it.
Keep every test small, dated, and tied to one changed variable.
Multiplayer Not Working
Stuck on Joining
Dedicated Server Not Working
Tool note
This router points to the safest next guide. It does not diagnose exact server ports, provider steps, driver fixes, or config paths. Those details need current-build verification.
If the game closes or freezes while joining, treat it as a crash report before changing network settings.