The Bornless error codes and crash fixes
Every error, crash and connection failure we have a fix for, one page per code. Before the fix, each page says whether the problem is your machine or the studio's servers — because if it's theirs, no amount of verifying game files will help, and the only useful answer is whether it's happening right now.
Things you can fix
Crashes, install faults and driver conflicts. Find your symptom, work the steps in order, stop when it launches.
None yet — The Bornless isn't playable yet. This page fills in automatically once real players hit real codes.
Things you cannot
Queues, capacity limits and login failures. These are server-side — every page below links back to live status rather than a fix you can perform yourself.
The Bornless "servers offline" between test windows (fix)
The Bornless disappears from your Steam library, won't launch, or throws a generic launch error, even though it worked during a previous test — and no patch or update is showing.
The Bornless "AuthenticateUserTicket error" — access ended (fix)
Launching shows "Steam API AuthenticateUserTicket error response: ('response': ('error'…)" or leaves you stuck at the main lobby screen instead of loading in, right after previously being able to play.
The Bornless "no license found" launch error (fix)
Clicking Play immediately shows "an error occurred whilst launching the game — no license found," with no other explanation, even though the game launched fine earlier the same event.
How these are graded
Every fix step carries a label. Confirmed means players demonstrably got back in with it, or the studio said so directly.Reported means it worked for some people and not others. Unconfirmed means it's circulating and there's no evidence either way yet. The distinction is the point — a page that lists five fixes with equal confidence costs you an evening.