FREE TOOL · DrawMarker & CreateCheckpoint

FiveM marker types and checkpoint types

All 44 marker types and all 50 checkpoint types, searchable, with the call written out for whatever scale, colour and flags you pick. The id is the easy part — the look comes from the twenty-three arguments after it, and those are explained below rather than left as a row of zeros.

Marker names from the FiveM docs — Markers reference (42 named, 2 listed without a name). Argument descriptions from Cfx.re natives — DRAW_MARKER. Checkpoint ids from the FiveM docs — Checkpoints reference, which gives pictures and no names — so 43 of those rows are derived from the older family table and tagged as derived.

-- MarkerTypeVerticalCylinder
-- Markers are not objects. Nothing is created and nothing persists: the call
-- paints one frame, so it belongs in a loop that runs every frame.
local ZONE = vector3(-47.8, -1757.5, 29.4)

CreateThread(function()
    while true do
        Wait(0)
        local ped = PlayerPedId()
        local dist = #(GetEntityCoords(ped) - ZONE)

        -- Stop drawing well before the marker is out of sight. Every DrawMarker
        -- in every resource is drawn every frame whether anyone can see it or
        -- not, and that is where the frames go on a busy server.
        if dist < 25.0 then
            DrawMarker(
                1,                        -- type
                ZONE.x, ZONE.y, ZONE.z - 0.95,   -- position, sunk into the road
                0.0, 0.0, 0.0,                   -- dir: zero, so rot is used
                0.0, 0.0, 0.0,              -- rot: only rotZ matters here
                1.5, 1.5, 0.5, -- scale
                255, 122, 26, 120,      -- colour and alpha
                false,                         -- bobUpAndDown
                false,                        -- faceCamera
                2,                               -- rotationOrder
                false,                      -- rotate
                nil, nil,                        -- textureDict, textureName
                false                            -- drawOnEnts
            )
        end

        if dist < 1.5 then
            -- Inside it. Show the prompt here, not a second marker.
        end
    end
end)

These are different systems and the vocabulary blurs them. A marker is drawn in the three-dimensional world, where the player walks into it. A blip is a flat icon on the minimap and the pause map, created with AddBlipForCoord and given a sprite number. Most job points need one of each: a blip so the player can find the place and a marker so they know where to stand. This site already has the sprite list, so it is not repeated here.

Each row gives the published description first and then what it means when you are trying to get a marker to look right. The direction and rotation arguments are the interesting pair: they are alternatives, not a set, and the choice is made by whether the direction vector is zero.

• typeint

  The marker type, 0 to 43.

  The list above. Everything else on this page is about the other twenty-three.

• posX, posY, posZfloat

  The position of the marker.

  The marker is drawn centred on this point, so a cylinder sunk into the road wants a Z a little under the ground rather than exactly on it.

• dirX, dirY, dirZfloat

  The direction vector for the marker, or 0.0 to use rotX/Y/Z.

  A vector the marker points along. Pass 0.0, 0.0, 0.0 and the rotation arguments are used instead — which is what almost every copied snippet does, usually without knowing there was a choice. Give it 0.0, 0.0, 1.0 and a flat marker faces straight up.

• rotX, rotY, rotZfloat

  The rotation for the marker. Only used if the direction vector is 0.0.

  Degrees. rotZ is the one you want for a chevron: it turns the arrow on the ground to point where the player should go. rotX at 90 stands a flat marker up on its edge.

• scaleX, scaleY, scaleZfloat

  The scale of the marker.

  Metres, roughly. A cylinder at 1.0, 1.0, 1.0 is about a metre across and a metre tall; most zone markers want something like 1.5, 1.5, 0.5 — wide enough to stand in, short enough to see over.

• red, green, blueint

  The colour of the marker.

  0 to 255 each.

• alphaint

  The alpha of the marker.

  0 to 255. Anything over about 150 looks like a solid object rather than a hologram; 100 to 120 is the usual compromise.

• bobUpAndDownBOOL

  Whether or not the marker should slowly animate up/down.

  The gentle float. It draws the eye, and it makes a ground zone look like it is hovering, so it suits cones and chevrons more than cylinders.

• faceCameraBOOL

  Whether the marker should be a "billboard", as in, should constantly face the camera.

  Turns the marker into a flat image that always faces you. Right for a symbol or a digit, which should be readable from anywhere. Wrong for a cylinder, which stops looking like a volume.

• rotationOrder (p19)int

  The order yaw, pitch and roll is applied. Usually 2.

  Only matters once you set more than one rotation axis. It is the argument most snippets show as a bare 2 with no comment.

• rotateBOOL

  Rotations only apply to the heading.

  With this set, the marker spins on its vertical axis. A slowly rotating ring is the standard "interact here" look; combined with faceCamera it does nothing useful.

• textureDictchar*

  A texture dictionary to draw the marker with, or NULL. Example: "GolfPutting"

  Lets a marker draw your own texture instead of the built-in shape. Pass nil for both texture arguments unless you have a streamed dictionary to point at.

• textureNamechar*

  A texture name in textureDict to draw the marker with, or NULL. Example: "PuttingMarker"

  The texture inside that dictionary.

• drawOnEntsBOOL

  Whether or not the marker should draw on intersecting entities.

  With it off, a marker is hidden by a car parked on top of it. With it on, the marker paints over the car. Neither is right in every case; false is the safer default.

The checkpoint ids changed at around game build 2189. The current reference lists them 0 to 49 as pictures with no names; the older native page describes them as families of five — a cylinder or a ring with one arrow, two arrows, three arrows, a cycling arrow or a checker pattern — but under the old numbering. Lining the two up gives an offset of 2: the old table’s two unknown slots land exactly on the two the current page marks unused, the numbered cylinder family lands exactly on the current numbered family, and the three plain cylinders at the end land exactly on the last three ids. The reference suggests subtracting three, which those three landmarks disagree with. We have gone with what the landmarks say, labelled every row derived, and left the pictures as the final word.

On checkpoint types 44, 45 and 46 the reserved argument is not reserved at all: it chooses the number drawn on the cylinder, and above 99 it also attaches one of the markers from the list at the top of this page. Everywhere else, pass 0.

• typeint

  The checkpoint type.

  The list above. Ids shifted between builds, so an id copied from a 2017 script may not be the shape you expect.

• posX1, posY1, posZ1float

  The position of the checkpoint.

• posX2, posY2, posZ2float

  The position of the next checkpoint to point to.

  This is what the arrow on an arrow-type checkpoint aims at. Pass the same coordinates as the checkpoint itself and the arrow has nothing to point at, which is why so many race scripts have a checkpoint with a jittering arrow.

• diameterfloat

  The diameter of the checkpoint.

  A diameter, not a radius — the argument markers get wrong in the other direction. 10.0 is a comfortable car-sized gate.

• red, green, blue, alphaint

  The color of the checkpoint.

  0 to 255 each. The native page does not state the ranges; they are the usual byte values.

• reservedint

  Special parameter, see below for details. Usually set to 0 in the scripts.

  Only meaningful for the numbered types, where it chooses the number and the marker drawn with it.