PolyZone FiveM: create zones, export code and fix imports

What does createzone do on a FiveM server?

A command name only has the behavior implemented by the resource that registers it. If a tutorial tells you to use /createzone, identify that resource and its version before copying arguments. A hint in chat is not a universal FiveM specification.

PolyZone’s own wiki documents /pzcreate {poly,box,circle} [options]. It prompts for missing details and previews the zone for editing. This guide follows that workflow rather than attributing an unrelated command to PolyZone.

Create and export a zone on staging

The reviewed wiki documents /pzadd and /pzundo for polygon points, /pzfinish to serialize the result into polyzone_created_zones.txt in the resource root, and /pzcancel to stop creation. It also describes /pzlast for reusing the last finished box or circle at a new position.

Choose a meaningful name and record the intended behavior before drawing. A garage interaction, a shop entrance and an entire property boundary may need different geometry. Verify the generated shape against the specific area rather than selecting a large zone simply because it is easier to draw.

Exported code is not automatically a complete gameplay feature. Place it in the owning resource according to that resource’s integration contract and attach the intended behavior. Keep the original output and any edits so you can reproduce how the final boundary was created.

Import the zone classes your script actually uses

The README reviewed at commit 0f9003080706d61ff29b9b3db5332d407632d4df requires importing PolyZone’s client.lua before using its base class. Additional classes need explicit imports in the documented order; for example, BoxZone depends on the base class and EntityZone depends on BoxZone.

The excerpt below supplies the base and box classes before your own client file. It is not a full resource manifest. Match file paths and resource names to your actual installation and retain any other declarations your resource requires.

client_scripts {
    '@PolyZone/client.lua',
    '@PolyZone/BoxZone.lua',
    'client.lua'
}

A drawn boundary is not the same as a working interaction

Test the geometry independently from the action it enables. First establish where the player is considered inside or outside. Then test whether the intended menu, target option or gameplay handler follows that state. A visible debug shape only proves the drawing path.

Use the matrix below as a proposed acceptance plan. It does not report a PolyZone runtime test by Magnate. Keep the map version, zone output and owning resource revision with the observations.

Diagnose nil classes, wrong heights and awkward boundaries

For a nil class during creation, inspect the imports and their order before changing coordinates. The upstream README specifically identifies missing dependencies between zone classes as a possible cause. Confirm which resource owns the failing code and which manifest loads it.

For a shape at the wrong height, compare the generated vertical settings with the actual floor. For an irregular polygon, inspect the recorded point order and the intended edge path. Avoid changing geometry and gameplay permissions simultaneously, since that makes the original failure harder to isolate.

If the shape is correct but an action is missing, trace the consumer’s event or target integration. A working zone does not establish job authorization, inventory access or server-side validation for the action. Keep those checks in the appropriate authoritative component.

Keep zone generation separate from deployment

Preserve the generated definition in version control with the owning feature and describe why the boundary exists. Recheck the zone after an interior or entrance changes. A valid old coordinate set can describe the wrong area after a map update.

Use the qb-target and Ox Target guides for their respective target integrations; do not assume they accept identical option schemas. This guide does not establish GTA VI compatibility or run creator commands against a live community server.

Questions, answered.