Windrose Ports Explained (Direct Connect)

For Direct Connect, Windrose uses the egg’s primary allocation as DirectConnectionServerPort. On Chapter22’s game node this is commonly in the 7777+ range (allocations 7777–7790 observed free on the Windrose-capable node — always copy your panel value).

Port table

Service	Port	Protocol	Public?
Direct Connect game port	Panel allocation (often 7777)	TCP + UDP	Yes when Direct Connect enabled
Invite-code path	No fixed public forward	Punch-through	N/A — use invite code

Managed hosting (Chapter22)

In Pterodactyl, copy the primary allocation IP:port.
Enable Direct Connect (guide).
Confirm R5/ServerDescription.json shows the same port.
Share IP:port with players.

Verified 2026-09-26 against egg id 33 config (DirectConnectionServerPort ← server.build.default.port) and panel allocations including 7777.

DIY / self-hosted readers

DIY VPS readers enabling Direct Connect should allow the chosen game port TCP+UDP in OS + provider firewalls. Invite-only setups skip fixed forwards but still need outbound connectivity.

Invite-only reminder

If UseDirectConnection is 0, do not troubleshoot “closed 7777” as the first step — fix invite code / party flow first.

Frequently Asked Questions

What port does Chapter22 use?

The egg writes DirectConnectionServerPort from the primary Pterodactyl allocation. Nodes have 7777+ allocations available — check your panel IP:port.

Invite mode needs 7777?

Invite-code join relies on punch-through; direct mode needs the public allocation.

TCP and UDP?

Open both on the allocated game port for Direct Connect.

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.