Introduction

Introduction

ATY Map Editor is an in-game map editor for FiveM. You fly around your server, place things, and the result is a map that stays on the server, survives restarts, and can be exported as a real, startable resource.

It places three kinds of entity, not one:

Type	Catalogue	What you can set
Objects	15,946 props, indexed and searchable	position, rotation, scale, freeze, collision, alpha, LOD, door mode, light source
Vehicles	843 models	full paint and modification set, plate, tint, dirt, doors, engine, locked, invincible
Peds	830 models, including animals	idle pose or scenario, invincible, non-reactive

Most editors stop at props. If you want a parked car outside your new building or a bouncer at the door, you normally reach for a second script and a second config file. Here they are the same tool, the same gizmo, the same layer list, the same export.

What the editor is for

• Building interiors, exteriors and props into your map without leaving the game
• Dressing scenes with vehicles and people so a location looks lived-in
• Producing a .ymap you can ship as a normal streamed resource
• Removing default GTA V world props that get in the way of your build

What makes it different

The map is not stored in the editor. Placements live on the server and are pushed to each player as they join. Restart the server, crash it, or stop the editor resource entirely — the props stay where you put them.

The export is a resource, not a text file. YMAP export writes a manifest and a stream/ folder with streaming extents calculated from real model bounds, so the map actually streams in game. See Export.

Everything works on a selection. Box-select fifty props and offset, align, distribute, mirror, rotate, scale or re-layer all of them in one action — and one undo step.

Areas are shapes you draw. Click corners around the region you want and fill it or clear it. Not a bounding box around your shape — the shape itself.

Requirements

• aty_lib
• ox_lib
• setr game_enableDynamicDoorCreation "true" in server.cfg

Works on ESX, QBCore and standalone servers. See Installation.

Where to start

1. Installation — files, dependencies, start order
2. Permissions — who can open the editor
3. The editor — freecam, cursor, tabs, HUD
4. Placing objects — your first prop

If the editor opens but says you have no permission, go straight to Permissions — the server console prints the exact fix.