Windrose Dedicated Server Hosting on GlassHosting

Why a dedicated Windrose server

Windrose co-op on a listen host works until the host sleeps, updates mid-session, or sits behind residential CGNAT. Friends time out, progress stalls, and someone always asks whether the server is up. A dedicated Windrose instance on GlassHosting (Glass Gaming — powered by GlassHosting) stays on in a datacenter so the group can join on their own schedule.

This guide is the main-site hub for first launch: panel start, Direct Connect vs invite-code join, ServerDescription.json hygiene, and how friends connect. Deeper ticket-style how-tos live in the GlassHosting knowledgebase as articles land.

Order, then open the game panel

After checkout, open your Windrose service in panel.glasshosting.com. Note the allocated public IP and the game port shown for the service. You will share that address with friends later—do not invent a home router port forward.

New to the panel? Skim the game panel beginner guide for console, files, SFTP, and safe restarts. Background on why home hosting fails for friends: CGNAT explained and home Wi-Fi vs datacenter.

Two join modes: Direct Connect and invite code

Windrose supports two ways for friends to join. On GlassHosting, Direct Connect is the usual datacenter path because the panel already publishes a public IP and port.

Direct Connect — friends enter the panel IP and game port in the client. The published allocation must be reachable on TCP and UDP for that port (commonly 7777 when that is what the panel allocates; always use the port shown in the panel if it differs).
Invite code — friends paste a case-sensitive code (at least six characters: letters and digits) from ServerDescription.json or the console. Invite-code mode relies on NAT punch-through / UPnP on home networks; on GlassHosting you normally stay on Direct Connect instead of fighting home UPnP.

Do not mix modes in your instructions. If Direct Connect is on, share IP:port. If you switch to invite-code mode in the panel startup settings, share the invite code and confirm the mode after a clean restart.

Configure ServerDescription.json before first start

Windrose stores day-one community settings in ServerDescription.json under the server data path (panel File Manager or SFTP). Common knobs:

InviteCode — at least six alphanumeric characters, case-sensitive. Set a memorable private code if you use invite-code mode; leave mode and sharing consistent.
IsPasswordProtected — optional extra password layer; share passwords off public Discord channels.
MaxPlayerCount — keep within your plan and what your group actually needs on day one (smaller peaks are easier to smoke-test).
UseDirectConnection / Direct Connect — when enabled (GlassHosting default path), friends join with panel IP:port; when disabled, expect invite-code join instead.
DirectConnectionServerPort — must match the port the panel allocates when Direct Connect is on. The panel allocation is the source of truth—do not hard-code a home default if the allocation differs.

Stop the server cleanly before editing config files, save, then Start again so changes take effect. Treat invite codes and passwords like any other shared secret.

Ports Windrose actually uses

In Direct Connect mode, Windrose expects the published game port open for TCP and UDP. On GlassHosting you do not configure home router forwarding—the datacenter path already publishes the allocation. Share the panel IP and port exactly as listed.

If friends still cannot join, verify the console shows the world loaded, that they used Direct Connect (not a stale invite code) or the correct invite code for your mode, and that you did not paste a home LAN address. Related join walkthrough: how friends join with IP:port.

Start clean and watch the console

Click Start in the panel.
Watch the console until the dedicated process finishes loading and reports it is ready.
Do not invite the full group while the process is still installing or mid-boot.

If boot fails, stop, re-check Direct Connect / invite settings and the published port, and start again. Avoid rapid restart loops that interrupt saves. After a first provision, if the console never reaches a healthy ready state, open a ticket before wiping the world.

How friends join

Friends need a matching Windrose client build. Depending on your mode:

Direct Connect: panel public IP + game port (and password if you enabled one).
Invite code: Play → Connect to server → paste the case-sensitive code from ServerDescription.json or the console.

Have one trusted friend smoke-test before you announce to everyone. Confirm they load into the correct world and that movement/combat feels normal. If only some players fail, compare client versions and whether they used the same join mode you documented.

World saves, mods, and backups

World and config files live under the server data path. Before mods, map experiments, or major config changes:

Stop the server cleanly from the panel so saves flush.
Create a named panel backup, or download the data folders via File Manager or SFTP.
Add content only with packs your group agrees on; keep client and server content matched when the game requires it.
Start once, watch the console for errors, then invite one tester before the whole group.

Named backups beat “I think there was an auto copy.” Related habit: backups before mods. Panel-level file tips: SFTP workflow.

Private co-op checklist

Join mode chosen on purpose (Direct Connect or invite code—not mixed instructions)
Invite code / password shared off public channels
One friend join smoke-test before group announce
Named backup before updates or content drops
Console clean on boot (no repeated crash loops)
Join info is panel IP + port (Direct Connect) or the current invite code—not a home LAN address

Related guides

MSP note

GlassHosting runs Windrose as always-on Glass Gaming capacity—panel control, datacenter connectivity, and backup hygiene—not a PC that sleeps after work. Order or manage plans at billing.glasshosting.com; operate day-to-day at panel.glasshosting.com.