FiveM postal maps: datasets, JSON checker and route setup

Check dataset structure before testing the map

Use the local Postal JSON checker above for the x, y and code structure used by the reviewed nearest-postal dataset. It rejects malformed JSON, non-numeric or non-finite coordinates, empty codes and duplicate codes after whitespace trimming. It preserves case and treats leading-zero string codes as distinct.

A passing result does not prove a point is in the right place, matches a map image or produces a useful route. Compare the selected dataset with your map version and verify representative locations on staging. Extra fields are ignored, and the checker does not alter your input or save a repaired file.

A printed postal label and a lookup dataset are different

The map image shows labels; the lookup resource associates codes with positions and selects or routes to them. An image with postal numbers does not automatically supply the data expected by a script. Check which assets and files each package includes.

Record the map author, version and numbering scheme beside the lookup resource’s revision. If the two disagree, changing the text color cannot fix the underlying location mismatch. Start with one known location and compare the visible map label with the lookup result.

Select the dataset documented for your resource

This guide reviews nearest-postal commit a0c100de02e7764bbe86ce690a9bfe2405e2841a. Its README lists new-postals.json, old-postals.json and ocrp-postals.json for three named map variants. The manifest selects new-postals.json by default through a local postalFile variable and targets GTA V.

Choose the dataset corresponding to your actual map rather than the one whose filename looks newest. Preserve the package’s existing declarations and change only what its revision-specific instructions require. The excerpt below is the selection line, not a complete replacement manifest.

local postalFile = 'new-postals.json'

Use the route command without assuming universal behavior

The reviewed README documents /postal [postalName] to set a route and /postal without an argument to remove it. It describes automatic removal near the destination. These commands belong to this resource; a different postal script may register different commands or behavior.

On staging, select a code that exists in the chosen dataset and compare the route endpoint with the intended location. Repeat from another starting point. Record whether the route points to a representative postal position or the exact entrance your roleplay scenario needs.

Diagnose the map, nearest code and route separately

Use this proposed acceptance matrix to isolate failures. Retain one location and one dataset as a baseline before changing several integrations. The checks are a test plan, not observations from a Magnate-hosted FiveM server.

Adjust the overlay without changing location data

The reviewed config.lua separates text display and position from blip settings. It exposes text.display, posX and posY as well as route-marker properties. Use the exact structure of your installed revision rather than copying a configuration block from an unrelated fork.

Test the overlay at the resolutions and HUD layouts your community actually uses. Keep the nearest-code text readable without covering navigation or other necessary controls. A layout that works in one screenshot may overlap when another HUD changes size.

If only presentation is wrong, preserve the known-good dataset while changing the display. If routing is wrong, preserve the display while inspecting data. This keeps cosmetic adjustments from obscuring the original failure.

Extend postals for custom maps with an explicit data contract

For a custom map, define the code format, coordinate source and intended representative point for each area. Check for duplicate codes and record the map revision that each dataset supports. A code name should have a documented meaning within your community.

Verify locations in the actual supported game and build before publishing a dataset as tested. Keep author credit and reuse permissions with any map artwork. Do not treat GTA V postal files as GTA VI coordinates or claim compatibility with a new world because the resource can read JSON.

Use the main FiveM maps guide for asset evaluation and the blip guide for marker configuration. Include the map version, lookup revision, selected file and one reproducible location when requesting support, without exposing private player data.

Questions, answered.