1. Check compatibility
Start the 2-minute check. Your game needs working multiplayer and a Linux x86-64 server program that runs without a window. We host your server; we do not create multiplayer or host the separate player client.
2. Build the server
Keep the server build separate from the game your players install. Use the guide for Unity, Godot, or Unreal. For Node.js or Python, package your server and Linux dependencies with the approved local tooling described below.
3. Test two players
Run your server locally and prove that two players can connect and see each other's actions. Keep the test output. A running process or an open port does not prove multiplayer works.
Check existing server
Check these requirements before requesting changes. Ask your developer or AI to identify evidence for each:
- Configurable port: the connection number can be supplied through settings rather than edited in code.
- Health check: a small request confirms the server is ready. Describe its protocol, port and expected answer.
- Clean stop: the server saves state and exits when told to stop.
- Game-level join check: a small client or request verifies that the game accepts a player; an open port alone is insufficient.
Optional prompt for your developer or AI
Inspect my existing multiplayer server without changing files. Do not add another dedicated-server mode or replace networking that already works.
Report its engine, Linux x86-64 build/start command, configurable port, health check, clean save/stop handling and game-level join check. For each, give file/line evidence or say unknown. Do not print secrets.
List missing requirements separately from unknown requirements. Explain how to test each. Propose only the missing changes and wait for my review before editing. Do not upload, install an unverified tool or contact hosting services.
4. Check and package locally
The ncg tool is not publicly distributed yet. There is no public download or package to install today. Do not install a similarly named package. You can complete the build and two-player test above while waiting.
If you already have an authorized NetCraftGames source checkout
This is the supported source-checkout route, not an instruction to obtain private source. Install Node.js 24.14.1 or later in the supported Node 24 line. In that checkout, install the locked dependencies, then use the included launcher:
npm ci
node cli/ncg.mjs --help
node cli/ncg.mjs init /absolute/path/to/your-server-build --out /absolute/path/to/your-server-build/ncg.json
node cli/ncg.mjs check /absolute/path/to/your-server-build --manifest /absolute/path/to/your-server-build/ncg.json
node cli/ncg.mjs pack /absolute/path/to/your-server-build
Run these commands from the NetCraftGames checkout, replacing the example path with your server build folder. After init, open the generated ncg.json and resolve every TODO(ncg) before running check. check reads locally and uploads nothing; pack creates an archive locally. Review --help and the checkout's CLI documentation for your engine before packaging. Node/Python dependency installation during packaging is a separate local operation and may download packages. These commands do not submit a build or start a server.
5. Submit after launch
Submissions and paid hosting are unavailable today. Keep your tested build and settings. Join the waitlist for opening information or read launch status. Once available, the intended sequence is upload, review detected settings, check the release, publish, start the server, then test and share connection details with players.