Test together on your home network.

Set up every test PC

1. Connect each PC to the home network. Guest Wi-Fi may prevent PCs from reaching the server.
2. Download the ZIP, right-click it and choose Extract All. Use a writable folder, such as Documents\SchemaBuilderBetaTest. Open the extracted folder.
3. Double-click Play-Test.cmd. Read the package README if Windows shows a download/script warning. The helper does not change your computer's permanent script policy.
4. Choose a unique name using 1–16 letters, numbers or underscores: TestPC1 on the first PC and TestPC2 on the second. The helper remembers your name on this PC, including across package updates.
5. Let the first setup finish. It downloads and prepares the development environment; allow several minutes, or up to an hour on a slower first setup. Later launches reuse the downloads. Internet is needed for initial setup; the game connects over your LAN.
6. On the first game launch, choose your accessibility settings and click Done. The client then attempts to join the test server directly. If you reach the menu, choose Multiplayer → Direct Connection and enter 192.168.2.149:25567.

No Microsoft passwords or account tokens are requested. This is a development test environment. The ZIP contains our original mod and setup files; it contains no Minecraft game binaries, player accounts or saved worlds.

Try a two-PC network test

1. Join both PCs at the same time. Confirm both unique names appear in the player list.
2. Stand near each other. Move and place/break a block; confirm the other PC sees each change.
3. Craft a Lookout Hut Brick and a Footbridge Brick, then throw them in an open area. Both PCs should see the same structures. The server grants the recipes automatically.
4. For the netherite golem test, ask the owner for a spawn egg. Both PCs should see it spawn and move. It should remain calm toward players until attacked.
5. Disconnect one PC, reconnect with the same test name, and confirm its inventory and position return. Use the same name again on later visits.

Players have ordinary permissions. Successful downloads and server status checks do not establish two-PC gameplay; these steps are the remaining human test.

Next launches and beta updates

Double-click Play-Test.cmd again to launch the installed test snapshot. To update this test client, download the newest beta ZIP from this page and extract it into a new folder, then use the same test name. The helper is not an automatic beta release updater. Keep the previous folder until the new version joins successfully.

If a PC cannot connect

• Connection timed out: check the home/guest network and the address, including port 25567.
• Duplicate player/name: close the duplicate client and use a different test name on each PC.
• Mod/version mismatch: use this exact beta test ZIP on all PCs. The normal beta port 25566 and stable port 25565 use their own profiles.
• Setup failed: keep the error text from the launch window and the test folder's logs. Do not copy credentials or real account profiles into this folder.

Download verification

Beta download checksum · Beta test manifest

Client ZIP SHA-256: aeaf28f18649113545b8eb5748dccc91206c1fd7baf3b92e2913ed876ecbd3d0