-
Enter your invite code in the box below.
-
Enter a display name in the box below.
-
Pick your team.
-
Pick which radio's setup steps to show first.
This only picks which instructions show below -- it does not limit which radios you can register. Run both kinds? Pick either one now and add the other afterward from the setup-check panel at the bottom of this page, any time you like.
Meshtastic registration isn't open yet. Once it is, it works the same way MeshCore's does here -- register, then add your node ID.
This does NOT replace MeshMapper. Your coverage data, points and leaderboard standing there are unaffected. MeshWars receives a copy.
Matched against the mwmesh.com directory this board already uses to resolve check-ins. Don't see your node?
Looks like
cddb2304.Optional -- you can register with no node picked at all and add one (or several) afterward from the setup-check panel further down this page, or just start a wardriving session and let it self-bind on first contact.
Don't see your node?
Looks like
!a1b2c3d4— find it in the Meshtastic app.Meshtastic node IDs can change; the key is what lets us keep following your radio when one does.
Optional here -- you can register with no radio at all and add this (or several) afterward from the setup-check panel further down this page. See the steps below for the radio settings that make sure MeshWars can actually see you.
-
Click Join.
-
Copy your API key now — this is the only time it will ever be shown.
You're already registered — this key is only for coming back later, to add or change radios or check your setup.
Closing or reloading this page loses it for good. MeshWars stores only a one-way hash of your key, never the key itself, so there is no way for anyone, including an admin, to look it back up. The only fix for a lost key is a brand new one from an admin, which retires this one. Copy it somewhere safe before you do anything else.Your key will appear here once you join.
-
Open MeshMapper, then Settings, then scroll to API Endpoints.
-
Toggle Custom API Endpoint on.
-
Paste this as the URL.
Do not paste the meshmapper:// link into the URL field. It is not a web address. It is only for Import from Clipboard. -
Paste your API key into the API Key field.
Your key will appear here once you join.
-
Save.
-
In the same API section, make sure Include Contact Key is on.
-
Start a wardriving session — nothing is sent without one.
-
Carrying a second radio, MeshCore or Meshtastic? The setup-check panel further down this page is also where you go to add or remove radios later, any time, not only to check on things.
-
In the Meshtastic app, under Radio Configuration → LoRa, turn on OK to MQTT. Without it no gateway will forward your packets and MeshWars will never see you.
-
Under Radio Configuration → Position, make sure GPS is enabled and your node is broadcasting its position.
-
Under Channels, on your primary channel, set position precision to full. If it is reduced, your position gets rounded off and you will paint the wrong square, or none at all.
-
Make sure you are on FREQ51, so a gateway that feeds meshview can actually hear you.
MeshMapper sends a batch every fifteen to thirty seconds while a wardriving session is running. Nothing is sent between sessions.
Squares are only claimed where your radio hears a repeater. Driving through an area with no mesh coverage logs your position and claims nothing — that is normal, not a fault.
To check, paste your API key into the setup check at the bottom of this page. It will tell you when MeshWars last heard from you and what is wrong if anything is.
Lost your key? It's still sitting in MeshMapper — open Settings, then API Endpoints, and read it back out of the API Key field.
Nothing is pushed to MeshWars at all. MeshWars polls meshview every 45 seconds and picks you up whenever your node broadcasts a position that a feeder hears — there is no session to start or batch to send.
Squares are only claimed where a feeder hears your node's position. If you're somewhere with no feeder coverage, your position is never reported to meshview in the first place, so nothing gets claimed — that is normal, not a fault.
To check, paste your API key into the setup check at the bottom of this page. It will tell you when MeshWars last picked up your node from meshview, how many squares you hold, and what is wrong if anything is.
Lost your key? Nothing on a Meshtastic radio or in the Meshtastic app ever stores it — ask an operator for a new one.
Paste your API key below to check your setup, add another radio to your account, or remove one — any time, not just once at signup.
Paste your API key to see whether MeshWars is receiving anything from your app. Lost it? It's saved in MeshMapper under Settings → API Endpoints → API Key.
Paste your API key to see when MeshWars last picked up your node from meshview, how many squares you hold, and what is wrong if anything is — nothing is sent to us directly. Lost it? Nothing on your radio ever stored it — ask an operator for a new one.
Advanced: MeshCore check-in name isn't matching?
Most players never need this. It only matters if your net check-ins aren't being credited because your radio's public key isn't yet in the mwmesh.com directory MeshWars checks first. If your contact already resolves there, setting a name here does nothing for you.
Type the exact name your radio posts under in the weekly-net channel (matching ignores case, nothing else).
MeshWars is currently scoped for the western US and Texas. If you'd like to join the fun or need help, please reach out to malice in the Intermountain Mesh Discord.
The outline is the live play area, read from the server — pings outside it are not scored. Open the board.