RED21 Games announced global matchmaking and parties for Murderers VS Sheriffs DUELS on November 13, 2024, describing the system as beta at that time. That official history supports playing with friends across servers, but it does not establish the current party limit, menu path, skill inputs, region behavior, or whether the beta label remains. Follow the current Lobby prompts and treat old screenshots as navigation hints only.
Before forming a party, confirm every player opened Place 12355337193 by RED21 Games. A look-alike experience cannot join the same inventory or queue.
Form the party from a clean state
Have every player leave active queues and return to the main Lobby. Open the current party or social control shown by the client, then invite one person at a time. Ask each player to confirm that the party roster appears on their screen before selecting a mode.
Choose a queue that fits the number of party members and any restrictions displayed in the live interface. The official game supports 1v1 through 4v4, but the party system may limit particular combinations. Do not infer that four members can enter every visible stand without reading the prompt.
Let the party leader select the queue once. Repeated input from several members can make it unclear which request is active. If the client names a leader, region, or readiness state, use the current label rather than an old guide term.
Confirm everyone reached the same match
After queuing, compare the mode and party roster. If one player remains in the Lobby, stop and regroup instead of playing multiple rounds while they retry alone. Confirm whether they received an error, were sent to another place, or lost connection.
The official Universe has historically exposed named places including a Pro lobby, Trading Hub, and Beginner lobby. A teleport to another place can be part of the experience rather than a separate game, but the Universe ID should remain 4348829796. Do not use this fact to invent current eligibility rules for those places.
If the match starts with the wrong mode, finish or leave according to the current client options, then reform from the Lobby. Avoid rapid repeated joins that obscure the original problem.
Troubleshoot queue and party failures
First, record the exact error text. Next, verify that every member is online, in the same target experience, out of another queue, and using a compatible Roblox client version. Leave the party, return to the Lobby, and form it once more. Then try the smallest supported queue for the current party size.
If the problem persists, change one variable: a different leader, a different Roblox server, or one fewer party member. Do not change all three simultaneously. A successful smaller party suggests a roster or queue restriction; a successful new server suggests the previous server state may have been involved.
Check Roblox platform status if multiple experiences fail to join. A local connection issue can look like a matchmaking bug. Do not share account credentials or browser session data with anyone offering to “fix” the party.
Understand what global matchmaking does not prove
The 2024 announcement said players could queue across different servers and referred to skill level. It did not publish the calculation, rating, search range, or current implementation details. Do not claim that a visible stat directly controls matchmaking unless RED21 Games or the live client says so.
A long queue does not prove your rating is unusually high or low. Queue size, party composition, server health, region, time, and an update can all affect the wait. Use observable facts: selected mode, party size, elapsed time, error, and whether solo queue succeeds.
Likewise, a difficult opponent does not prove a broken match. Review spacing and first-contact choices before assuming the matchmaker ignored a hidden rule.
Prepare the party for team play
Agree on a queue, broad lane assignments, and one short callout format before joining. In 2v2, decide who applies first pressure and who protects the exit. In 3v3, keep one flexible player. In 4v4, form pairs rather than four separate chases.
Tell teammates which abilities are equipped only if that changes the plan. Do not promise an exact cooldown from memory; current ability values belong to the live menu. Use the team modes guide for spacing and recovery after the first elimination.
If a friend is new, start with 2v2 or a short 1v1 practice instead of immediately joining the largest queue. A smaller mode gives them room to learn prompts and routes without tracking every player at once.
Report a useful bug
Include the check date, Place ID, device, Roblox client, party size, selected mode, sequence of actions, exact error, and whether solo or a different server worked. Remove private account information from screenshots. A reproducible report is more useful than “parties broken.”
Use the official links page to reach verified RED21 and Roblox destinations. Do not post authentication details in a public report.
Quick party checklist
- Confirm Place 12355337193 and RED21 Games for every member.
- Leave other queues and return to the main Lobby.
- Invite one member at a time and verify the roster.
- Select a queue compatible with the displayed party size.
- Let one leader queue once.
- If a member is left behind, record the error and reform.
- Change one troubleshooting variable per attempt.
- Keep team roles and callouts simple after joining.