Murderers VS Sheriffs DUELS Prototype Map Guide

Prototype was officially introduced by RED21 Games in the July 8, 2023 Murderers VS Sheriffs DUELS update. Its historical name and release are confirmed; its exact current lanes, cover, spawn positions, and rotation status are not frozen by that announcement. Verify the map inside the official Place ID 12355337193 before following any route.

Use Prototype to practice route-tree thinking: from each safe observation point, decide which branch follows each piece of information. This avoids a memorized path that fails when an opponent or update changes the situation.

Confirm Prototype before mapping it

Write down the visible map label, date, queue size, spawn side, and selection method. Compare the live scene with any older video or community diagram. If they differ, the live official experience controls the session.

Begin with neutral callouts such as spawn cover, first observation, near branch, far branch, central contact, and safe return. Only name a physical object when it actually exists and everyone can recognize it. Do not infer laboratory, platform, corridor, or other geometry from the title “Prototype.”

Observe both perspectives over multiple rounds. Mark uncertain cover or collision as a test, not a fact.

Create the first observation node

Find the nearest position that lets you learn something without giving up all cover. The goal is not necessarily to see the opponent; it is to determine whether a line is occupied, whether a push is early, or whether a route remains open.

At that node, pre-aim the expected opening and define three branches. Hold when the opponent commits into your prepared line. Return when the line is already controlled against you. Advance when current information and ability state make the next cover reachable.

The node fails if all three choices require the same exposed movement. Move it closer to safety or use a different initial route.

Build a route tree

Map no more than two decisions ahead. A simple tree is easier to execute: spawn to observation, then observation to pressure, alternate line, or retreat. For each edge, record the visible risk, destination cover, and cancel condition.

Do not add a branch simply because movement is possible. It must answer a likely opponent action. If the opponent disappears, return to the last known safe node instead of chasing through several unverified branches.

Test one branch across multiple rounds with varied timing. When the opponent adapts, note which observation revealed the adaptation. That observation becomes more valuable than the route itself.

Use Prototype in 1v1

In the first round, stop at the observation node and measure first contact. In the second, keep the route but change timing. In the third, choose the alternate branch only after the opponent supplies the trigger you defined.

Avoid autopilot loops. If both players circle through repeating routes, break contact at a known safe point and re-acquire information. A missed attack should lead to a planned return or new branch, not an immediate repeat peek from the same place.

Review the first irreversible decision after each loss. It may be advancing with no destination cover, treating a guessed location as confirmed, or spending an ability before deciding how to use its result.

Assign branches in team modes

Give each player a responsibility tied to a branch rather than telling everyone to “push.” One watches the first-contact line, one covers the likely opponent return, and one remains flexible in larger teams. In 2v2, each player needs a separate angle plus a short path to support the other.

Communicate observation and direction: target seen, branch taken, time observed. Do not treat a previous call as permanent. When information becomes old, say that it is lost.

Avoid stacking on the observation node. If one teammate already uses it, take the supporting line or wait for space. Crowding can block vision, movement, and ability landings.

Test abilities as branch tools

Use Dash only after the destination branch is verified. Compare the normal and assisted crossing for exposure, arrival control, and remaining cooldown. Use Propeller with a visible landing and a path out.

Use Shroud to choose between defined branches rather than activating it with no question. If its current result shows one line occupied, the response might be hold, rotate, or support a teammate. Verify live duration and behavior.

Treat Soul Reap according to current trigger and combat rules. Official history shows ability tuning has changed, so historical costs and effects require live checks.

Prototype route card

Run a five-round experiment

Round one identifies the first node. Round two repeats it with a timing change. Round three uses the advance branch only on its trigger. Round four tests one ability as a branch tool. Round five counters the opponent’s most repeated response.

Afterward, keep only observations that were clear and repeatable. Mark one-time collision behavior, unclear audio, or uncertain routes for retesting. Separate tactical failure from mechanical failure so the next practice has one objective.

Prototype mistakes to avoid

• Guessing layout features from the map name.
• Copying a 2023 path without checking current geometry.
• Building a long route with no decision nodes or cancel conditions.
• Treating an old sighting as the opponent’s current position.
• Advancing because an ability is available rather than because information supports it.
• Putting multiple teammates on one observation point.
• Changing route, timing, and ability together so the result cannot be explained.
• Presenting a community callout or current-pool claim as official.

Return to the Maps hub for the universal scan and compare Ridge for angle-height practice. Prototype notes should remain short, current, and tied to decisions a player can actually repeat.

Sources checked

• RED21 Games MVSD patch notes
• Official Roblox experience
• MVSD community Maps page