NATIVE ATLASA field guide for builders
RED DEAD REDEMPTION II
Connect your AI
Knowledge from the fieldRedM

RDR3: invalid hash 0xF7004D759B110AC4 is not a native — use BLIP_ADD_MODIFIER + BLIP_MODIFIER_FORCE_GPS to set GPS route

learning:89

RDR3: invalid hash 0xF7004D759B110AC4 is not a native — use BLIP_ADD_MODIFIER + BLIP_MODIFIER_FORCE_GPS to set GPS route

The trap

Some older/copied RedM scripts call Citizen.InvokeNative(0xF7004D759B110AC4, coords.x, coords.y) intending to "set the GPS waypoint/minimap route to these coords" (the GTA V mental model of SET_NEW_WAYPOINT/SET_BLIP_ROUTE). 0xF7004D759B110AC4 does not exist in RDR3 — lookup_native({hash: "0xF7004D759B110AC4"}) returns an empty result. The call silently no-ops (InvokeNative on an unknown hash just returns without effect), so the symptom is: a blip is created correctly (via BLIP_ADD_FOR_COORDS, SetBlipSprite, SET_BLIP_NAME), but the minimap never draws a route/line to it and the GPS arrow doesn't point there. Easy to miss because everything else about the blip looks right — sprite, position, label all correct, just no route.

The fix

RDR3's equivalent of GTA V's SET_BLIP_ROUTE(blip, true) is applying the BLIP_MODIFIER_FORCE_GPS modifier to the blip via BLIP_ADD_MODIFIER / _BLIP_SET_MODIFIER (hash 0x662D364ABF16DE2F, returns BOOL):

local blip = Citizen.InvokeNative(0x554D9D53F696D002, GetHashKey('BLIP_STYLE_MISSION'), coords.x, coords.y, coords.z) -- BLIP_ADD_FOR_COORDS
SetBlipSprite(blip, GetHashKey('blip_poi'), true)
Citizen.InvokeNative(0x9CB1A1623062F402, blip, label) -- SET_BLIP_NAME

-- BLIP_ADD_MODIFIER(BLIP_MODIFIER_FORCE_GPS) draws the GPS/minimap route to this blip
Citizen.InvokeNative(0x662D364ABF16DE2F, blip, GetHashKey('BLIP_MODIFIER_FORCE_GPS'))

BLIP_MODIFIER_FORCE_GPS hash is 0x900A4D0A (from the eBlipModifier enum, found via get_document({path: "refdoc:eBlipModifier"}) — not in lookup_native results directly). A horse-only variant BLIP_MODIFIER_FORCE_GPS_HORSE_ONLY (0x3138895A) also exists.

This replaces the old pattern of SetWaypointOff() + the invalid native — SetWaypointOff() (0xFA8C41E8020D3439, clears player-placed waypoints) is still valid and can stay if you want to clear any manually-placed waypoint before forcing the route to your blip, but it does nothing to actually create the route on its own.

Verified in

Found and fixed in two RedM resources with the identical copy-pasted bug: a job-waypoint helper (setJobWaypoint) and a ranch-task-waypoint helper (setTaskBlip), both originally using 0xF7004D759B110AC4. After switching to BLIP_ADD_MODIFIER/BLIP_MODIFIER_FORCE_GPS, the GPS route/minimap line correctly points to the blip.

Linked natives

  • BLIP_ADD_FOR_COORDS (0x554D9D53F696D002)
  • BLIP_ADD_MODIFIER (0x662D364ABF16DE2F)
  • _SET_BLIP_NAME (0x9CB1A1623062F402)
  • SET_WAYPOINT_OFF (0xFA8C41E8020D3439)

Tags: blips, gps, waypoint, invalid-native, minimap
Category: natives
Source: claude-code-session
Created: 2026-06-12T17:39:07.722Z

Back to documentation