Troubleshoot

Check the server status above first — if Velocity or the specific server shows offline, it's a server-side issue, not you. Give it a few minutes and try again. If it's been down longer than 15 minutes, check the Discord — the host usually posts when something's being worked on.

BillySMP runs on the latest release. If you're getting a version mismatch error, update your client. If you're on a older launcher, switch to the official one or make sure you're launching the right version. Snapshots won't work.

Double-check that you've entered the port (19132) in the port field — it's a separate box from the address. On console, you might need to use a DNS workaround to add external servers; the BillySMP Discord has a pinned guide for this. If the Bedrock section on the status page is showing offline, the Geyser bridge may be down temporarily.

billysmp.ddns.net is a dynamic DNS name. Occasionally DNS propagation has a lag — try flushing your DNS cache. On Windows: open Command Prompt and run ipconfig /flushdns. On Mac: sudo dscacheutil -flushcache. Then try reconnecting. If the site itself loads fine but the game server doesn't resolve, it may be a DDNS hiccup — check back in a few minutes.

There’s no whitelist — anyone can connect. If you’re getting kicked immediately, it’s more likely a version mismatch (make sure you’re on 26.2+) or a brief server hiccup rather than an access issue. Once you’re in, you’ll land in the Lobby in adventure mode. Unverified players can’t actually do anything — to play for real, you need to get verified. Verification puts you in survival mode, gives you a verified badge on the community board, and gets you more trust with staff. Head to the Discord to get verified.

Run the latency test above to get a baseline. Under 80ms is solid, 80–200ms is playable but noticeable, above 200ms will feel rough. If your latency looks fine here but the game still lags, it's more likely a server-side TPS issue — post in Discord so staff can check. If your latency is high, there's not much to do besides trying at a different time of day.

The status monitor reads from the bot's process log, not a live TCP probe. It's possible for the process to appear running while the server is in a crash loop or restarting. Check the freshness indicator above — if status data is stale (more than 2 minutes old), the bot itself may be having trouble. Otherwise, try connecting again in 30–60 seconds; it might be mid-restart.

Check the status grid above — if BeamMP shows offline, the server is down. If it shows online, try refreshing the in-game server list (it can take a minute to populate). You can also use Direct Connect with billysmp.ddns.net:48900. Make sure your BeamMP Launcher is up to date and you're signed in.

Vehicle sync is heavily latency-sensitive. Run the ping test above — anything above 150ms will cause visible desyncs. Try deleting and respawning your vehicle, or using "Reset Vehicle" in-game. If it affects everyone, it's usually a server hiccup; give it a minute or rejoin.

Check the status grid above first. The server uses Steam's server browser (Valve's API) — there's no port or direct connect involved. In-game, go to Multiplayer → Servers and search for BillySMP-Stormworks Edition. If the server doesn't appear, try refreshing the list. Also check your Stormworks version matches the server.

Large vehicles with lots of logic blocks are CPU-intensive for both the server and all clients. The BillySMP Stormworks server runs on a dedicated core slice to avoid starving the Minecraft servers, so there's a ceiling on how much it can absorb at once. Try reducing your vehicle's complexity or spawning fewer at a time.