FiveM MLO Floor Plans: Playtesting Queues, Sightlines and Staff Routes

A hospital reception can look excellent in a screenshot and fail as soon as two patients arrive together. One blocks the treatment-room door, another stands inside the interaction point, and the receptionist cannot see either of them from the chair. The interior loaded correctly. Its layout still needs a playtest.

Floor-plan testing asks whether people can perform the scenes you want inside a building. It complements collision, lighting and performance checks. Run it with the actual interactions and a few volunteer players, using a short set of repeatable scenarios rather than an unstructured tour.

Describe three scenes before counting rooms

Choose the building’s ordinary activity, its busiest credible activity and one awkward exception. For a small clinic, those might be a walk-in consultation, two simultaneous admissions, and a patient brought through the wrong entrance. A restaurant might test one order, a queue at closing time and a delivery arriving during service.

Write the participants and their destinations in each scene. That gives every room a job. A consultation room needs space for the patient, clinician and any intended companion, plus a workable route between the door and treatment position. An attractive office nobody has a reason to enter adds little to that scene.

Use the number of people your server can reasonably gather. Designing every venue around a packed launch event may leave ordinary evenings feeling empty. You can stage an occasional large event somewhere else without making the everyday venue enormous.

Draw the routes on a simple plan

A rough annotated screenshot is enough. Mark public entry, service counter, waiting space, staff space and exit. Draw the path a new visitor is likely to take before showing them the intended route. If those paths differ, you have useful information about the entrance or signage.

Repeat the drawing for staff. Can a worker reach supplies without walking through the queue? Can a second employee pass behind the counter while the first uses an interaction? If the path crosses a treatment scene or interview every time someone fetches equipment, the layout creates interruptions that no decorative prop will solve.

Then draw any delivery route. A back entrance only helps when the vehicle approach, unloading point and storage location form a usable connection. Test the actual handoff rather than giving the door credit merely for existing.

Queue where the camera can see the service

Place one player at the counter and others in the likely waiting positions. Have them look towards the service point using normal gameplay camera positions. Check whether they can see when it becomes their turn and whether the waiting space obstructs people entering or leaving.

Try standing, sitting and turning. A reception desk that frames a cinematic shot may obscure the person speaking from an ordinary third-person view. Furniture can also place the player’s camera against a wall. The practical test is a conversation played in normal conditions, not a carefully selected camera angle.

Do not assume you need more floor area when the real issue is a misplaced queue. Moving a bench or shifting an interaction point may free the main route. Use permitted configurable furniture options where available; confirm what the asset actually allows before planning structural changes.

Distinguish visible privacy from audible privacy

Stand one player inside an interview or consultation room and another outside. Check views through windows, open doors and corridors. Then test conversation with your actual voice setup. A closed-looking room should not be assumed to provide the intended voice isolation simply because its walls are visually solid.

Record visual and audio results separately. This makes the eventual fix easier to assign: furniture placement, room layout, door behavior and voice configuration may belong to different systems or creators. Our guide to MLO rooms and portals covers the separate problem of an interior drawing incorrectly.

For the floor-plan review, focus on what participants experience. Can a visitor accidentally see the entire interview from the public counter? Does a busy corridor encourage constant interruptions? A scene that needs privacy should not depend on everyone politely avoiding the most obvious waiting spot.

Test interaction space with the real resources

Install the intended target zones, menus and door configuration in a test environment. Walk towards each interaction from more than one direction. Check whether two nearby targets are difficult to distinguish, whether a menu opens from the wrong side of a counter, and whether standing at one workstation blocks another.

An MLO does not guarantee compatibility with a particular job workflow. Cfx.re’s resource manifest documentation explains how resource files and data are declared; it does not establish that your treatment, stockroom or billing interactions are positioned correctly. Those remain installation decisions to verify.

Keep a record of the coordinates and approach used for each failure. A note saying that the counter is awkward becomes actionable when it says the stock target captures attention while facing the till from the customer side. Give the person fixing it a position and a direction to reproduce.

Walk the inconvenient routes too

Test a player arriving through the secondary entrance, leaving while another enters, or returning to collect something after the main interaction. Where your gameplay supports carrying, escorting or stretchers, use those mechanics during the test. Extra participants and attached objects can expose constraints a solo walkthrough misses.

If movement stops unexpectedly, separate a narrow design from a collision defect. The CodeWalker project documentation identifies YBN data with collision bounds and describes its world inspection tools. That gives a mapper a route into investigation; it does not make every obstruction a file you should edit yourself.

Ask the creator to investigate defects in protected or licensed assets through their supported process. Your strongest evidence is a short clip with the route, the installed version and a clear statement of where movement should have continued.

Give each finding a practical decision

Sort the results into launch blockers, configuration changes and preferences. An exit players cannot use is a blocker. A counter target needing relocation is a configuration task. A preference for a different wall colour should not consume the meeting while everyone remains trapped in reception.

Assign a person to each necessary change and repeat the affected scene afterwards. Avoid approving the building on a list of promises. The corrected queue must work with players occupying it, and the relocated interaction must work from its intended side.

Keep the three scenarios as a small regression check for later updates. A replacement desk or new door can change circulation even when the building itself stays the same. A successful floor plan gives visitors a readable route, staff room to work and scenes space to continue without constant negotiation over who is standing in the doorway.

Blog