Agentstrap Docs

Matchmaker

Join a place automatically the moment Roblox starts, optionally picking a server that isn't already full.

The matchmaker is Agentstrap's most automation-heavy feature. Once it's enabled and you give it a place, every time Roblox launches it immediately joins that place — and if you'd rather not land in a packed server, it can look for one with room first.

Where it lives. Settings → Deployment → Matchmaker. It is off by default.

Options

OptionDefaultWhat it does
Enable matchmaker Off Join the place below as soon as Roblox starts. Leaving this off means the place ID is ignored.
Place ID Empty The experience to join. Accepts a raw numeric place ID, or a full link such as https://www.roblox.com/games/123456789/Whatever — the ID is pulled out of the link for you. Leave it empty to pick a place at launch time instead.
Prefer low population servers On Skip full servers even when the list still has slots. This avoids long queue times on popular games. When it's on, Agentstrap picks the server with the fewest players; when it's off, it picks the busiest one that still satisfies your minimum.
Minimum free slots 1 How many free slots a server needs before the matchmaker will join it. Offered values are 1, 2, 3, 5 and 10. Values outside 1–50 are clamped.

Finding a server right now

The Find a server now button does the whole thing immediately, without waiting for the next launch. It:

  1. Saves your settings first, so the search uses exactly what you see on screen.
  2. Queries Roblox's public server list for the place, following at most three pages of results. The search is deliberately bounded so a single request can never churn through the entire server list.
  3. Keeps only servers where MaxPlayers - Playing >= Minimum free slots.
  4. Sorts by your preference: fewest players first when Prefer low population servers is on (ties broken by the larger server), most players first when it's off (ties broken by the most free slots).
  5. Launches Roblox with a deep link that joins that exact server.
Roblox doesn't report back. After the matchmaker asks Roblox to join a server, Roblox doesn't tell Agentstrap whether the join actually worked. The status line tells you what was requested, not what happened.

Status messages

The card under the matchmaker options tells you what the last action did:

MessageMeaning
Enter an experience ID or link, then find a public server.Nothing has been attempted yet.
Enable Agentstrap Matchmaker before searching for servers.You pressed search with the feature off.
Enter a valid Roblox place ID or a roblox.com/games/{id} link.The place field couldn't be parsed.
No public server found with at least {n} open slot(s). Try a lower minimum or search again later.The search ran but nothing qualified.
Launch requested for a server with {playing}/{max} players.Roblox was asked to join a specific server.
Server search failed: {message}Roblox's API returned an error or was unreachable.

Configuration migration

If you enabled the matchmaker in an older build but never set a place ID, Agentstrap's configuration migration turns the matchmaker off for you rather than leaving it in a state where every launch does nothing. The Updates page will show this as a pending migration you can apply.

Old key names. The matchmaker settings are stored in Settings.json under the keys VoidstrapMatchmakerEnabled, VoidstrapMatchmakerPlaceId, VoidstrapMatchmakerPreferLowPopulation and VoidstrapMatchmakerMinimumFreeSlots. The names are legacy but are kept for compatibility with existing installations.

Agentstrap 2.11.4 · These docs describe Agentstrap 2.11.4. Features marked new are not present in upstream Bloxstrap.