0xDocs 0x.limo

Docs / Steamworks compatibility

Limitations and test evidence

Partly live

What Steamworks compatibility on 0x does not cover yet, and how it is tested with C++ suites against the public SDK headers and with real games.

#Not covered yet

AreaStatus
Distributionsg-steamclient is not in the 0x app download (0.1.0) yet, and the app does not start Steamworks games.
Self-serve app setupAn app's stats and achievements schema, inventory item definitions and registered game-server tokens are set up by 0x with the app. There is no self-serve editor for them yet. Use LogOnAnonymous for servers.
macOSNo macOS build.
32-bit WindowsNo steamclient.dll. 64-bit only.
WindowsSee Windows below.
Steam-signed dataRelay tickets, certificates and auth tickets are signed by 0x, not by Steam. A game or server that checks Steam's own signatures itself will reject them.
Steam-only servicesRemote Play, broadcasting and video, the music player, the embedded HTML browser, the game coordinator, parental settings, and game search have no 0x counterpart. They are inert by design: they report "unavailable" exactly as Steam does in that state.
Unreliable sends on fallback pathsOver the IP (TCP) sockets and the push-stream fallback, every message is delivered reliably and in order. That is within the API contract, but it can add latency under packet loss.
OverlayThe 0x app does not draw an in-game overlay yet.
VideoNo game video is recorded, so timeline recordings and clips are always empty.

#Windows

The native steamclient64.dll is new and exercised by one real game so far. Structs that methods fill through a pointer are converted to the Windows layout where it differs. One gap remains: games built with Windows SDKs older than 1.64 receive callbacks in the 1.64 Windows layout, so a few callback fields may read wrongly in those games. Windows games under Proton or Wine use the Linux library through Proton's bridge and do not have this gap.

#Evidence

Suites. C++ test programs built against the public Steamworks SDK headers drive sg-steamclient against a fresh 0x backend, usually as two users, and most run once per SDK generation. They cover friends and presence, user, utilities, apps and DLC, cloud, Workshop, stats, achievements and leaderboards (46 checks per SDK generation), timeline, parties, input, both networking APIs (165 checks per SDK generation for ISteamNetworkingSockets), game servers and the server browser. A legacy-ABI suite calls through 12 historical SDK header generations (0.99u to 1.49) and asserts every inert-by-design value (576 checks).

Real games. Each of these runs unmodified, with its own libsteam_api, on a fresh sg-steamclient and backend:

GameEnginePathExercised
DDNetC++Linux, SDK 0.10-era libraryinit, launch command line, rich presence, join requests, two clients on a server
MindustryJava (steamworks4j)Linuxstats, achievements, lobby create, search and join, P2P world download and chat over the relay
Skillet demoGodot 4 (GodotSteam)Linux, SDK 1.65stats, an achievement, leaderboard upload with an attached replay, and a second player downloading it
PixeloramaGodot 4 (GodotSteam)Linux; Windows under Proton; Windows with 0x's own steamclient64.dllinit, four achievements earned through the game, read back by a new session
BitburnerElectron (steamworks.js)Linuxan achievement; a Steam Cloud save written by the game and imported on a second machine
SNKRXLÖVE (luasteam)Windows under Protoninit, stats, rich presence

A real game proves only the paths it exercises. The suites cover far more methods, but a passing suite is not a proof of every argument combination. If your game uses a call in an unusual way and behaves differently than on Steam, report it with the call and the arguments.