Secure client portal

Connect (Invite vs Direct)

Windrose Invite Code vs Direct Connect

Choose invite-code join or IP:port direct connect—and what breaks when both are misconfigured.

Windrose supports two join philosophies:

ModeHow players joinNetworking
Invite codeEnter code in clientNAT punch-through / P2P proxy path
Direct connectIP:portRequires public game port (often 7777)

Chapter22 defaults

The SteamCMD egg sets UseDirectConnection from the Use Direct Connection variable (default 0). Invite codes are the path of least resistance for new crews.

Pick one, test one

  1. Configure either invite or direct as the primary path.
  2. Restart after JSON/variable changes.
  3. Join from a second client/network before inviting everyone.


Frequently Asked Questions

Default on Chapter22?

Egg default Use Direct Connection = 0 (invite-code / P2P punch-through).

When enable direct?

When you want a stable IP:port join and have the allocation published.

Can both fight each other?

Mis-set flags/ports cause failed joins — pick one primary path and test.


Need help?

If you are stuck after following this guide, open a ticket from the Chapter22 client area with the exact error, the port or DNS change you made, and whether the service listens locally (ss / Resource Monitor) but fails externally.

Build the server. Grow the community. Start your next chapter.

Chapter22 Windrose hosting

Deploy a managed Windrose server.

Crew, Expedition, and Flagship Windrose tiers on Pterodactyl with SteamCMD eggs in Ogden, UT.