Project Intel NPC — Talk to ANY Ped. They Remember. They Gossip. They Snitch.

Installation

1. Install and start ox_lib 3.x.
2. Copy lastresort_intel_npc into the resources directory. Do not rename it.
3. Add this after its dependencies and any optional LastResort resources in server.cfg:

set onesync on
ensure ox_lib
ensure lastresort_intel_npc

Do not also ensure lastresort_npc_chat — see step 6.

3 — Restart and read the console

Expected server-console output on a clean boot:

[lastresort_intel_npc bridge] server: framework=qbox inventory=ox notify=simpleasf target=ox

The client prints its own [lastresort_intel_npc bridge] client: ... line in F8. The framework= / inventory= / notify= / target= values are what auto-detection picked — if one is wrong for your stack, force it in Config.bridge (shared/config.lua).

The loaded with N static persona(s) line only prints when the verbose convar in step 4 is on — it goes through the operator-log gate, not print.

If you have edited data/personas.lua, watch F8 for a yellow line like persona "your_persona_id" declares gta_voice_name "...", which is not a real GTA ambient voice. It is exactly the check that caught Maggie's voice name in this release. That check runs on every boot: a voice name GTA does not have makes the NPC permanently mute with nothing else to explain it, so the persona falls back to Config.default_gta_voice_name and tells you. Fix the name, or set Config.validate_persona_voices = false to silence the check.

4 — Debug / verbose convars (optional)

Dev tooling (F12 dev menu, /intel_dev, all /intel_* test commands, 3D overlays, map blips) is gated behind Config.debug, which ships on so a fresh install can be driven immediately. Turn it off for production with setr lastresort_intel_npc:debug 0, which overrides the config file.

The 3D surfaces above every NPC's head are the exception: Config.debug_3d_mode ships 'off', so a fresh install has nothing floating over pedestrians. Set it to 'basic' or 'full' when you need it, pick the mode in-game from F12 → Modules → Above heads, or set setr lastresort_intel_npc:debug 1, which switches it to 'basic'. The same section carries the other two over-head surfaces, both also off by default: the coloured status dot (Config.mood_icon_enabled — talk / busy / hostile within 18 m) and the name above an NPC (Config.show_npc_name_tooltip, which draws only while the 3D overlay is off). All three are session-only from the panel — it never writes your config file. F12 is also Steam's default screenshot key — if you launch FiveM through Steam, either change the overlay bind, rebind the dev menu in Settings → Key Bindings → FiveM, or set Config.dev_menu_key. Control both from server.cfg without editing files — use setr so clients receive them:

setr lastresort_intel_npc:debug 1                  # 1 = dev tools on, 0 = force production
setr lastresort_intel_npc:verbose_server_log 1     # operator-facing console diagnostics

Both accept 1/true to force on and 0/false to force off; leave them out entirely to use whatever shared/config.lua says. A fresh install ships production-safe, so only add these on a dev/test server.

Who may use the dev tools — grant the ace (v1.46.0)

Config.debug is a feature switch, not a permission check. Two dev events reach the server (the police master toggle and the test-weapon give), and they are gated behind an ace. Nobody holds it by default, so an unconfigured server is closed rather than open:

add_ace group.admin lastresort_intel_npc.dev allow

The server console always holds it, which is what txAdmin and rcon use, so you can drive the dev tools from the console without granting anything. If a player fires a dev event without the ace the server refuses it and prints who tried. Before v1.46.0 these were gated on Config.debug alone — which ships on — so any connected client could flip the police system server-wide.

5 — Discord logging (optional, but read this if you use it)

Webhook URLs are read from the server convars first and from shared/config.lua second — both work. Prefer the convar: shared/config.lua ships to every client that connects, and any player who reads a URL there can spam or delete your channel.

Turn the module on in the config:

-- shared/config.lua
Config.discord = {
    enabled = true,
    ...
}

…and put the URLs in server.cfg:

# default channel — used by any category without its own override
set lastresort_intel_npc:discord_webhook        "https://discord.com/api/webhooks/1234/abcd"

# optional per-category channels: money, police, shop, npc, admin
set lastresort_intel_npc:discord_webhook:money  "https://discord.com/api/webhooks/1235/efgh"
set lastresort_intel_npc:discord_webhook:police "https://discord.com/api/webhooks/1236/ijkl"
set lastresort_intel_npc:discord_webhook:shop   "https://discord.com/api/webhooks/1237/mnop"

If your URLs are already in Config.discord.webhook / .webhooks, they keep working — the server just prints one line at boot pointing at the convar.

Per-event toggles live in Config.discord.events; red-light/speeding triggers and witness alerts default off because they are high volume.

5.1 — Language (optional)

-- shared/config.lua
Config.locale = 'auto'   -- 'auto' | 'en' | 'hu' | …; shipped packs: 'en', 'hu'

'auto' picks the language itself: the lr:locale convar first — setr lr:locale hu in server.cfg sets every LastResort resource at once — then locale / ox:locale / esx:locale / txAdmin-locale, then the player's own GTA language on the client, then English. Only a code with a pack in locales/ counts. The server console prints [lastresort_intel_npc] locale: hu (lr:locale convar) once at boot so you can see what it chose. Set a code instead of 'auto' to pin one.

Every player-facing line — menus, the dialogue panel, NPC hails, refusals, kick lines, the police scenes — comes from locales/<code>.lua. Add your own by copying locales/en.lua to locales/xx.lua, renaming the Locales['en'] table to Locales['xx'] and translating the values; keys you leave out fall back to English. Restart the resource to pick a new file up. See "Language packs" in README.md.

5.2 — SQL persistence (optional)

NPC memory, reputation, quests, errand runs, the bounty board and bribe history default to FiveM's KVP store, which needs no setup but never appears in a MySQL backup. To move them into your database:

-- shared/config.lua
Config.persistence = {
    backend      = 'sql',
    table_prefix = 'lastresort_intel_npc_',
}

Restart the resource. With oxmysql running it applies sql/lastresort_intel_npc.sql itself and prints:

[lastresort_intel_npc persistence] SQL backend active (tables `lastresort_intel_npc_*`)

Nothing to import by hand. If you would rather run the file yourself, replace its {{prefix}} token with your configured prefix first. If oxmysql is not running the resource says so in one line and keeps using KVP — it never fails to start over this, and oxmysql is not a dependency.

Older installs may still have a lastresort_intel_npc_ai_memory table from a previous version. It is no longer created or read; leaving it in place breaks nothing, and you can drop it when you want the space back.

5.3 — City life layer (optional, life points are ON)

Config.life_points ships enabled since v1.11.0. It spawns ambient scenario peds — sunbathers, bench sitters, someone at the ATM, and the night-only red_light_district preset that gives the prostitute hail lines and the street service flow someone to work with. These are real peds on top of R*'s ambient population, so:

• Config.life_points.max_active (default 12) is the hard ceiling across every preset. On a server that is already heavy, drop it to 6 and watch resmon.
• Config.life_points.enabled = false removes the whole layer.
• Config.life_points.presets_enabled switches presets off one at a time — e.g. red_light_district = false if you do not want the red-light posts.
• Config.life_points.furniture.enabled = false drops only the four furniture_* presets that sit peds on ATMs, benches, meters and bus stops. It does not touch the red-light preset.

The other four city-life modules — Config.scenario_groups, Config.world_ambience, Config.street_scenes and Config.paired_scenes — all ship on as well.

5.4 — Street scenes (ships ON)

Config.street_scenes.enabled = true by default. The peds already standing on the pavement around you start having authored conversations with each other — real GTA ambient speech in their own voices, the resource's normal bubbles over their heads, and a prompt to cut in and open the dialogue panel on whoever you interrupted.

Nothing here spawns anyone. The module borrows peds out of the population you already have and hands every one of them back, so it does not move your ped budget at all.

• Config.street_scenes.presets_enabled switches whole groups off in one line — street_talk, corner, cops.
• chance (default 0.25) and scan_interval_ms (default 20000) control how often a scene is even attempted; global_cooldown_ms is the floor between two of them.
• interject_prompt is 'help' (the game's help box), 'text3d' (floating text) or 'none'. interject_control defaults to 51 — INPUT_CONTEXT, E — change it if E is already spoken for on your server.
• bubbles = false keeps the audio and the gossip and drops the subtitles.
• The seven shipped scripts and the full entry schema are in data/street_scenes.lua.

While it is off there is one sleeping interval thread and nothing else: no peds touched, no natives called.

5.5 — Paired interactions (ships ON)

Config.paired_scenes.enabled = true by default. A greeting from an NPC who trusts you becomes an actual handshake, a familiar gang contact gets a dap, and giving an item, bribing or tipping becomes a real hand-over.

It is a cosmetic and it never changes an interaction outcome. The dialogue panel opens either way — after the handshake when there was one, immediately when the scene was refused or degraded.

• trust_tier_min per scene is the gate — trusted for the handshake, familiar plus the gang category for the dap, neutral for the hand-over. ambient_tier_thresholds is where an ordinary pedestrian's tier comes from.
• networked = false (the default) means only the player who triggered the scene sees the two peds animate. Set it to true if you want other players in range to see it, at the cost of a network scene per interaction.
• player_in_scene = false keeps your own ped out of the animation entirely — use it if handing the player's ped over for ~2 seconds is unacceptable on your server.
• dev_target_range (12 m) and dev_target_min_dot (0.5, ~60°) decide which ped /intel_paired acts on — the same forward-cone search quick-talk uses, not a hairline camera ray. Widen them if the dev command keeps answering no ped in front of you on a ped standing slightly off-centre.
• scenes.hug_flavour.enabled ships false on purpose.

While it is off there is one sleeping 120 s cooldown sweep and nothing else: IntelNpcPaired_Try answers false immediately and every call site keeps its current behaviour.

5.6 — Spoken dialogue panel (ships ON)

Config.dialogue_speech.enabled = true by default. Every line the dialogue panel types is paired with a tone-matched GTA ambient bark in the NPC's voice, with the typewriter finishing when the audio does.

Listen to it before you go live. The written line is yours and translated; the bark is a canned English pedestrian line that has nothing to do with the text. On an immersive or non-English server that mismatch may read worse than silence — enabled = false turns it off, sync_typewriter = false keeps the audio but unhooks the typewriter from it.

• Config.dialogue_speech.sync_typewriter = false keeps the audio but stops it driving the typing.
• Config.dialogue_speech.tone_contexts remaps any line tone to a different speech context.
• The full key table is in the README under "Spoken dialogue — voice casting & speech sync".

While it is off there are no timers and no natives called — the panel behaves exactly as it did in v1.11.0. Config.validate_persona_voices is a separate switch and still runs.

5.7 — Vehicle collision (ships ON, new in v1.19.0)

Config.vehicle_collision.enabled = true by default. It does two things while you are driving, and nothing at all while you are not:

• Below lethal_kmh (35) a pedestrian or a car occupant you hit is floored at survive_floor health (110) rather than dying, and GTA's critical-damage multiplier is removed from anyone inside radius of your moving vehicle. Above lethal_kmh impacts stay lethal.
• Contact is detected with IS_ENTITY_TOUCHING_ENTITY rather than from a health drop, so a ped reacts to being nudged even when completely unhurt — and a driver reacts when you tap their car, which never fired before.

Worth knowing before you ship it:

• The softening is borrowed. Peds near your car are measurably harder to one-shot for as long as you are driving past them, and it is handed back the moment they leave the radius, you leave the driver's seat, or the resource stops. GTA exposes no getter for that flag, so the restore writes the engine default (true), not the ped's prior value — if another resource had deliberately set it to false on a ped, this hands it back as true.
• It does not touch the wanted level. A nudge and a bump never make you wanted; a hit is reported by client/police.lua and only when Config.police_system_enabled is on. The victim's reaction fires either way.
• It needs no other module. With police off — the default — being run over now produces a reaction, which it previously did not.
• enabled = false restores vanilla GTA collision exactly. Nothing else in the resource depends on it.

If you are upgrading and had tuned Config.police_ped_hit.protect_nearby_peds, note that it never ran: nothing has read it since v1.17.0. Its replacement is this block, and this one is on.

5.8 — Keys worth reviewing after install (v1.16.0)

Three new config surfaces ship on by default, and they are on whether or not you copy the blocks across. If you keep a heavily customised shared/config.lua and paste nothing, the built-in fallbacks are the new defaults, not the pre-v1.16.0 tuning — concretely: the non-lethal police band is active at zero and one star (lethal force starts at two), the anti-repeat line picker is active, and ambient, dialogue and life-point peds run on GTA's own reaction defaults. Upgrade the Lua and the config together.

If you want a genuinely no-behaviour-change upgrade, the minimal paste is:

Config.police_nonlethal = { enabled = false }
Config.line_no_repeat_depth = 0
Config.native_ped_behaviour = {
    enabled = false,
    disable_shocking_events = true,
    clear_flee_attributes = true,
    brave_disable_bullet_reactions = true,
    combat_disable_bullet_reactions = true,
    dialogue_flee_lock = true,
    dialogue_bullet_lock = true,
    life_point_block_events = true,
    life_point_never_flee = true,
    life_point_disable_explosion_reactions = true,
    life_point_suffers_critical_hits = false,
    life_point_alertness = 0,
}

Config.native_ped_behaviour — leave it alone to get GTA's native pedestrian behaviour. Every key inside names its native default if you want to re-enable the old tuning. It only ever suppresses overrides on peds the engine owns; peds this resource spawns (static personas, life points, police-module peds) are still configured by the persona_* / life_point_* keys in the same table. Verify after boot with /intel_native_behaviour — it should print Config.native_ped_behaviour: present and enabled: true. If it prints MISSING, the block was not pasted — each override then falls back to its v1.16.0 default, which is not the v1.15.3 tuning.

With this on, the resource no longer fights other scripts over ambient-ped attributes, so conflicts with ped-behaviour or realistic-AI resources should disappear. Config.gang_territories and Config.disable_ai_police remain the two places where this resource still reaches for engine-owned peds; both ship off/empty.

Config.police_nonlethal — police never use lethal force at or below a configurable wanted level (default 1 star, zero stars included — lethal force starts at two). A cop you shoot or ram drops out of the band and fights back at full strength (self_defence, default true). The band spawns nothing and takes no bribes; it only disarms and restores. If you run your own police or dispatch resource and the two collide, set enabled = false — there is no yield_to_resources list and no require_police_system flag, despite what older copies of this page said. Verify with /intel_nonlethal.

Config.line_no_repeat_depth / Config.line_no_repeat_tries (default 3 / 6) — the anti-repeat dialogue line picker. No new dependency, no new file, no manifest change. Set line_no_repeat_depth = 0 for the old pure-random picking.

If you maintain a custom locales/ pack: refusal.prostitute is a new key. Missing it is safe — the English pack fills in, and before that the code falls back to refusal.default — but a translated pack should add it.

One realism note that is not a bug: Config.invincible_peds = true ships as the default and makes resource-spawned peds fully proofed, melee included, so a punch does no physical damage at all. Since v1.16.0 the reaction fires regardless — the struck ped fights back, flees or moves to arrest — but if you want peds to actually take the hit, set Config.invincible_peds = false, or Config.life_points.invincible = false for ambient life-point peds only.

---

6 — Superseded and optional resources

lastresort_npc_chat — stopped automatically

Intel NPC ships every NPC Chat feature and more. Running both means two panels fighting over the same ped, so Intel NPC stops it at boot — in either start order — and prints:

[lastresort_intel_npc] stopping lastresort_npc_chat: lastresort_intel_npc supersedes it and already provides NPC chat

Remove its ensure line from server.cfg. Nothing else is required.

lastresort_intel_npc_ai (AI conversations)

Optional. Start it after this resource and put its key in server.cfg:

ensure lastresort_intel_npc_ai
set lastresort_intel_npc_ai:openai_key "sk-..."

Its own INSTALLATION.md has the rest. Which NPCs talk through it is decided here, in Config.ai_bridge.

lastresort_notify (deep HUD integration)

Start it before this resource to light up the deep surfaces (mood toasts, provoke meter, achievement banners, wanted stars, ring timers, dispatch cards, news captions, pickpocket skillcheck). Without it every hook silently no-ops and plain toasts are used — it is never a dependency. Configure the surfaces in Config.simpleasf; verify with /intelfx_check, demo with /intelfx_demo.

One surface in that list is opt-in: Config.simpleasf.rep_rank ships false. It is the XP-style rank banner for a persona's trust tier, and after a conversation it reads as a game overlay on a roleplay server — it also lands over the NPC's face. With it off, a trust change is a quiet toast outside the dialogue panel and the header's gold trust bar inside it, and trust-tier promotions still raise their achievement banner. Set it to true if you want the banner.

lastresort_chat (speech bubbles and feed)

While it is running, every floating NPC line — hails, gossip, dialogue replies, police chatter — renders through the chat's 3D speech bubble, and the line lands in the chat feed as speaker: line on the overhearing client. A player who turned speech bubbles off in the chat settings keeps that choice. With lastresort_chat absent, the built-in floating bubble takes over on the very next line and the feed write speaks the stock chat:addMessage event, so the default chat resource works too. Tune or disable in Config.integrations.chat — it is never a dependency.

lastresort_levels (progression)

If it is running, quest acceptance (1 min), quest completion (5 min) and trust-building interactions (1 min, max one per minute per player) award bonus playtime minutes through its GrantBonusMinutes export. Tune the amounts in Config.integrations.levels, or set enabled = false there to never call it. With lastresort_levels absent it is a silent no-op — no config change needed.

ox_target / qb-target

If either is running, persona and ambient interactions surface through it automatically. Without one, the built-in fallback activates: look at an NPC and press E (rebindable in GTA keybinds; default via Config.builtin_target.key).

ox_inventory native shop UI

By default persona shops open a built-in, server-validated context menu that works on every framework. To use the native ox_inventory shop UI instead, set Config.shop_use_ox_inventory = true and register the catalog in your ox_inventory/data/shops.lua:

['kati_neni_247'] = {
    name = "Maggie's 24/7",
    inventory = {
        { name = 'cigarette', price = 2  },
        { name = 'pack_cigs', price = 18 },
    },
},

(kati_neni_247 is the historic shop id for Maggie's 24/7 — it is referenced from data/dialogue_lines.lua, client/shop.lua and server/main.lua, so keep it as it is unless you change all three.)

7 — Qbox stacks only (optional but recommended): defang qbx_smallresources

Several qbx_smallresources sub-resources actively fight the police features: they suppress ambient cop spawning, clamp SetMaxWantedLevel to 0 and hide the wanted-stars HUD. Intel NPC re-asserts each flag at 4 Hz, so it works without these edits — it is just cleaner to disable the upstream interference once instead of racing it forever. Skipping this still works; you may see mild flicker in the millisecond windows where the competing resource wins the race.

8.1 — qbx_ignore/client.lua

-- SetCreateRandomCops(false)
-- SetCreateRandomCopsNotOnScenarios(false)
-- SetCreateRandomCopsOnScenarios(false)

8.2 — qbx_disableservices/config.lua

Lift the max-wanted clamp so RP heat sticks. Keep police dispatch services off so native dispatch cannot stack shooting cops on the scripted RP unit:

return {
    maxWantedLevel = 5,   -- was 0
    enabledServices = {
        [1]  = false,   -- PoliceAutomobile
        [3]  = true,    -- FireDepartment
        [5]  = true,    -- AmbulanceDepartment
        [11] = true,    -- Gangs (faction backup)
        [15] = false,   -- ArmyVehicle (R*'s eDispatchType: 13 SwatHelicopter, 14 PoliceBoat, 15 ArmyVehicle)
    },
}

8.3 — qbx_hudcomponents/config.lua

Remove HUD component 1 (HUD_WANTED_STARS) from the disable list:

hudComponents = {2, 3, 4, 7, 9, 13, 19, 20, 21, 22}   -- 1 removed

Then restart qbx_ignore, qbx_disableservices, qbx_hudcomponents and lastresort_intel_npc.

The police module itself ships disabled (Config.police_system_enabled = false, alpha). These edits prepare the stack for when you turn it on — via the F12 dev menu, the SetPoliceSystemEnabled export, or the config flag.

8 — Verify

1. Walk up to Maggie at the Davis 24/7 gas station: Talk is the one option on her (target eye, or E on the built-in fallback, which opens the conversation straight away), and G starts a conversation with any ped you look at. Her shop and the single cigarette are offered inside the conversation, in the action row under the replies. 1.1. Errands: in that conversation pick "Got any work for me?" → "I'll take it." A tracker and a routed blip appear; /intel_jobs lists it and can abandon it. Errands that move items need matching inventory item names — set Config.npc_jobs.item_steps_enabled = false if your server has none. 1.2. Bounties: talk to Erika or Denny (the shipped brokers) once or twice to earn trust, then "I want a price on someone." /intel_bounties shows the board to everyone; NPC contracts are on it from the first boot. 1.3. Trade: open Maggie's shop. The header names how she reads you and the prices follow it; Haggle pushes for a discount — and can insult her.
2. Check both consoles for the [lastresort_intel_npc bridge] lines and confirm the detected framework / inventory / notify / target are what you expect.
3. If lastresort_notify is installed, run /intelfx_check; /intelfx_demo is the guided tour.
4. With setr lastresort_intel_npc:debug 1, press F12 (or /intel_dev) and use Simulate hit, /intel_what and /intel_status to exercise the systems.
5. /intel_native_behaviour should print Config.native_ped_behaviour: present and enabled: true; /intel_nonlethal should print enabled=true engaged=… applies=… disarm=true, stars=0/1, cops held=… and excluded by self-defence=… — it prints neither a max_stars= nor an sd_excluded= token, despite what older copies of this page said. Both need Config.debug.
6. Punch a gang member: he should fight back rather than walk on, and /intel_what on him afterwards should show the was_assaulted memory tag — not saw_assault.
7. Performance: F8 → resmon 1 and watch the lastresort_intel_npc row while you stand still, then while you walk a crowd, then with the panel open. See the Performance section of README.md for the ranges to expect.

---

Troubleshooting

Configure

• Leave framework, target, inventory, and notification detection on auto unless your stack needs a fixed provider.
• NPC behavior, interaction distances, city life, street scenes, and paired interactions are configured under config/.
• Set setr lr:locale en in server.cfg to choose one language for the LastResort suite.
• Configure Discord webhooks as server-only convars. Never put secrets in shared Lua files.

Verify

1. Check that the console reports ox_lib and the expected framework providers.
2. Approach an NPC and test the target option or E-key fallback.
3. Test one dialogue, shop, and crime interaction, then restart the resource and check cleanup.
4. Review all startup warnings before opening the server to players.

Important

• QBox installations also require ox_inventory.
• ox_target and qb-target are optional; the E-key interaction works without them.
• Do not run lastresort_npc_chat alongside it because Intel NPC already includes that feature.
• Disable debug, verbose, demo, and permission-bypass options before going live.

Changelog — LastResort Intel NPC

Newest first.

---

v1.63.0 — 2026-09-24

New — AI conversations through the optional lastresort_intel_npc_ai add-on

This resource still contacts no external service. When the separate add-on is running and has its owner's API key, the conversation panel becomes free talk and the add-on's model directs the NPC; without it nothing changes.

• Free-typed replies. A text field above the replies; any letter key starts typing, ENTER sends. AI reply suggestions sit on 1–3 with a suggested tag, the scripted topics stay under them (Config.ai_bridge.keep_scripted_topics). A FREE TALK chip in the header, a teal typing cue while the NPC thinks, the NPC's name in the header once a random pedestrian introduces themselves
• The NPC acts on the model's call: emotion to GTA facial idles and the mood badge, the delivery to a GTA speech context through the speech-synced panel (new tone ai_goodbye → GENERIC_BYE), a gesture as a secondary upper-body animation, and the closing reaction — ends it, walks away cursing, curses, flips you off, flees, hands up, begs, calls the cops, attacks, draws, arrest warning — through the existing reaction set, with the NPC marked panicked or hostile before the dialogue hold is released so the reaction is not cleared
• Lie tells: a lie shows as a one-second head turn away (secondary head IK), a stressed face and a tell line in the panel, Config.ai_bridge.lie_tell_chance of the time; the focus look-at is put back afterwards
• Audience: a shouting match, a public insult or a bizarre player raises the engine's shocking event on the NPC (EVENT_SHOCKING_SEEN_CONFRONTATION 111, _SEEN_INSULT 113, _SEEN_WEIRD_PED 119), read back with IS_SHOCKING_EVENT_IN_SPHERE; a refused event is removed and traced with its cause
• Gossip: six new gossip-worthy events (ai_praise, ai_complaint, ai_threat, ai_generous, ai_suspicious, ai_scandal) carry the NPC's rumour through the existing gossip network; they also surface as heard_ai_* tags for scripted dialogue
• Deals: an offer from the model becomes a gold Accept button in the action row. The server stores one pending offer per player and executes it on Accept inside a price band (Config.ai_bridge.deals): shop items, secrets for sale, bribes for corruptible cops. New callback lastresort-intel-npc:aiDealAccept, new event lastresort-intel-npc:server:aiDeal
• Intel: personas can carry ai.secrets (teaser, text, waypoint, trust gate, price). Bounty brokers and informants share the bounty board from intel.bounty_min_trust; informant and witness reports become street talk. A reveal arrives as a teal intel card, a notification and a waypoint, and the NPC points at the place
• Trust from the model is applied by the server and capped (Config.ai_bridge.trust: +1 a line, +2 a conversation, −2 a line)
• data/personas.lua persona field ai (lore, speech, look, accent, language, voice, no_violence, knows_bounties, secrets), or ai = false to keep one persona scripted
• data/generated/ped_profiles.lua — ped model hash → model name and engine personality for 533 ambient, gang, service and unique peds, generated from the game's ped index, so the model knows it is playing a young hipster or an old rich woman
• server/ai_bridge.lua exports for the add-on only (AiPersona, AiContext, AiConversationStart, AiConversationEnd, AiTrust, AiOfferDeal, AiReveal), refused for any other calling resource
• The speech-synced typewriter takes an external voice source (IntelNpcSpeech_PrepareExternal): an AI voice line holds the text like a GTA bark does, and a line whose audio never arrives releases as silent
• In AI conversations the idle timeout is Config.ai_bridge.idle_timeout_ms (45 s), typing counts as activity, the scripted "impatient" line and asides stay quiet, and a slow reply never counts as the player being idle

Changed

• tools/generate.js 1.3.0: validates the 17 AI gesture clips in both gestures@m@standing@casual and gestures@f@standing@casual and 9 facial idles in both generic facial clipsets (62 pairs, was 10), generates ped_profiles.lua, and no longer scans data/generated/ for model names. Every generated file carries the new version line
• IntelShop_OwnedBy(persona_id) (server) and IntelShop_ItemLabel(item) (client) globals, IntelBounty_PublicBoard() (server)

Fixed

• The dev lab's event table had two wrong eEventType numbers: MELEE_ACTION was 41 (that is EVENT_LEADER_UNHOLSTERED_WEAPON) and SHOCKING_INJURED_PED was 94 (EVENT_SHOCKING_PED_KNOCKED_INTO_BY_PLAYER). Now 42 and 97, checked against the enum dump

Tests

• tests/ai_bridge_server.test.lua (9) and tests/ai_bridge_client.test.lua (13), lua5.4, stubbed engine with a coroutine scheduler

---

v1.62.1 — 2026-09-05

Fixed — your saved standing is no longer announced as a fresh loss

Spawning in threw a trust toast at you for every persona you had a stored reputation with — "Maggie · Trust down (−10)" for something that happened days ago, and a screen-centre rank overlay for a saved positive. Nothing had changed; the restore was reporting itself.

• A restore is not a change. client:persistRestore pushed every saved row through Reputation_Set, which sees the fresh table at 0, calls that a move and fires IntelFx_OnRepChange. The saved set now replaces the table through Reputation_Restore instead: same numbers, same clamp to −10..+10, no toast and no overlay. A move made in the session still announces itself exactly as before, and the panel's trust bar is untouched
• Legacy ambient_<uid> rows are dropped by the restore itself. They were handed to Reputation_Set, which refuses an ambient key — so the prune pass that ran afterwards always found nothing to drop and reported nothing, while the refusal printed a yellow console warning on every single load. The rows are now counted and dropped where they arrive, and the line in the console says how many
• tests/reputation.test.lua — first harness for this module: boots client/reputation.lua and client/persistence.lua against a stubbed engine and asserts a silent restore, the clamp, the dropped ambient rows, and that a real change still fires exactly one toast. lua5.4 tests/reputation.test.lua

---

v1.62.0 — 2026-09-04

Fixed — patience is per NPC and it is remembered

Every NPC in the city showed 9 / 9 patience, and it was back to 9 / 9 the moment you spoke to them again. Two things, both in build_session: the total was Config.dialogue_angry_close_threshold for everyone, and asked_count started every session at 0.

• Each ped rolls its own patience once and keeps it. Base dialogue_angry_close_threshold, plus an offset for who they are — Config.dialogue_patience.by_archetype for ambient peds (an aggressive type loses 4, a cop 2, a stoic or a coward gains 1), by_personality for personas (grumpy −3, tough −2 … gossipy +2) — plus a spread of ±2, clamped to min..max (3..12). The roll lives in the ped's memory next to everything else it remembers about you, so the same NPC has the same patience next time and two strangers do not. The README has promised "Aggressive — zero patience" and "All tunable. Patience…" since the archetype table shipped; this is the first build where the dialogue patience actually reads that table
• Burnt patience carries over. Six questions, walk off, come back: six are still gone, and the meter opens at 3 / 9. It recovers one question per Config.dialogue_patience.recover_ms (2 minutes) of being left alone; an NPC that threw you out stays at 0 until it does, and the first question you ask before then ends it again. recover_ms = 0 disables recovery. The burnt count is written with the rest of the close bookkeeping, so every exit v1.61.0 taught the resource to record — walking away included — records it
• The grumpy point scales with the roll at the ratio the two base numbers have (5 of 9): a 5-patience ped turns grumpy at 3, a 12 at 7. A persona that authors mood_shift_threshold or angry_close_threshold in data/personas.lua is used as written — never rolled, never read back from memory, so editing it takes effect on the next conversation
• The mood-shift and last-question checks fire on >= with a one-shot each, because a session can now start past either point; they used == and would have skipped straight over a seeded count
• A disguised player burns from a fresh count: the disguise hides who is asking, and the patience was burnt by that someone. The ped's own roll stays
• Persisted for personas (patience_total, patience_used, patience_used_at_ms) through the same snapshot as the rest of the memory; ambient peds keep theirs for memory_ambient_max_age_ms like everything else they remember

Changed — panel

• The patience row sizes itself to the ped's total. Nine 4 px segments with their 3 px gaps just about fit the stylesheet's 56 px; twelve would have been under 2 px each

---

v1.61.0 — 2026-09-04

Fixed — NPCs actually remember the conversation you just had with them

Talk to someone, walk away, come back: they greeted you like a stranger and the whole topic list was askable again from the top. The causes were all in the wiring rather than in the memory model — the tags, the counters and the topic history were being computed correctly the whole time and then dropped on the floor.

• Walking away recorded nothing at all. Drifting out of range, the ped leaving or dying, getting into a car, a patrol claiming the ped — every one of those closes went through IntelNpcNui_ForceClose, which drops the NUI handlers without running on_close_request, and then end_focus, which nils the session. So the way a player ends a conversation most often wrote no interaction count, no close reason, no carried mood and no topic list. client/focus.lua records those closes now, with the reason it actually detected, and IntelNpcDialogue_CloseBookkeeping is idempotent per session so a close that named its own reason keeps it and is never counted twice
• Ambient peds never recorded which topics they had been asked. The write was gated on session.persona_id, which is nil by construction for every random pedestrian — so Memory_RecordTopic was never reached for the NPCs players talk to most, and the 30-minute memory_topic_ttl_ms band never applied to them because nothing was stored to expire. The read side in place_row carried the same wrong gate independently. Both key on memory_key now, like mark_asked's own repeat check, build_session's pre_asked and every other reader already did
• A re-opened conversation replayed its opening line word for word. Inside the five-minute resume window (Config.memory_session_resume_ms) the cached greeting was replayed verbatim and the re-meet line was explicitly suppressed, so a resume was indistinguishable from a first meeting. A resume now opens with the recognition line — "Back again, huh." — instead of the stored greeting; a genuinely new conversation still gets the recognition line in front of a freshly picked greeting, as before
• A recycled entity handle could inherit a stranger's memory. Where a ped carries no state bag the memory key falls back to the raw entity handle, and GTA reuses handles. The ped's model is stamped alongside the key, so a handle that comes back on a different model starts clean rather than greeting the player as a regular. There is no engine getter for "is this the same ped", and the model cannot prove that it is — it can only prove that it is not, which is the half that matters here
• A conversation open at a resource stop was lost whole. client/focus.lua tears the session down in its own onResourceStop, which the manifest order puts after the persistence flush, so nothing it recorded could reach the snapshot. The in-flight conversation is recorded in client/persistence.lua immediately before the flush instead

Added — the 3D surfaces over NPCs are switchable from F12

• An "Above heads" section at the top of the Modules tab. The three surfaces drawn over an NPC's head are together and reachable without editing shared/config.lua: the 3D overlay as off / basic / full with the current mode marked, and switches for the status dot (Config.mood_icon_enabled — talk / busy / hostile, 18 m) and the name above an NPC (Config.show_npc_name_tooltip, which only draws while the 3D overlay is off, and the row says so). Both switches defaulted off and were previously config-only, which is exactly the kind of look-at-one-thing surface a live toggle is worth most for
• The dot applies on the tick you flip it, through a new IntelNpcMoodIcon_SetEnabled. Writing Config.mood_icon_enabled alone was picked up only on its module loop's 2 s idle wait — long enough for whoever flipped the switch to decide it had done nothing
• The overlay action reads the mode back after setting it and reports what actually took, and refuses a mode that is not one of the three by name

Fixed — panel

• lp-btn on was already written for the ped-story view picker and had no CSS rule at all, so the picked view looked identical to the unpicked one

---

v1.60.0 — 2026-09-04

Changed — the panel is rounder, glassier and alive

• Roundness and glass. 22px panel, 14px rows and cards, pill chips and keys; the panel is translucent (--panel-bg alpha .80, raise it in nui/theme.css for a more opaque box) with the sunset horizon wash and an inner highlight. No backdrop blur — the NUI layer composites over the game and has nothing to blur
• Animation vocabulary. The panel springs in and eases out, the plate and portrait land a beat later, the sunset rail breathes, the name shimmers and glows while the NPC is speaking, replies cascade in with a stagger, the cursor row lifts with a light sweep, a picked row and a picked action flash, the trust fill glows on a change and both meters grow from empty on open, the mood pill pops when the mood changes, a burnt patience segment flashes, the body-language line fades in when it changes, the hint keys press when you press them, and a blinking caret rides the typewriter
• Restored from v1.58.0. The portrait initials, the body-language line in the plate, the witness chip's label, the patience count next to its segments, the impatience warning pill, the tone tag with its icon on every reply that has one, always-visible reply subtitles, the follow-up / cost / skill / lock / leave tags with icons, the "recent:" trail above the replies, icons on stage directions, the actions header with a count, trust and composure label icons and fill glow, a bigger log and reply list, T as a shortcut into the action row
• The replies no longer fold away. Folding shortened a bottom-anchored panel from its pinned edge, so the plate and the line being read dropped by the list's height on every exchange and jumped back with the next set. The list now stays where it is and recedes to a quarter opacity with the picked row lit, and a "thinking" cue with the speaker's name pulses in the log until the answer starts
• A default cursor. The first reply is highlighted when a set arrives, so ⏎ always has something to pick; the mouse moves it, ↑ ↓ move it, and only one row is ever lit (the hover style was removed in favour of the cursor, which the mouse drives)
• ⏎ during the audio hold picks in one press instead of first cutting the bark and needing a second press

Fixed

• The "scrollable" fade on the reply list was measured while the rows were still arriving; it is measured after the cascade now
• Meter fills animated in from the previous conversation's value on open; they reset to empty first
• The trust meter showed the previous action's value. The panel read the local cache, which the server only updates later on client:repSet, so the delta popped one action late and on the wrong reply. The server's answer now reaches the open panel the moment it lands, with the real delta
• Follow-ups with a type were dead content. A follow-up carrying type = 'beg' / 'tip' or close = true (Joe's cigarette, bread and beer asks, the gang tree's farewell) ran through the plain-answer path and ignored the type; they go through the same branches as a topic now and keep their thread
• The player's farewell line was printed twice on a polite close through the authored farewell topic
• The name prompt counted as idle. Typing your name in the introduce-yourself dialog could get you kicked mid-typing; the idle clock restarts when the prompt returns
• The idle watcher quit on its first tick when no camera focus existed (focus disabled in config, or a static persona whose ped is not spawned), taking the impatience line, the idle kick and the drew-a-weapon reactions with it
• An error inside a selection handler left the panel locked for the rest of the conversation. The bridge now prints the error and unlocks
• A selection resumed after a server round-trip kept messaging a conversation that had already ended (idle kick during the call); those paths return once the session is gone
• The ambient.<category> speaker-name fallback never fired, because a missing locale key returns the key rather than nil
• The close watchdog could fire while the close message was still queued behind a line being typed, dropping NUI focus on a panel still on screen; the watchdog is fed from the moment the close is queued
• An unlock without a new reply set left the picked row lit and the keyboard cursor unsynced
• Long names and roles were ellipsized because the chip column never shrank

---

v1.59.0 — 2026-09-04

Changed — the dialogue panel is a scene, not a chat window

• One panel, bottom-right. The floating header and the chat shell were two boxes of the same width on the same edge, and the shell grew upward into the header whenever the topic bar was expanded. Name plate, dialogue log, replies and the action row are now one box, with a pixel height budget written from JS (--scene-max) so the log and the reply list shrink before the panel can grow off the top of the screen
• A script, not bubbles. The log shows the speaker in small caps, the line under it, and stage directions in italics between (body language, a trust change, a warning). The avatar initials, the chat bubbles, the "You" bubble alignment, the three typing dots, the blinking caret, the "Waiting for response…" spinner and the "recent:" trail are gone — every one of them read as a chatbot
• Numbered replies plus an action row replace the collapsible "Bring up a topic" bar with its count badge and T key. Conversation lines are the numbered rows; the things you do (tip, bribe, flirt, threaten, beg, the persona's shop or job) are small buttons under them. ↑ ↓ and ⏎ pick a reply, TAB moves to the actions, 1–9, SPACE and ESC are as before
• Replies fold away while the NPC answers and open again with the next set — a reply is on screen exactly when it can be given. The picked row stays lit for a beat first so the player sees which one registered, on the number keys as much as on the mouse
• Choice previews render inline under the row on hover or cursor. They were a floating tooltip positioned outside a row with overflow: hidden, so they had never been visible
• The hover lift works. Each row's enter animation used fill-mode: both, whose final transform outranked the hover transform forever
• Less ornament: no film grain, no breathing neon rail, no letterbox bar across the top, one sunset hairline on the panel and the gradient on the name. nui/theme.css keeps every token; --bubble-npc now colours the reply under the cursor

Changed — the E menu is Talk

• The target menu on a ped carries one option: Talk. Give item, Rob, Mug, Pickpocket, Bribe, Tip, Threaten, Flirt, Help up, Take photo, Frisk, Drag away and Drop are gone from the menu; money, threats, flirting and begging live inside the conversation as actions, where they always were wired into reputation, perception and the witness network. On the built-in look-at fallback, E opens the conversation directly and the prompt reads [E] Talk; the prompt hides while a conversation is open
• A persona's own interactions (buy an item, browse the shop, take a job) moved with them: they are actions in that persona's conversation rather than rows next to Talk. IntelNpcInteraction_Run(persona_id, index) runs one from anywhere

Changed — conversations flow

• No more lost clicks. Selecting a reply was gated on a 900 ms wall clock (Config.dialogue_click_cooldown_ms), so a player who skipped a line and answered quickly saw the row light up and nothing happen. Selection is now gated on the previous answer finishing: the panel locks itself on a pick and unlocks with the next reply set. The config key is kept but no longer read
• Replies appear when the text is done, not when the audio is. With Config.dialogue_speech on, the typewriter used to hold the whole panel until the bark ended (up to six seconds), which read as the panel hanging. Only the NPC's next line and the close wait for the audio now; picking a reply cuts the bark, the way interrupting someone does
• Follow-up siblings stay reachable. Picking one of three follow-ups used to bury the other two: the response showed only that follow-up's children, and the parent topic was then locked as "Asked". A thread now keeps every follow-up whose parent has been asked on the table, closest first
• A leaf answer returns to the topics. The "Ask something else / End conversation" dead-end after every answer is gone; "Ask something else" stays only while a thread still has follow-ups
• Asked topics stop cluttering the list. One whose thread still has unanswered follow-ups comes back as a way into that thread ("more to ask"); one with nothing left sits muted at the bottom, still selectable — re-asking it gets the "I just told you" line and earns no standing. That line pool (feature.dont_remember) had never fired: the flag it reads was reset before it was read
• The NPC's counter question follows their answer as one voice, without the "They look at you, waiting" pill
• A beat before some answers. bridge.<mood> pools ("Hm.", "Ugh. Fine.", "Now that's interesting you ask.") are prepended to an answer at Config.dialogue_bridge_chance (0.4), never on the first answer and never on an interaction outcome
• One unprompted remark per conversation. After Config.dialogue_aside_after (2) answered questions the NPC says something nobody asked for — aside.* pools keyed on wanted, bloody, armed, masked, rain, the hour, then their mood — before the topics come back. Config.dialogue_aside_enabled / Config.dialogue_aside_chance (0.7)
• Leaving is a line, both ways. The leave row is the tree's own farewell topic where it has one, otherwise one of leave.lines picked per session; the NPC answers from farewell.<mood>, and either way it is the polite close that reports the standing point. ESC is walking off without a word and stays a stage direction
• Impatience is spoken. At the idle warning the NPC says an impatient.<mood> line in the log (and in their voice, with speech on) and the patience meter dims, instead of a pulsing HUD pill
• The patience meter counts what they will still answer. The live watcher added one to it, so it read "1" at the point where the next question ends the conversation
• The mood-shift notice, the last-question warning (which was hardcoded English) and the "nothing more to ask" line are stage directions in the log; "One more question and they're done with you" is dialogue.last_question_warning
• New config keys are backfilled in shared/defaults.lua, so an existing config gets them without editing

Removed

• nui.topics_bar, nui.waiting, nui.key_topics, nui.recent, nui.impatience, dialogue.npc_asks_back, dialogue.back_to_topics_sub, dialogue.locked_reputation, dialogue.already_asked, dialogue.all_topics_done, dialogue.npc_annoyed, the thirteen target.* menu labels and the interact.* strings behind them, from both languages. interact.unknown_reason stays (jobs, bounties and the shop use it)

---

v1.58.0 — 2026-09-04

Changed

• The 3D debug overlay no longer ships on. Config.debug_3d_mode was 'basic', and Config.debug ships on so a fresh install is drivable — so out of the box every pedestrian within 25 m carried two rows of text over their head: name/category, archetype and distance on the first, live state (panic, hostile, busy, irr 2/3, rep -4, voice cast, driver:…, fighting you, fleeing) on the second. That is a development tool, and on a live server it reads as a broken HUD rather than as diagnostics. The default is now 'off'. Nothing else about Config.debug changed: the dev menu, /intel_* commands and the map blips are where they were, and an existing shared/config.lua that already sets debug_3d_mode keeps its own value
• setr lastresort_intel_npc:debug 1 now sets debug_3d_mode = 'basic', so the convar still gives a dev server the overlay along with the rest of the tooling; debug 0 sets 'off'. The convar previously wrote Config.show_debug_3d, a legacy key that is only consulted when debug_3d_mode is nil — and the shipped config always set it, so that line had no effect on the overlay at all

Fixed

• The overlay held a per-frame slot while drawing nothing. The frame callback was registered whenever Config.debug was on, then returned immediately if the mode was 'off' — a no-op every frame, on every install, for as long as the overlay was switched off. It is now registered only when something will actually be drawn, which is what the README's performance section always claimed. Four copies of the mode-resolution expression collapsed into one overlay_mode()

---

v1.57.0 — 2026-08-31

Added

• shared/defaults.lua, the config backfill this resource never had. shared/config.lua is the file you edit and keep, so a release can never assume a new key exists — the copy on your server is the one you wrote months ago, and a feature added in an update would read nil there, run nothing and print no reason. Any key added from here on gets its default in the backfill, which loads immediately after the config and fills nil keys only, so a value you have set always wins.

Fixed

• README masthead still read v1.56.0 after the version bump.

---

v1.56.0 — 2026-08-29

Fixed — exports that could not do what the table promised

• IsInPoliceScene() had been permanently false for eleven versions. It answered by calling IntelPolice_HasActiveScene() and IntelPolice_HasWaitingPed(); both were deleted when the police module went native-dispatch-only, and because the call was guarded with and, the export silently returned false instead of erroring. README told server owners to check it before their own dispatch sends a unit, and INSTALLATION.md repeated the instruction. It now returns false with the reason written next to it, both docs say so, and both point at the real hook, lastresort-intel-npc:server:dispatchRequested. The export is kept rather than deleted so a server already calling it does not error
• The scene field on the ped-hit payload was IntelPolice_OwnsDispatch(ped) — a third deleted probe, so the field was always nil and nothing on the server read it. Removed
• README described AddReputation(id, d) as "adds a delta, same clamping". It has refused and returned false since v1.42.0, when reputation became server-owned. SetReputation(id, v) was described as setting reputation; it writes the local display value, which the next server restore overwrites. Both rows now say what the functions do

Fixed — money and rewards reported as facts before they happened

• server:itemBought fired on every purchase attempt, including the failures. default_handle_buy_item has four early exits — no item, not enough cash, the withdrawal refused, the inventory full — and the caller triggered the event unconditionally right after it. Any external shop-log or analytics resource recorded sales that never happened. The handler now returns a boolean and the event is gated on it. A refund that the money adapter refuses after a full-inventory rollback is now logged loudly instead of vanishing
• A job reported the cash it rolled, not the cash it paid. Adapters.money.AddCash returns false when the framework refuses the deposit; the return was discarded, and the reply, the chat line and server:jobCompleted all carried the rolled amount regardless. cash is now what was actually deposited, a refusal sets payout_failed, and the player is told rather than shown an unexplained $0
• A job payout was rendered as a purchase. client/jobs.lua announced it through IntelFx_PurchaseToast, which draws -total under the word "Purchase" and follows it with "Added to your pockets" — so earning $500 read as spending $500 on nothing. New IntelFx_RewardToast draws it as money in. The shop keeps PurchaseToast, because that one really is a purchase

Fixed — config that documented a system that no longer exists

• Config.police_patrol advertised two police fleets and nothing read them. Cruise patrols with max_active, spawn and despawn distances, car and ped models, speed; a response unit with accuracy ranges and a despawn timer — 17 keys in all, plus a 16-line comment arguing why cruise patrols ship on by default. Every spawner behind them was deleted when the module went native-dispatch-only, so a server owner could set cruise.max_active = 6, restart, and change nothing. The dead keys are gone. The three that are read — bribe_amounts, bribe_refusal_chance, bribe_distance_m, all server-side — keep their path so existing configs still work
• Config.police_nonlethal carried orphaned comment fragments describing dispatch-service switching, a SET_WANTED_LEVEL_DIFFICULTY dial, require_police_system and yield_to_resources. None of the four was ever implemented in the band. The block now states that its seven keys are the whole feature, and README and INSTALLATION.md stop offering the phantoms as integration advice

Fixed — panels and tests that could not fail

• Two in-game test steps passed unconditionally. pol_nonlethal printed c.nonlethal_on / nonlethal_engaged / cops_held / self_defence_excluded / dispatch_off from IntelPolice_Counters(), a table that has never carried any of those five keys — they belong to IntelPolice_NonLethal_Counters() in the other module — so it printed nils and returned true every time. pol_cleanup asserted cruise + response + spawned_peds == 0 against three counters the module hard-codes to zero, and told the tester to expect spawned cops to disappear. Both now read the real API and have real failure paths, and pol_cleanup says what /intel_police_clear actually does: it drops the wanted level
• The scene panel's police block read five keys that were never sent. Same cause: the panel asks for the non-lethal band's state and was handed the wanted module's counters. The band always read "off" and the two counts read undefined no matter how many officers were held. client/scene_panel.lua now merges in the band's own counters. The three permanent-zero patrol rows are gone, dispatch suppressed is relabelled dispatch suppression requested — ENABLE_DISPATCH_SERVICE has no getter, so it is a request and never a confirmation — and the waiting ped / scene rows went with the scripted scenes they reported
• Three buttons labelled "cycle the 3D overlay" opened the dev menu. All three sent /intel_dev. There was no command for the cycle at all — toggle_3d_overlay was a file-scope local reachable only from a menu row. It is registered as /intel_overlay, allowlisted, and the buttons point at it
• Reputation_OnPoliteClose returned "persona trust +1" while the line above it explains the point is only reported — the server prices it and may pay nothing. It says reported now

Fixed — a second pass: the public API, the metrics, the phantom hotkey

• The perception fallback for events GTA has no crime type for had never raised a single star. It fired client:adjustWantedMin, a handler whose first line is if Config.police_system_enabled then return end — that event is the EXTERNAL path, for when this module's police system is off. The branch that fired it sits inside if ... and Config.police_system_enabled then, so the event could only ever reach a handler that returned immediately. It goes through IntelPolice_Bump now — the module's own clamped setter — and the trace reports the level that actually landed, or names why nothing did
• The speeding toast printed the star count as a speed. police.speeding_desc read "A patrol clocked you at %dkm/h" and was formatted with stars, so 140 km/h past an officer said "clocked you at 1km/h". The measurement was already in scope; both languages now take the speed and the stars
• Every metric the client reported was discarded at the door. metric() sent (group, key) as two positional arguments and the server's handler opens with if type(payload) ~= 'table' then return end. Independently, the two keys it sent were not in the server's bucket, which drops unknown keys. Both fixed
• peaceful_resolutions never counted one. It and damages_paid were triggered back to back through the metric NET event, whose handler is rate-limited at 100 ms per source — and a server-local TriggerEvent carries no source, so both shared one bucket and the second was always dropped. Server metrics now bump directly
• Seven metrics in a public export sat at zero forever. GetMetrics() and /intel_metrics reported pre_call_timeouts, combat_resolutions, bribe_paid, bribe_refused, bribe_no_money and sessions_closed_normal as live counters. The first two counted the scripted police scene deleted in v1.17.0 and are gone; the three bribe outcomes are wired to the bribe that does exist; sessions_opened is wired; sessions_closed_normal is gone because the server cannot observe a close
• The dev police toggle claimed a change the server may have refused. Both the F12 panel and the ox_lib menu set the client flag, fired a net event with three silent exits (debug off, no ace, rate limited) and reported the new state as fact. It is a callback now: it answers, refusals name their cause, and the UI says which halves actually moved
• "B — Apologize" was on the HUD and nothing was bound to B. No RegisterKeyMapping, no command, no handler — the one-press apology belonged to the pre-call panel deleted in v1.17.0 and only the on-screen promise survived. The hint, Config.apology_quickkey_enabled, Config.apology_key and the locale string are gone
• *Fifty orphaned `police.` locale strings** — the responding officer's lines, the talk-down, the surrender and hang-up notices, the patrol blip, the tow — removed from both languages, which stay in sync
• Three documented server callbacks did not exist. preCallBribe, bribeRespondingCop and listQuests were rows in the README's callbacks table; an external resource calling any of them waits forever. Removed, with the real errand callbacks named in place of listQuests. bribeSpawnedCop is real but was described as bribing "a scripted patrol officer" — it bribes an officer GTA dispatched, and the row now says what the server actually checks
• server:policeBribe reported kind = 'patrol' for a module that has spawned no patrol since v1.17.0, and the Discord log said the player "bribed their way out of a police scene". It is 'native_cop', and the log says an officer took the money
• The README's A–E flow described the police module as it was before v1.17.0 — a pre-call talk-down window, a cruiser that drives in, an officer who walks over, a seven-choice cop scene. All of it was deleted years of versions ago. The flow now describes contact detection, the severity tiers, the report roll, the hand-off to native dispatch with a search centre at the scene, and the non-lethal band
• Config.police_wanted_clamp_enabled does not exist and both docs told owners to set it to false "so the two don't fight over the wanted level". Nothing needs disabling: the ceiling caps only what this module asks for and never lowers a level anyone else set
• A dev-test step told the tester to look for the pre-call panel and to mark the test failed when it did not appear

Fixed — a third pass: the medium sweep

• Behaviour, not wording:

• A clamped raise could LOWER the wanted level. bump_wanted compared the current level against the UNCLAMPED request and then handed that number to a setter that clamps it. At three stars with a request for four the guard did not fire (3 >= 4 is false), the setter clamped 4 down to the module ceiling of 2, and the player dropped from three stars to two — a raise that lowered a level this module never set, which it must never do

• client:adjustWanted was a registered net event with no sender. It set an ABSOLUTE level, so unlike adjustWantedMin it could lower stars, and any other resource on the server could fire it. Deleted

• A purchase from a persona has never moved their opinion of you. The server passes interaction.type — the literal 'buy_item' — into GrantProven, which looks it up in Config.reputation_interaction_delta. There was no buy_item key, so the grant returned nil every time. The key exists now (+1, smaller than a tip), and the grant runs after the sale instead of before it — a player with no cash or a full inventory used to earn the goodwill anyway

• A manual bounty claim destroyed the kill proof every other poster needed. The block above ledger_names states the rule — one death settles every bounty already standing on that victim — and calls consuming the record "the WRONG fix". The manual claim path did exactly that. posted_before is the rule and it needs no deletion

• START_ALARM is void and the alarm was never read back. IS_ALARM_PLAYING is a real getter, this file's own header says so, and it was only ever asked elsewhere. An alarm that does not sound now says so — and says the NPCs are still reacting to a sound the player cannot hear

• Void natives reported as facts:

• SET_PLAYER_WANTED_LEVEL is void, and both the police module and the dev menu reported the level they ASKED for. GET_PLAYER_WANTED_LEVEL is free; a refusal is now named, with the usual cause (another resource's max-level clamp)

• The non-lethal hold traced four void writes as done. Two can be checked — GET_PED_ACCURACY, and GET_BEST_PED_WEAPON for what the officer still OWNS after the disarm — and a cop who kept his pistol is now reported loudly. The two combat attributes have no getter and are reported as requested

• The gesture diagnostic's header claimed "every answer here is read from the engine". Six of seven are; layer_on is our own bookkeeping, because none of the seven SET_PED_CAN_PLAY_*_ANIMS natives has a getter. Its final verdict said "the engine is gesturing", which nothing can know

• Restores that were resets (all three kept the scope, which is the real protection — only names this resource wrote are touched):

• client/audio.lua's header promised every emitter and zone was "put back". There is no getter for either, so what goes back is the engine default

• client/crowd.lua's header promised every recruit's blocking flag was "snapshotted before the write". SET_BLOCKING_OF_NON_TEMPORARY_EVENTS is one of GTA's write-only setters — there is nothing to snapshot

• /intel_lab dispatch_enum logged "all dispatch services restored to enabled"

• client/duck.lua's header promised the release "escalates to STOP_AUDIO_SCENES()" eleven lines after explaining why that native is never called here. The NUI repeated the promise

• Counters and labels that did not mean what they said:

• /intel_patrol printed "%d guards walking one right now" from a count of peds assigned a route. verified — the count that means walking — was already on the next line

• /intel_lookat_test printed "%d people glanced at you" from the number of peds TASK_LOOK_AT_ENTITY was issued on

• The red-light trace and toast said "an officer saw you". Nothing established that — only any_cop_within(), a distance sweep. Proximity is not witnessing

• The debug overlay's header promises "an empty row 2 means a perfectly ordinary pedestrian". Two chips were unconditional: own voice for any ped with no cast voice, and in a car for any ped in a vehicle. Row 2 was never empty

• The speeding toast formatted the star count into a %dkm/h string

• Surfaces and switches:

• IntelFx_OnWaiting deleted. A countdown ring plus a key hint bar for the pre-call window and cop scene, both deleted in v1.17.0. Nothing in gameplay called it; its own dismiss loop polled IntelPolice_IsInScene, a fifth undefined police global, so even in the demo the ring vanished on the first tick. A countdown the player cannot act on says there is a window, and there is not. Config.simpleasf_fx.police_timers and seven locale strings went with it

• IntelFx_OnDispatch finally has the hook its config advertises. It is raised where the wanted level READ BACK higher after REPORT_CRIME — the one moment the engine demonstrably took the call. Only the two radio codes the file's own header sources are used; the rest read 911 rather than an invented number

• IntelPolice_IsInScene removed from all four files that called it — the mood icons, the FX ring, the inspector's police-scene tag and the focus guard. All four were guarded with and, so all four silently answered false

• The item, purchase and reward toasts returned true even when the simpleasf export threw and the integration was marked down — so every caller's fallback to a plain notify was skipped and the message vanished

• The F12 hail button said "Hail forced." on all five gates. try_hail already knew which one closed, for its trace line, and threw it away. It returns (ok, why) now and all four callers report it

• The hail trace said the line went "in the chat feed". That feed is opt-in and defaults OFF; the floating hail frame is what the player actually reads and was the one surface never mentioned

• The Modules tab's "Police system" and "Verbose server log" switches write only the client's config. Both labels say so; the Police tab's ace-gated version is the one that moves the server

• SetPoliceSystemEnabled() likewise, in the export table and in README

• award_rep_gain awards no reputation — it grants a levels bonus and reads Config.reputation_interaction_delta only as an on/off gate. Renamed

• The ESX test-pistol route reported a pcall status as "added through ESX addWeapon". ESX's addWeapon returns nothing

• client/dev_menu.lua claimed "the preflight harness now fails the build". There is no build step for a FiveM resource and no such harness in the tree. Its "Dump cruise patrols" button dumps the wanted state

• The control panel's header claimed "nothing here has its own private truth". The Tests tab is a hardcoded array in the NUI, kept in step with client/dev_test.lua by hand

• Docs:

• README still said Version 1.16.7, "Five tabs" (there are nine), "all 74 of its actions, verified by a coverage check" (there is no coverage check) and "139 clickable actions" (a number derived from nothing), and "Fourteen" experiments where the bench has sixteen

• extra_light_hashes was advertised for custom-map traffic lights and exists nowhere; the junction and its lights come from GET_VEHICLE_NODE_PROPERTIES, which needs no hash list

• /intel_police_clear was "Reset all police state"; /intel_nonlethal listed four fields it does not print; INSTALLATION.md said /intel_police_dump prints cruise patrols

• *145 orphaned `police.locale strings** removed from both languages — the complete dialogue trees of the pre-call talk-down, the mid-call conversation and the seven-choice cop scene, plus the responding officer's lines, the surrender and hang-up notices, the patrol blip and the tow. Sixpolice.*` keys are live and they are the six that remain

Fixed — a fourth pass: the low sweep

• "Wipe hail cooldowns" left the global gap in place. IntelNpcHail_ResetCooldown cleared only the per-ped table; try_hail returns on LastGlobalHailMs before it ever looks at a ped, so for up to 25 s the wipe changed nothing
• The Patience pill was off by one. The kick fires at asked_count > hard, so the pill read "0 left" while one question remained
• The informant Discord embed has never logged a coordinate. It read payload.coords; both senders use event_coords
• client:patrolBribed had no handler anywhere. It was the stand-down signal for the scripted patrol unit deleted in v1.17.0
• AddPersona() returned true after a failed registration. IntelNpcSpawn_RegisterRuntime returns false for a persona with no coords — the entry lands in the table and nothing will ever spawn it
• The overlay's reputation colours were written for a ±100 scale. rep <= threshold + 10 put the red band at or below +5 on a scale that stops at +10, and rep > 30 made the green band unreachable. The archetype thresholds it is fed run −2 to −9. client/npc_state.lua's fallback was -50, which no ped could ever cross
• Three void writes now use the getters that exist: SET_NEW_WAYPOINT → IS_WAYPOINT_ACTIVE (the bounty toast said "Marked on your map" regardless), SET_ENTITY_HEALTH → GET_ENTITY_HEALTH (the collision softener said "put back to %d"), SET_AMBIENT_VOICE_NAME → GET_AMBIENT_VOICE_NAME_HASH (a persona "speaks as X" even when the build ships no such voice)
• Five more that have no getter now say what they asked for: the manhunt release, the incident delete (where IS_INCIDENT_VALID is ambiguous by design), the crowd's "gathered", /intel_engine_police's three config-intent values, and /intel_ambience release — which restores the radio on/off flag from a real getter but writes loud to false and never puts the station back
• The cop bribe answered "(cleared N stars)". The clear happens on the client and the server never reads it back
• trace_clear and ped_forget reported success when the trace module was not loaded; the command runner promised console output for commands that print none
• The inspector's event queue: gunshot/shot/… labels invited reading 124 (SHOT_FIRED, the shooter's own event) as "this ped was shot"
• Config.mood_icon_enabled draws no mood — the colour comes from whether the ped will talk to you and from the reputation tier. The key keeps its name so existing configs load; the comment stops lying about it
• The Lab tab pointed at docs/NATIVE_AUDIT.md, a file that does not exist
• The Tests tab's "simpleasf master switch" was rendered as a button, so it carried no state and its first click could be a silent no-op
• client/dev_menu.lua claimed the ox_lib menu "owns" the per-persona memory and reputation editors "which the panel does not carry" — the Personas tab has all of them
• The whole FX layer was hardcoded English while the locale pack's header tells a server owner that copying and translating one file covers everything. Ten strings moved to fx.* keys in both packs
• The dispatch card's meta line read "Caller on scene · plate noted". There is no caller entity and no plate is ever queried
• The dialogue header's Zone · HH:MM pill was computed once at open and never updated. GTA's clock runs ~30× real time, so a two-minute conversation left it an hour wrong. The zone stays; the clock is gone
• GetReputation() is the client's cached copy of the server's last answer, not a live read. Both the export and README say so
• INSTALLATION.md's verify step told you to look for max_stars= and sd_excluded= tokens that /intel_nonlethal does not print

Fixed — the seventh dead police global, found by scanning for the bug class

• The lie hunt found five functions that no longer exist being called through an and guard, so each answered false in silence forever. Rather than trust that five was all of them, the whole tree was scanned for the pattern — and it was not.

• IntelPolice_TryEngage and IntelPolice_GetNearestWaiter are defined nowhere, and were called from eight places across client/quick_talk.lua and client/dialogue.lua. They were the entry into the scripted cop scene — "the officer is waiting for you; press G" — deleted in the v1.17.0 cut. Because every call site guarded them, waiter was always nil, every engage branch fell through without a word, and the quick_talk.step_out_* notice could never appear

• The wrong-officer redirect in both files went with them: it fired on PoliceSpawnedPedSet, which this module has not put a ped in since the same cut, and its only job was to hand you to a waiter that cannot exist. A cop GTA dispatched now falls through to the ordinary ambient dialogue, which is the right behaviour for a ped this resource does not own. Four more orphaned locale strings removed from both packs

• The scan is now a harness. It walks every .lua in the resource, builds the set of names the resource actually defines, and fails on any guarded use — X and X(, if X then X(, X and X., X and X[ — of a resource-prefixed name that is not in it. The six dead police names are also asserted by name. This class of bug cost seven silent failures; it cannot hide again

Fixed — reputation dev controls (carried over from the same sweep)

• The NUI reputation buttons still read = 50 friendly and = 80 trusted from the pre-v1.42.0 0–100 scale. v1.54.0 fixed the ox_lib menu and left the primary surface untouched. They are +1 / −1 / = −10 hostile / = 0 neutral / = +5 friendly / = +10 trusted on the real −10..+10 scale
• The trace filter toggled the wrong way: the payload reported the class's state before the click, so the first press on any filter sent the opposite of what the button then showed
• "Wipe all reputation" cleared only the local table; the server restored every row on the next load. It calls the new ACE-gated server:devWipeReputation now
• The rep toast printed the old number as "is now N", because it read the local value before the server's answer arrived. It no longer quotes a value
• The memory dump button never printed anything
• Three panel replies said the resource had done something it had only asked for (hail, scene, hit test)
• EN and HU locale strings promised wanted stars the engine had not been asked for and might refuse; they say reported/requested

---

v1.55.0 — 2026-08-29

Fixed — nothing claims the engine acted when it cannot know

• Two contradictory truths about REPORT_CRIME, in one resource. client/police.lua documents that the native is void, that a successful pcall proves nothing, and then reads the wanted level back ~900 ms later to report crime_native_took or crime_native_ignored. client/perception.lua kept its own copy of the call and the crime-id map, and reported filed = true from the pcall alone — tracing that the crime "went through GTA's own dispatch". The duplicate is deleted; there is one implementation and one crime map, and the trace now says the crime was handed over, that the outcome is not knowable at that point, and where the engine's actual answer appears
• The manhunt traced two pcall booleans under the keys is_wanted and police_focus. Both natives are void with no getter, so those keys named engine state that had never been read. They are set_is_wanted_call_ok / set_police_focus_call_ok now, the message says the calls were made rather than that they landed, and the open question — whether the flags apply at all when another client owns the vehicle — is marked [NEEDS IN-GAME TEST] instead of being quietly answered
• /intel_witness printed "N played by the ENGINE" from a counter fed by pcall(TaskShockingEventReact, ...). That native is void: the count was tasks that did not error. engine_reacts → engine_react_tasked, engine_reactions → engine_tasked, and the command says "TASKED to the engine" with a line explaining why that is the honest word
• IntelNpcAudio_Emitter and _Zone returned the pcall boolean as their success value, so every caller was told the emitter or zone had been switched. Both natives are void with no getter. They are EmitterCall / ZoneCall now and return "the call was made" plus a reason; the old names remain as aliases so no caller breaks

Note on the tooling

• The first scan written to find these read a return_type key the native dump does not have. Every one of its 6416 entries came back None and it produced a list of 110 false findings. The field is results; the real count is 12, of which 4 were lies, 1 is a documented void-with-out-params case, and the rest were already honest. A tool that cannot be trusted is worse than no tool, so the harness now pins the dump's shape as its first assertion.

---

v1.54.0 — 2026-08-29

Fixed — the dev tools were lying about reputation

• Asked whether everything was testable in dev, the answer turned out to be no — and the reputation controls were actively misleading.

• The F12 "Rep +10 / -10" buttons moved a number the server never had. Reputation_Add became local display only in v1.50.0, so the button reported a change, the panel showed it, and the shop went on pricing at the old value. Every reputation-gated feature — shop prices, job eligibility, bounty trust — was untestable, because the thing the gates read never moved

• And they were on the wrong scale. Reputation is clamped to −10…+10, so the old Rep = 50 and Rep = 80 buttons both landed on 10: the same button twice. The buttons now span the real range

• server:devSetReputation writes what the server actually stores and answers with it, behind the same ace as every other dev event. The control panel's rep action goes the same way

Added — so a refusal can be seen

• /intel_authority. Almost every server callback refuses with a named reason — too_far, not_a_cop, no_wanted_reading, bad_shop — and the player saw none of them, so a silent no-op was indistinguishable from a working gate. The server now keeps the last dozen refusals per player and this prints them, with your citizen id, routing bucket, the wanted level as the server reads it, and which shops are in reach of their owner
• /intel_rep. Prints the server's stored reputation beside the local one and flags any disagreement — a local number the server does not have is exactly the bug above. It also shows whether a dialogue session is open, since since v1.52.0 talking earns nothing without one

Note

• IntelNpc_DevAllowed is exposed after the local it wraps, deliberately: a closure written above a local function captures the nil global of that name. That trap has now bitten this resource six times and is commented at the site

---

v1.53.0 — 2026-08-29

Security — a bounty could be collected without a kill

• Half health counted as death. victim_is_down compared health against a flat dead_health_max = 100, and GET_ENTITY_HEALTH's own DESC gives a player's range as [0 to 200]. So a target at exactly half health — alive, running, shooting back — read as a corpse to the bounty gate. Wound a target to 100 HP, stay within the claim radius, open the board and click: paid, with no kill anywhere in the chain. Death is now zero, and a framework that leaves downed players above zero opts in with a fraction of that ped's own maximum, which cannot be confused with a health value the way 100 was
• The damage ledger recorded hits that never landed on the victim. The weaponDamageEvent handler resolved each hit entity and passed NetworkGetEntityOwner(entity) in as the victim — but that returns whichever client is simulating the entity, normally the nearest player. Shooting the target's parked car, or an NPC standing beside them, wrote a damage record against the target with no bullet touching them. The hit now only counts when the thing hit is that player's own ped
• A bounty could be settled by a kill that predated it. The automatic payout never cleared the damage record, so a second bounty posted on the same still- down victim was satisfied by the same old record and the same body. Consuming the record would have been the wrong fix — one death legitimately settles every bounty already standing on that victim, and the manual claim is the fallback for a transient refusal — so the actual rule is stated instead: the kill must postdate the posting

Security — the SQL backend announced itself without checking

• sql_install_schema ran its statements and returned true unconditionally. sql_exec swallows a failure into a log line, so a database the resource could not write to still printed "SQL backend active" while every reputation, job and bounty write went nowhere — an owner would find out from players reporting lost progress. The tables are now proved through information_schema before anyone is told they are live, and a missing table keeps the KVP store with the reason named
• The reputation write no longer has a window where the player has nothing. It was a per-citizen DELETE followed by an INSERT from the delete's callback, untransacted: two interleaved writes left the older snapshot standing, and a crash between them lost the citizen's entire reputation. The table is keyed (citizenid, persona_id), so the write is one idempotent UPSERT, and the prune of dropped personas runs after it — the worst a crash can now cost is a stale row

Fixed — the red-light detector punished obeying the light

• "Detector B" is deleted, and nothing replaces it. It remembered that you had stopped at a light and reported you when IS_VEHICLE_STOPPED_AT_TRAFFIC_LIGHTS went false and you moved — but that is exactly what happens when the light turns green. A player who stopped at red, waited, and pulled away legally was booked for running it
• The surviving detector's header no longer calls its inference "correct". It quotes the rule it is bending — "another car stopped at a light does not prove YOUR light is red" — and carries a [NEEDS IN-GAME TEST] for whether cars queued behind you during a green discharge still read as held

Fixed — a collision module was changing headshot lethality

• SetPedSuffersCriticalHits(ped, false) ran as the first statement of the per-ped handler, before the contact test, so every human within the scan radius of any moving car lost its critical-damage multiplier. That native's DESC is "Headshotting a player no longer one shots them" — a vehicle-collision module was silently altering gunfire in a bubble around traffic. It now runs only on actual contact
• And it overwrote this resource's own configured value. spawn.lua sets that flag on every persona from persona_suffers_critical_hits, and collision wrote a guessed true back — drive past your own shopkeeper and he became headshot-killable, permanently, against the config. This is not the "we cannot know a stranger's prior value" case: the value is written down, and we clobbered it. Resource-owned peds are now skipped, using the guard that already existed

---

v1.52.0 — 2026-08-29

Security — reputation was still farmable from a modified client

• v1.42.0 moved the NUMBER to the server and left the OCCURRENCE with the client. That is not server authority — it is a client-authored occurrence with a server-authored delta. A modified client standing nowhere near anybody could fire server:repEvent(persona, 'interaction'), 'gift', 'topic' and be paid for each, then spend the standing on cheaper shop prices, reputation-gated jobs and bounty trust
• v1.50.0 made it worse. The reason families it added (interaction:<kind>) each got their own rate-limit bucket, so the 750 ms gap between reports gated nothing at all
• repEvent now pays penalties only. A positive that reaches it is discarded, and the positive table is unreachable from the network. A negative is still accepted deliberately: reputation is per-citizen, so forging one only lowers your own standing, and the reaction penalties have no other witness
• Positives now come from a path that already proved the event. A completed shop purchase, an item the server itself removed from the inventory, an interaction looked up by index in the persona's own list — each grants the reputation where it happens, through a server-only function with no net event behind it
• Talking is the one reward with no other witness, so the server opens the conversation. dialogueOpen checks the persona is real and that the player is standing at its own authored coordinates — server-owned data a client cannot move — and returns a session id. Topics are reported against it: the session belongs to one player and one persona, it expires, proximity is re-checked so walking away stops paying, each topic id pays at most once, and the whole conversation is capped. That does not make the client honest; it bounds what dishonesty is worth to what a real conversation already earns

Security — you could bribe yourself

• bribeSpawnedCop accepted any nearby ped as a police officer. It checked that the net id resolved to a ped within reach — and a player's own ped satisfies both, at distance zero. So you could name yourself as the officer and have the server take a one-star bribe and clear a real five-star level. Any passing civilian worked too
• It now refuses a player ped (walking the real connected-player list, since IS_PED_A_PLAYER is a client native), requires a police model, and requires the same routing bucket before the distance is even compared
• Every model in the list is verified against tools/refs/peds.json, the game's own index, rather than typed from memory

---

v1.51.0 — 2026-08-28

Added — the police look for the CRIME SCENE, and for the CAR

• Two things GTA V has always modelled and this resource never switched on. Both are single natives; neither is a new system.

• A crime happens somewhere, and the police now search THERE. The engine keeps a per-player wanted search centre and works outward from it. Left alone it defaults to the player — so a star effectively told the police where you were standing, and leaving the scene achieved nothing. It is now pinned to the position the crime was actually witnessed at, which the perception layer already knew and was already sending to the server; it simply was never given to the engine. Walking away from a scene is finally worth something

• SET_PLAYER_WANTED_CENTRE_POSITION 0x520E541A97A13354. R's own scripts call it with two arguments and pass GET_ENTITY_COORDS straight in — the DESC records "P2: Not set by any call" — so the `Vector3` is an IN pointer, not an out-param

• It is verified, not announced. GET_PLAYER_WANTED_CENTRE_POSITION 0x0C92BA89F1AF26F8 reads it back, and the centre only counts as pinned if the engine agrees within verify_tolerance_m. A refusal is named

• The police can be looking for your CAR. A crime committed from a vehicle now flags that vehicle, so ditching it is a real escape route rather than a cosmetic one

• SET_VEHICLE_IS_WANTED 0xF7EC25A3EBEEC726 and SET_POLICE_FOCUS_WILL_TRACK_VEHICLE 0x4E74E62E0A97E901, whose DESC reads "Sets flag on vehicle that changes behaviour in relation to when player gets wanted level"

• Neither has a getter, so the module records exactly which vehicles it flagged and clears only those handles when the star goes out. It never sweeps the vehicle pool, which would clear a flag another resource set

• Both fire only when an actor was proven (v1.48.0's attribution split), so an explosion you merely witnessed does not start a manhunt against you

• New Config.manhunt and /intel_manhunt, which prints what the engine says the search centre is rather than what we asked for

Not used, deliberately

• GET_WANTED_LEVEL_RADIUS 0x085DEB493BE80812 looks like the natural partner for the search centre. Its own DESC says "Remnant from GTA IV. Does nothing in GTA V." Read the DESC; do not pair on the name

---

v1.50.0 — 2026-08-28

Fixed — the v1.42.0 reputation migration was half-finished

• Every authored negative dialogue outcome RAISED reputation. apply_rep_delta was rewritten to report a reason instead of a number, but it reported 'topic' whatever the sign of the authored delta — and the server pays topic +1. So apply_rep_delta(session, ped, -10) for insulting a persona improved their opinion of you by one. Every negative rep_delta in the dialogue trees was inverted. The reason is now derived from the delta's sign, and a negative is bucketed by magnitude (dialogue:minor|major|severe) so authored intent survives without the client ever sending a number
• Six gameplay paths never got migrated at all and have silently not persisted since v1.42.0: target-menu interactions and gifts (target_options.lua), reaction penalties against static personas (reactions.lua, two sites), the polite-close point (reputation.lua), and the public AddReputation export. All now report a reason
• The server can price them. New reason families let the client name which authored entry fired — interaction:<kind>, reaction:<field>, dialogue:<bucket> — and the server reads the value out of the same shared Config table the content author edits. The client still never sends a number
• The trust toast had been dead. It hung off Reputation_Add; once every path started reporting, the value arrived through client:repSet → Reputation_Set, which never fired it. Moved to Reputation_Set, the one place the number changes, so every route in shows it
• exports:AddReputation now returns false and says why, instead of returning true after applying a number that vanished on the next restore

Fixed — the v1.47.0 facing cone leaked out of the HUD

• A gunshot behind a ped's back stopped being heard. v1.47.0 added IS_PED_FACING_PED to fix the panel's "Witnesses" pill, but put it in the shared ped_can_witness helper. That helper also serves collect_witnesses, and the events called with requires_los = false are called that way because they are heard, not seen — gunshot, explosion, alarm. The cone ran ahead of the line-of-sight branch, making it a stricter gate than the raycast that was deliberately declined. v1.49.0's own notes say the opposite in writing: "a gunshot is an AUDIBLE event and sound carries through walls"
• Worse for an explosion: the cone was tested against the player, so a blast 150 m away was only noticed by peds who happened to be looking at you
• The gate now applies only to seen events. The witness trace says which of the two regimes ran instead of always printing "LOS not required"

Fixed — a paid bribe never cleared the wanted level

• bribeSpawnedCop requires Config.police_system_enabled, and the client's adjustWanted handler stands aside when that is on. So on every server where the bribe was reachable at all, the server took the money and the clear was swallowed. Paid clears now go through client:wantedPaidOff, which clears unconditionally — the bribe is this module's own decision, not a foreign write

Removed

• 49 orphaned nested config keys, and the preflight harness that missed them. It checked only the 270 top-level Config.X keys and then reported "every config key is read" — but 86 of those are tables holding 661 more, none of them looked at. Config.police_ped_hit declared 27 keys and the code reads 3; the other 24 described a scripted persona-driven police reaction that has not existed since the v1.17.0 native-dispatch cut. Config.police_spawn is gone entirely — all five keys dead and nothing read the table either
• The harness now walks nested keys too, and names out loud the four tables it cannot scan because they are read with a computed key (('star_%d'):format(n) and friends) rather than skipping them silently
• Its first implementation matched only 14 of the 86 tables and reported green. A scan that sees a sixth of its subject is worse than none, because it reports success; replaced with a line-based walk that agrees with an independent check

---

v1.49.0 — 2026-08-28

Fixed

• A regression from v1.48.0, found and closed here. When dispatch_event gained its actor_is_player argument, three call sites in the polling thread — gunshot, melee and drug use — were not updated, so the argument arrived nil. Since v1.48.0 those three events have quietly had no consequence at all: no wanted level, nothing recorded in NPC memory, nothing leaked to informants. It failed silently because it removed behaviour, and the v1.48.0 harness only covered the two paths that change had touched. The harness now fails if any dispatch_event call passes fewer than four arguments

Changed — the engine knows what you fired and how to file it

• A suppressor is the whole point of a suppressor. Every shot was heard at the same 100 m whether it came from a silenced pistol or a shotgun. IS_PED_CURRENT_WEAPON_SILENCED is the engine saying one is fitted, and a suppressed shot now carries Config.perception_suppressed_range (25 m)
• A snowball is not a shooting. GET_WEAPON_DAMAGE_TYPE's own DESC enumerates the classes — 1 is "no damage (flare, snowball, petrolcan)", 3 is bullet, 5 is explosive. Only a bullet or an explosive raises a gunshot now; a flare gun used to bring the police
• The police consequence goes through GTA's own crime system. A witnessed crime became a direct wanted-level write. The engine models this: REPORT_CRIME(player, crimeType, wantedLvlThresh) files it with GTA's dispatch, which then decides the radio call, the search area and how the level builds. The crime numbers are transcribed from REPORT_CRIME's own DESC — 28 Shots fired, 22 An explosion, 11 Assault on a civilian — and GET_WANTED_LEVEL_THRESHOLD turns the configured star count into the value the native wants, so severity is still yours; it is just spent through the engine instead of written over its head
• Events GTA has no crime type for (drug use, an alarm) keep the direct path. That is not a fallback for a native, it is covering something the engine does not model — and when REPORT_CRIME itself refuses, the console says so rather than the crime vanishing

---

v1.48.0 — 2026-08-28

Fixed — a shop alarm made you a bomber

• Any explosion within 200 m was treated as the player's. A car cooking off across the street, another player's grenade, a scripted set piece — all of it handed the player a wanted star, was recorded in NPC memory as they blew that up, and leaked to informants. The detector only ever asked "did a blast happen near me", which is not the same question as "did I cause it"
• A shop alarm raised a perception explosion. That is a 200 m radius around the player: every civilian in it force-cowered for 8 seconds, the player was recorded as having caused an explosion, informants leaked it, and a wanted star was applied. A siren two streets away made the player a bomber
• IntelNpcAudio_Alarm(coords, ...) took a coordinate it never read. START_ALARM takes a name: alarms in GTA V are map-bound, the engine sounds them where they live, and there is no position to pass. Every caller handed one over and the function dropped it

Changed — three questions, asked separately

• The perception layer now separates what the NPCs observed, who did it, and whether there is a police consequence. Only a proven actor gets the third.

• The engine answers attribution, and it takes two natives together. GET_PED_LAST_WEAPON_IMPACT_COORD gives the point where the player's own last shot landed; IS_EXPLOSION_IN_SPHERE asks whether the blast is at that point. If it is, the explosion is theirs. If it is anywhere else, the engine is not claiming they did it and neither do we

• That native is published as (Ped ped, Vector3* coords) and takes one argument in Lua, returning (found, coords) — so through pcall the coord is the third value. Its DESC is quoted at the call site

• An alarm is its own event. Heard at Config.perception_alarm_range, reacted to, and on a never-attributed list that a caller cannot override. siren is there too

• Not everything makes people cower. A gunshot, blast, fight or robbery is a threat; an alarm is news. A hundred metres of civilians curling up because a shop siren went off read as a bug because it was one

• A melee is attributed to the player only when the victim resolver names someone — and since v1.47.0 that only happens off GET_MELEE_TARGET_FOR_PED or HAS_ENTITY_BEEN_DAMAGED_BY_ENTITY, so a named victim is proof

• witnessAlert now carries actor = 'player' | 'unknown', so the server can tell an observation from an accusation

• New: Config.perception_explosion_attribution_radius (5.0), Config.perception_alarm_range (100.0). Config.audio.alarm_event now defaults to 'alarm'. /intel_dev and the control panel can fire an alarm witness event to see the difference

---

v1.47.0 — 2026-08-28

Fixed — two things the script claimed that the engine never said

• The "Witnesses" pill on the dialogue panel was a body count. It counted every human within 25 m: facing away counted, behind a wall counted, inside a building counted. The panel then showed that number to the player as a fact about who had seen them. Proximity is not witnessing
• It now asks the perception layer, which runs the engine's own two-part test: IS_PED_FACING_PED first — its DESC says the angle is the ped's view cone — and the ordinary LOS raycast only on whoever passes. A clear line of sight is not having seen it: a ped with its back turned has a perfect LOS, because nothing is between you
• Cheap gate first, deliberately. HAS_ENTITY_CLEAR_LOS_TO_ENTITY_IN_FRONT does both halves in one call and is not used: its own DESC calls it "one of the most CPU demanding BOOL natives in the game; avoid calling this in things like nested for-loops", and this walks the ped pool. With twenty back-turned peds nearby the old path ran twenty raycasts; the new one runs none
• There were two definitions of "did this ped see it" — the reaction fan-out's and the panel's. There is one now, and the fan-out's was the correct one
• A forward cone was naming melee victims. When the player was swinging, whoever stood nearest inside a 0.35-dot cone became "the victim" — undamaged, untouched, possibly just walking past. That cost twice: a victim is recorded in memory as someone you assaulted, and a victim is excluded from the witness list. So swinging at air beside a bystander framed them as your victim and deleted the only person who actually watched you do it
• The cone is gone and nothing replaces it. GET_MELEE_TARGET_FOR_PED and HAS_ENTITY_BEEN_DAMAGED_BY_ENTITY are the only two answers to "who did I just hit", and when neither names anyone the answer is nobody — which is what the engine says when you swung and connected with nothing. The bystander stays a witness and reacts to the engine's shocking event, which is both correct and the better scene
• /intel_witness now reports which engine answer named each victim, and how often the player swung and hit no one
• Config.perception_victim_cone_dot is deleted with the cone it configured

---

v1.46.0 — 2026-08-28

Security — the biggest hole found so far

• Any player could clear a five-star wanted level for $200, from anywhere on the map, with no police present. Three separate defects chained:
• server:devSetPoliceEnabled was gated on Config.debug and nothing else. Config.debug ships true on purpose so a fresh install can be driven immediately — it is a development convenience, never an authorisation check, and there was no ACE check anywhere in this resource. Any connected client could fire the raw event and flip police_system_enabled server-wide, for every player on the server
• bribeSpawnedCop then had no target and no proximity check of any kind: no cop had to exist, let alone be nearby
• It priced the bribe from payload.stars, a number the client supplied. Claiming one star at a real five charged $200 instead of $75,000, rolled a 15% refusal instead of 95%, and cleared everything. bribeCop had the same pricing bug
• A refused bribe could lower your wanted level. Both refusal branches sent client:adjustWanted — an absolute level — so being refused at a real five stars set you to two, for free, with no cash taken. They now send client:adjustWantedMin, which only ever raises
• Ambient robbery paid out unverified with OneSync off. The target proof (net id, server-side entity resolve, ped check, server-measured distance, single-use Entity().state burn) was gated on onesync_enabled(), so on a non-OneSync server the whole block was skipped and loot was paid on the client's word — no ped required, roughly $450/minute. It now refuses with the cause named in the console

Changed

• The engine says how wanted you are, not the client. GET_PLAYER_WANTED_LEVEL is a CFX native with apiset: server (int GET_PLAYER_WANTED_LEVEL(char* playerSrc)), verified against the native declaration rather than assumed, so the server reads the real value. There is no fallback to the client's number — a fallback is the same lie one hop further away. If the native will not answer, the bribe is refused and the console says why
• bribeSpawnedCop now requires the cop's network id, resolves it server-side, confirms it is a ped, and enforces Config.police_patrol.response.bribe_distance_m — a key that already existed in the config and that nothing read
• Dev events are gated by an ace. Grant it in server.cfg: add_ace group.admin lastresort_intel_npc.dev allow. Nobody holds it by default, so an unconfigured server is closed rather than open; the console always holds it, which is what txAdmin and rcon use

---

v1.45.0 — 2026-08-28

Removed

• server/lifecycle.lua was a six-line no-op that looked like a safety feature. It registered entityCreating, read Config.safety_zones, returned, and never once called CancelEvent() — it blocked nothing, while a server owner reading the manifest would believe entity creation was being filtered. The file, its manifest entry and the config key are gone
• Eleven commands were offered and none of them existed. The audit named three (intel_police_spawn, intel_police_respond, intel_force_call); a mechanical sweep of every button and doc line against every registration found eight more (intel_force_precall, intel_force_fight, intel_force_flee, intel_force_curse, intel_force_flipoff, intel_hit_reset, intel_hit_dump, intel_police_state). They were deleted in an earlier "remove the dev tooling" pass which left their dev-menu buttons and README lines behind, so seven F12 buttons silently did nothing when pressed. The control panel's allowlist comment claimed it held "only the dev commands this resource itself registers", and that was untrue
• client:spawnResponsePatrol had no consumer anywhere. The server sent it on every ped-hit call; no client listened. It described a scripted responder fleet that was never built — dispatch here is the engine's. server:dispatchRequested is the real hook for another resource
• Nine config keys declared and never read. Three of them (police_wanted_watcher_*) documented a watcher that "spawns ONE scripted RP cop unit", which is precisely the thing this resource does not have; the other six were marked RESERVED and stayed that way. A key that promises a behaviour the code lacks is worse than a missing one, because an owner turns it off to stop something that was never happening

Added

• A preflight harness that keeps all of the above closed. It fails if a manifest entry names a file that is not on disk, if a .lua file is shipped but never loaded, if the control panel or the dev menu offers a command nothing registers, if the README or install guide documents one, or if a config key is declared and never read. It resolves commands registered under a name read from Config as well as literal ones — intel_bounties, intel_jobs and intelfx_demo are registered that way and a literal-only scan wrongly calls them dead

---

v1.44.0 — 2026-08-28

Fixed

• No persona has ever offered a job in conversation. fetch_offers in client/jobs.lua was missing the lib.callback.await line entirely, so the list it then tested was a nil global: the guard was always true, every fetch returned an empty offer list, and the three authored jobs were unreachable. The server sets the pending offer inside that same callback, so jobs:accept could only ever have answered no_offer as well. The whole errand system was dead content, which is why the broken quest path below had survived next to it
• Pete offered a job that did not exist. His dialogue has promised pete_paper_delivery since it was written, and there was no such job in the registry — the old quest path accepted any string, so the promise was taken and led nowhere. The job now exists, paying the $20 Pete says out loud, with English and Hungarian lines

Security

• A second quest state machine, and it was the exploitable one. server/main.lua kept a PlayerQuests table keyed by source, so it emptied on every reconnect; it was fed only by a client event, read only by a callback nothing called, and completed by nothing at all
• server:questOffered accepted any string as a quest id — no registry, no persona linkage — and paid levels.Grant(src, 'quest_accept') for each. That is twenty fabricated ids per life and a reconnect for twenty more: a bonus-minutes farm
• server:questComplete paid up to $1000 for any quest id, and nothing in this resource ever triggered it — it was reachable only by another resource on the server
• The persisted quests document it implied is written by nothing yet was still restored to the client: a third state machine that only ever existed as a shape
• All of it is deleted and nothing replaces it. data/jobs.lua plus server/jobs.lua already is the quest system and it is the better one: a job names its persona, its reputation gate, its cooldown, its steps and its reward; the server issues a time-limited offer, re-validates every step, checks proximity, and grants the levels itself. A type = 'quest' dialogue topic now goes through it

Changed

• The client stopped applying reputation locally before the server answers. Since v1.42.0 the server writes the value and announces it on client:repSet; when it refuses — rate limit, ambient persona, a reason it does not pay for — no answer comes back, so the optimistic add left the panel showing a number that was never stored. Dialogue now reports the reason and displays what comes back
• Config.reputation_quest_accept_bonus is removed. Accepting work is the jobs system's event and it pays Config.npc_jobs.accept_rep_bonus from the server; two keys for one event meant the one you edited was not necessarily the one that applied

---

v1.43.0 — 2026-08-27

Security

• A shop was not tied to the persona who sells from it. shopPrices, shopHaggle and shopBuy each took a shop id and a persona id from the client, and checked only that a catalog existed for the shop and that the player stood near the submitted persona. Nothing connected the two. Stand next to any NPC in the game, send Maggie's shop id, and you bought her goods at your standing with someone who does not own the shop — nowhere near her counter. The haggle state is keyed by shop id, so the same trick won a discount off a persona who sells nothing
• The server now decides who owns a shop, and the binding is derived from the persona data rather than written out by hand, so it cannot drift: a persona owns a shop if one of its own interactions opens it, or if its dialogue tree has a post_action that does. Two personas claiming one shop is reported at startup as the data error it is, and a catalog nobody owns says so instead of quietly selling nothing
• One resolver for all three paths. The persona is looked up from the shop id; the persona the client sent is compared against it, logged when it disagrees, and then discarded. Proximity is checked against the owner, and the price comes from your standing with the owner
• client/dialogue.lua carried a hardcoded fallback shop id. A buy_item step with no shop of its own charged against Maggie's catalog, whoever you were talking to. It now asks the persona which shop it sells from, and a persona that sells nothing gets no purchase rather than someone else's. client/interaction.lua likewise stopped passing a persona id off as a shop id
• Two server-side reputation grants still went through the client. Job rewards and the haggle-insult penalty were sent to the client as a delta for it to apply. Since v1.42.0 stopped the save flush accepting client-written reputation, those two silently stopped persisting at all — a job could pay out standing that vanished on reconnect, and insulting a shopkeeper cost nothing. Both now call the server's AdjustReputation and announce the stored value on client:repSet. The client:npcReputation event is deleted at both ends: there is one writer of reputation and it is the server

---

v1.42.0 — 2026-08-27

Security

• Reputation was whatever the client said it was. The save flush (persistFlush) took a whole snapshot from the client and wrote each table through verbatim. Reputation gates shop prices, job eligibility and who may place a bounty, so a player could set their standing with any persona to anything and then buy at that price. quests and lastBribe went the same way, gating progression and cooldowns
• The flush now accepts narrative memory and nothing else. Memory decides which lines an NPC has available; nothing on the server reads it to decide whether money moves, so the client may still own it. Every other key in the snapshot is refused and the refusal is named in the log
• Reputation changes go through one server function. AdjustReputation reads the stored value, applies a single delta, clamps it to −10…+10, saves, and returns what it actually stored. It is the only path that writes reputation
• The client reports a REASON, never a number. repEvent takes a persona and a reason word (interaction, topic, gift, quest_accept, or a penalty); the server looks the delta up in its own table. A reason it does not pay out for changes nothing. Ambient personas are refused server-side as well as client-side, and each player is rate limited per persona and reason
• The client is told the value it ended up with. client:repSet pushes the canonical number back, so the panel shows what the server agrees with rather than a number the client made up

Changed

• Ducking no longer has a "panic release". STOP_AUDIO_SCENES() takes no arguments and drops every audio scene on the client, including another resource's phone call, cutscene or interior mixer. A scene that will not stop is now retried by name, then ducking stands itself down for the session and says which scene did it. A feature that switched itself off with a named cause beats a client whose audio we silenced

---

v1.41.0 — 2026-08-27

Security

• Bounties paid out on a claim the victim's own client made up. bountyDeathReport(killer_server_id) took the killer's server id from the victim, and that name was the only evidence behind every payout. Nothing proved the victim had died, and nothing tied the named killer to the death. Two players standing next to each other, one carrying a bounty, could mint money without a shot being fired
• Three server-side facts now replace it, and all three must hold. Damage: a weaponDamageEvent ledger, fed from the attacker's side of the wire, naming this victim recently — a victim can no longer nominate anyone. Death: the server reads the victim ped's health itself. Instance: GetPlayerRoutingBucket must match, so two players in different instances at the same coordinate cannot satisfy each other's proximity check
• The client death report survives only as a TRIGGER. It makes the server go and look, and it now carries no arguments at all — there is nothing left in it to forge. The client-side helper that read the last damager is deleted
• One gate, both paths. The automatic payout and the manual claim call the same kill_is_proven(), so there is exactly one definition of "this player killed that player" and it lives on the server. Every refusal names its cause in the log instead of failing silently
• The payout is atomic. The bounty moves open → claiming → paid and is taken off the board before the money moves, so two claims landing in the same tick cannot both pay. A failed payout returns it to open rather than losing it. open_bounties() now excludes anything mid-payout
• Config.bounty_board.damage_ledger_ttl_ms (120000) and dead_health_max (100)

Verification

• 15-check harness, proven by reintroducing the exploit: 3 failures. It also asserts the two forward-reference orderings that this codebase has been bitten by before — cfg() before the ledger uses it, and killer_is_over_victim before the gate that calls it. Both were briefly wrong while writing this and were caught the same way

---

v1.40.0 — 2026-08-27

Fixed

• The collision survivability floor HEALED a dying ped. apply_floor() set health to survive_floor (110) whenever post-impact health was below it, with no check against pre-impact health. A ped already dying at 10 HP, clipped at 5 km/h, was set to 110 — the impact healed it by a hundred. The rule is "a light knock does not kill", not "a light knock is a medkit": the floor can now at most undo the damage that impact caused
• The wanted clamp lowered OTHER resources' wanted level. A 250 ms watchdog pulled any level above this module's ceiling back down, whoever set it — its own trace said "something outside this resource set N stars; clamped back". A heist granting four stars was dragged to two and the engine's higher-tier response disappeared
• Our own requests were already capped at the source in set_wanted_clamped() and still are. The watchdog now observes and reports; it never writes. Config.police_wanted_clamp_enabled → Config.police_wanted_observe_enabled
• Config.perception_enabled = false was overwritten back to true. if not X then X = true end also catches an explicitly configured false, so the switch could not be turned off. Now == nil
• Reading a vehicle seat SPAWNED a ped. client/world_ambience.lua called GET_PED_IN_VEHICLE_SEAT with no IS_VEHICLE_SEAT_FREE guard, and that native's own DESC says: "If there is no ped in the seat, and the game considers the vehicle as ambient population, this will create a random occupant ped in the seat." The radio-candidate scan was increasing the population as a side effect of looking. client/collision.lua already guarded this correctly; the same guard is now used

Changed — ownership

• STOP_AUDIO_SCENES() and STOP_ALL_ALARMS() are gone. Both take no arguments and drop everything on the client, including scenes and alarms other resources started. v1.38.0 shipped the first as "the panic release", which was exactly the kind of plausible-sounding unverified claim to avoid
• The duck now retries the named stop, and if that will not clear it says so and disables ducking for the session rather than reaching for a global. Resource stop releases only our own scene; the probe never escalates
• client/audio.lua stops only the alarms it started, by name
• lua54 'yes' removed. It is not required, verified against the official Cfx manifest docs: "This setting is deprecated and you do not need to enable it. As of June 2025, Lua 5.3 has been deprecated and all Lua scripts now use the 5.4 version."

Documentation

• A native is not safe merely because it is native. Decide who owns the state before writing it. Never use a global cleanup native to release a local claim. With no getter and no proof of the previous value, do not guess
• Do not present an inference as an engine fact. Proximity is not witnessing; a nearby explosion does not prove the player caused it; another car stopped at a light does not prove your light is red

---

v1.39.0 — 2026-08-27

Added

• A5 · Red-light posts — an officer standing at a lit junction, watching traffic. There is no coordinate table anywhere in it. GTA's own map data says which road nodes are junctions and which of those are light-controlled, so the feature reads the map instead of shipping a list of places
• Two bits, not one. eVehicleNodeProperties carries JUNCTION = 1 << 7 (128) and TRAFFIC_LIGHT = 1 << 8 (256), and both are tested. A junction without lights is a stop-sign post, not a red-light one — the existing red-light detector only ever needed bit 8, so bit 7 had never been read
• The post goes on the pavement via GET_SAFE_COORD_FOR_PED and is then proved off the road with IS_POINT_ON_ROAD. If it is still on the road, no officer is placed at all rather than one standing in a traffic lane. A Vector3.Zero return is treated as "found nowhere", never as the origin
• The officer gets the engine's own scenario at that position, with a negative timeToLeave — which the parameter's own description documents as setting IdleForever, not an undocumented idiom. IS_PED_USING_SCENARIO says whether it actually took
• GET_STREET_NAME_AT_COORD supplies the post's name and a second, independent witness that a coord is an intersection: crossingRoad is non-zero only where two named roads meet, which the engine computes by a different route than the node flags
• /intel_junctions — read-only. Prints what the map says about every road node around you: junction or not, lit or stop-sign, lane count, street names. The junction finder can be checked without placing anything
• /intel_redlight, /intel_redlight_test, /intel_redlight_clear, Config.redlight_post, a module switch in F12 → Modules, and a Red-light posts group in Try this

Verification

• 40-check harness. All three out-param traps are exercised individually, because each is silent:
• GET_VEHICLE_NODE_PROPERTIES returns a BOOL plus two out-params, so flags is the fourth pcall value — the harness feeds density 15 and asserts it is not mistaken for flags
• GET_NTH_CLOSEST_VEHICLE_NODE_WITH_HEADING is published with ten parameters and takes seven in Lua — the harness asserts the arity and that the fifth argument is the search flags, not a position
• GET_STREET_NAME_AT_COORD returns void, so there is no leading found-flag — the harness asserts the street is the first returned value and the crossing road the second

---

v1.38.0 — 2026-08-27

Added

• C7 · Ducking — the world gets quieter while an NPC is talking to you, and the ENGINE does it. START_AUDIO_SCENE activates one of GTA's own dynamic-mixer scenes and the game lowers ambience, radio and score by its own rules. No volume is touched by hand, and nothing is faked if the engine refuses
• The RELEASE is what gets verified. A duck that fails to start is a quiet feature; a duck that fails to stop leaves the whole world muffled and nothing else would ever notice. Every release is read back with IS_AUDIO_SCENE_ACTIVE, and a scene that will not stop escalates to STOP_AUDIO_SCENES() with a loud console line saying whether that cleared it
• A watchdog releases a duck held past max_hold_ms, and onResourceStop calls the panic release unconditionally — bookkeeping cannot be trusted on the way out
• Anchored on the panel's open/closed transition, not on focus. IsOpen was written in five places and set_focus in six, including the public IntelNpcNui_SetFocus wrapper — a fifth entrance that is easy to miss. All five assignments now run through one set_open(), so a conversation that ends down a path nobody thought of still releases the mix
• The player's phone radio is snapshotted and restored to what it was — never switched on for someone who had it off
• /intel_duck_probe — scene names cannot be validated. No native and no Rockstar dump lists the mixer scenes a build ships, so unlike ped models and scenario names they cannot be checked at build time. Each candidate is started, read back, and stopped again, and the results printed. Re-probing clears the session's remembered refusals so it genuinely re-tests
• /intel_duck, Config.dialogue_duck, a module switch in F12 → Modules, and a Ducking group in Try this
• 34-check harness, including the stuck-release path and the case where the panic release itself fails

Fixed

• A remembered winning scene was reused even after it had been removed from Config.dialogue_duck.scenes. Caught by the harness, not in play

---

v1.37.0 — 2026-08-27

Added

• C3 · Gestures — and the answer was that the engine already does them. GTA V gestures a ped automatically while it speaks: the gesture layer rides on ambient speech, picks clips from the ped's own gesture group, and needs no animation dictionary, no clip name and no task. We had simply never switched it on
• Of the seven natives in the SET_PED_CAN_PLAY_* family this resource called exactly one. SET_PED_CAN_PLAY_GESTURE_ANIMS — the one the whole feature turns on — had never been called anywhere in the codebase
• Now switched on for a ped as its line begins, along with the base ambient clip a gesture layers over, lip-sync (SET_PED_CAN_PLAY_VISEME_ANIMS), arm IK (gestures are arm motion; IK off damps them), and SET_PED_CAN_USE_AUTO_CONVERSATION_LOOKAT — the engine aiming a speaking ped's head at whoever it is talking to, by itself. That last one is the native version of what client/lookat.lua does by hand for bystanders, at one call instead of a watcher
• Nothing here is a task. These are per-ped capability switches, so no scenario, patrol or conversation can be cancelled by them — the harness asserts that no task native and no REQUEST_ANIM_DICT is ever issued
• SET_PED_CAN_PLAY_AMBIENT_IDLES is deliberately not used: its first bool is bBlockIdleClips, so its polarity is inverted and calling it with true would block exactly what the others enable
• SET_PED_GESTURE_GROUP can give each archetype its own gesture vocabulary, so a gang member and a shopkeeper move differently without one animation played by hand. Off by default — the group names are not enumerated anywhere in the native database, and an unknown one degrades to the ped's default rather than breaking
• /intel_gestures_why — none of the seven switches has a getter, so "did it take" is not readable. What is readable is the driver and the causes, and this reads all of them from the engine: the model's ambient voice (GET_AMBIENT_VOICE_NAME_HASH — no voice, no speech, no gesture), whether another resource muted the ped (IS_AMBIENT_SPEECH_DISABLED), config flag 17 holding them still, and whether they are speaking at all
• /intel_gestures, Config.gestures, a module switch in F12 → Modules, and a Gestures group in Try this
• 32-check harness

---

v1.36.3 — 2026-08-27

Build tooling

• Not shipped — tools/ is excluded from the Tebex package.

• Scenario names now fail the build too, like model names. v1.33.1's note claimed scenario names had been validated at build time "since the start". They had not: generate.js builds the whitelist from scenariosCompact.json, and the only check on the names the resource actually uses was at runtime — client/life_points.lua warns and drops an unknown one, so the ped simply never appears and the message scrolls past

• All 237 scenario names in the resource were swept against the game's 247-entry dump: every one is real, so nothing was broken. The gap was that the next typo would only have surfaced at runtime

• Proven both ways, like the model check: the clean tree passes, and a reintroduced typo fails the build with file, line and a suggestion

Documentation

• An out-param in the MIDDLE of the published signature is dropped from the Lua argument list. GET_CLOSEST_VEHICLE_NODE_WITH_HEADING is published with 8 params and takes 6; GET_NTH_CLOSEST_VEHICLE_NODE_WITH_HEADING 10 and takes 7; GET_SAFE_COORD_FOR_PED 6 and takes 5
• A void native has no leading status. GET_STREET_NAME_AT_COORD yields both values through out-params, so pcall gives (ok, street, crossing)
• An out-param's name is not its meaning. GET_CLOSEST_ROAD's width is the median gap between forward and backward lanes, not the road's width
• Road nodes: JUNCTION is bit 7 (128) and TRAFFIC_LIGHT is bit 8 (256) — only the second is currently used, and a junction without lights is a stop-sign post rather than a red-light one. GET_SAFE_COORD_FOR_PED wants flags = 16 (its own DESC: "16 works for me, 0 crashed the script"), and a false return means abandon the placement, never fall through to the origin

---

v1.36.2 — 2026-08-27

Fixed

• Hit an officer and he could not shoot back — he had been disarmed for good. The band recorded GET_CURRENT_PED_WEAPON, which reports the equipped weapon. A cop on patrol carries his pistol holstered, so that returned WEAPON_UNARMED, nothing was recorded, RemoveAllPedWeapons stripped the pistol anyway, and release handed back nothing
• GET_BEST_PED_WEAPON(ped, ignoreAmmoCount) answers what he has, not what is in his hand, and is what gets recorded now
• The hand-back is read back: HAS_PED_GOT_WEAPON confirms it, with p2 false because the native's own DESC says it otherwise always returns false. If the engine refuses, the console says so and names the officer
• Config.police_nonlethal.restore_ammo (default 200)
• Punching a civilian made them fight you to the death. client/reactions.lua calls IntelPolice_MarkSelfDefence for every ped the player damages within 30 m, and neither end checked for a cop. So any struck pedestrian got SetPedAsEnemy + TaskCombatPed — a primary task that clobbers whatever the archetype system had just decided. A coward fought to the death like everyone else
• Self-defence is a rule about officers leaving the non-lethal band. The guard now lives inside IntelPolice_MarkSelfDefence, so both call sites get it, and a civilian's answer goes back to client/reactions.lua where it belongs

Verification

• New 13-check harness that drives the module's real enforcement loop rather than poking at internals. Both fixes were reverted in turn to confirm it fails on each: 3 failures for the holstered pistol, 3 for the missing cop guard

---

v1.36.1 — 2026-08-27

Fixed

• Police shot at one star. Two separate bugs, both real.
• The band was switched off by default, by something unrelated. band_should_apply() required Config.police_system_enabled, which ships false. That flag belongs to the alpha module that decides when you get stars; this band decides whether police shoot at the stars vanilla GTA hands out on its own. Coupling them meant the band never applied out of the box — the exact thing the file exists to prevent. They are now independent; Config.police_nonlethal.enabled is the only switch that governs it
• The wrong combat attribute was being set, off by seven. The code wrote SetPedCombatAttributes(ped, 46, true) with the comment -- CA_CAN_BUST
• CA_CAN_BUST is 39. 46 is CA_CAN_FIGHT_ARMED_PEDS_WHEN_NOT_ARMED
• So every held officer was disarmed and then told "you may take on armed people while unarmed", and was never told he may arrest. Release then cleared 46 — a flag this module never meant to touch
• data/ped_flags.lua has carried the verified numbers since v1.15.4, when five of them were last found wrong. This file was bypassing that table with raw integers. It now uses the named constants, and no file anywhere passes a bare number to SetPedCombatAttributes

Verification

• New 27-check harness. It extracts R*'s own eCombatAttribute enum from SET_PED_COMBAT_ATTRIBUTES' description and checks every entry in data/ped_flags.lua against it by name, so an off-by-seven cannot survive again. It also fails the build on any raw integer passed to that native

---

v1.36.0 — 2026-08-27

Changed

• The engine has a witness system, so the engine does it now. v1.35.0 found ADD_SHOCKING_EVENT_* / TASK_SHOCKING_EVENT_REACT and documented them while shipping a hand-rolled fan-out next to them. That was the wrong call and it is reversed
• Every assault now raises a real GTA shocking event on the victim (ADD_SHOCKING_EVENT_FOR_ENTITY), confirmed with IS_SHOCKING_EVENT_IN_SPHERE. The engine propagates it, decides how far it carries, and who notices — including peds this resource never looks at
• The visible reaction is played by TASK_SHOCKING_EVENT_REACT: the ped's own reaction set, its own animations, its own personality. scream_flee, walk_away_cursing, stand_ground and comply are no longer tasks we issue
• Nothing is hand-built when the engine refuses. The console names the cause and the crowd simply does not react
• What is still ours is only the cast layer — gang solidarity, same-set backup, and calling the police module. The engine has no concept of "his set got slapped" and does not know our police module exists
• Config.cast_witness.shocking_duration; the event kind is selectable (melee, shot, run_over, killed, …) and picks one of the engine's own eEventType values

Added

• /intel_witness_native — settles the one thing that was still unproven, on your build. Raises a real shocking event and asks every nearby ped what HAS_PED_RECEIVED_EVENT says at 0.5s, 1.5s and 3s, alongside how many are visibly reacting. Each of the three possible outcomes is spelled out
• /intel_witness — engine events raised vs refused, and reactions played by the engine vs by us

Fixed

• A refused event left the PREVIOUS one live, so peds were tasked to react to an assault that had already finished. Caught by the harness, not in play

---

v1.35.0 — 2026-08-27

Fixed

• Every witness reacted on the SAME FRAME. Eight bystanders screaming and bolting in perfect unison was the most artificial-looking thing the system did
• Reactions now travel outward from the victim, nearest first, over about a second. The decision is still synchronous — who reacts, how, and the gang-attacker cap are all settled in one pass, so nothing races; only the visible reaction is deferred
• A witness who has vanished, died, or started panicking before their turn comes round is skipped rather than tasked
• react_delay_base_ms / react_delay_spread_ms / react_delay_jitter_ms
• A clear line of sight is not the same as having seen it. A ped standing with its back to you has a perfect line of sight — nothing is between you — so people facing the other way, thirty metres off, reacted to things they could not possibly have seen
• IS_PED_FACING_PED (0xD71649DB0A545AA3) gates it now; its own documentation says the angle is the ped's view cone
• HAS_ENTITY_CLEAR_LOS_TO_ENTITY_IN_FRONT does both halves in one call and was rejected on its own DESC: "one of the most CPU demanding BOOL natives in the game; avoid calling this in things like nested for-loops." The collector walks the whole CPed pool. So the cheap angle test gates first and the LOS raycast only confirms what passed it
• require_facing (default true) and view_cone_deg (default 120)
• The trace now separates three numbers that were one: how many saw it, how many were in range but facing away, and how many had no line of sight
• The inspect panel said "these five" under six rows. The sixth is a different kind of refusal that had been filed with the rest: the other five are setters we write and cannot read back, while GET_PED_SCRIPT_TASK_COMMAND is a native that does not exist at all
• The two are now stated separately, and the count is derived from the list rather than typed, so it cannot drift again
• All six claims re-verified against the native database: the five setters exist with no getter in any namespace, and GET_PED_SCRIPT_TASK_COMMAND is genuinely absent — GET_SCRIPT_TASK_STATUS only answers "is this task running", one hash at a time, which is what the "our task" row above asks it

Documentation

• docs/NATIVE_AUDIT.md §8.8, including §8.8.1: the engine has its own witness system (ADD_SHOCKING_EVENT_*, TASK_SHOCKING_EVENT_REACT, IS_SHOCKING_EVENT_IN_SPHERE), recorded with hashes so it is not re-investigated from scratch. It could replace the perception half outright; it cannot replace the casting half, because the engine has no concept of "his set got slapped". Blocked on the HAS_PED_RECEIVED_EVENT MP read-back that §7 already flags

---

v1.34.0 — 2026-08-27

Changed

• The "They are getting worked up" provoke meter is OFF by default. It landed in the screen centre, over the face of the NPC you were provoking — the one place a HUD element is most in the way
• The signal is not lost. The ped's own reaction is the signal; the 3D overlay shows the irritation ladder against its threshold; and inside a dialogue the same thing already goes into the panel's chat stream instead, which is unchanged
• Config.simpleasf.provoke_meter = true brings it back, and there is now a switch for it in F12 → Modules

Added

• A master switch for the whole simpleasf FX layer in F12 → Modules (Config.simpleasf.enabled). Toasts, banners, wanted stars, dispatch cards, achievement surfaces — all of it off in one click. Nothing stops working; it stops drawing
• A On-screen surfaces group in Try this

---

v1.33.2 — 2026-08-27

Fixed

• /intel_status reported scan: 0 runs in a way that reads as broken when it usually is not. Chasing that line in a real log cost a detour: life points scan every 15s after a 3s boot delay, street scenes every 20s after a 6s one, so any status printed inside the first interval honestly shows zero
• Four states were collapsed into one number. They are now told apart: the module is switched off; the scan loop never started (its data failed to load, and it already warns separately); it has not come round yet, now printed as none yet — first scan in 12s, then every 15s; or it has genuinely run
• 8-check harness holding the four apart, including the exact case from the log

---

v1.33.1 — 2026-08-27

Fixed

• Four life points were spawning the wrong people, silently. This is the validation drops: 0 scenarios, 4 models line in /intel_status — the runtime was catching it and saying so; nothing had gone back and fixed the names
• a_m_y_tourist_01 and a_m_y_tourist_02 do not exist. There is exactly one male tourist in the game index: a_m_m_tourist_01
• s_m_y_busker_01 does not exist — the busker is s_m_o_busker_01
• g_m_y_ballas_01 does not exist (dev menu) — the Ballas street ped is g_m_y_ballasout_01
• Affected downtown_tourist, vinewood_blvd_tourists, del_perro_promenade_tourists and vespucci_boardwalk_performers
• Verified against the game's own ped index (1109 entries), not from memory

Build tooling

• Not shipped — tools/ is excluded from the Tebex package.

• A wrong model name is silent, and now it fails the build. At runtime IsModelInCdimage says no, lib.requestModel never loads it, and CreatePed substitutes a default civilian — so nothing errors and the wrong person simply stands there

• Scenario names have been validated against scenariosCompact.json since the start, which is exactly why the runtime reported 0 scenario drops and 4 model drops. Model names had no such check. Now they do

• tools/fetch_refs.sh also fetches peds.json; tools/generate.js fails the build on any model name not in it, naming the file, the line, and the real alternatives (s_m_y_busker_01 → did you mean: s_m_o_busker_01)

• Proven in both directions: clean tree passes with 65 distinct names across 104 files; each removed fix is caught again when reintroduced

---

v1.33.0 — 2026-08-27

Fixed

• A SWAT officer, a soldier, a paramedic, a fireman and every ped another resource spawns were all "coward". DefaultArchetypeByCategory.default was 'coward', and that table is the last word for any ambient ped
• Utils.get_ped_category names six things — civilian, cop, gang, homeless, prostitute, animal — and returns 'default' for everything else. That is nine of the thirty ePedType values: dealer, medic, fireman, criminal, special, mission, SWAT, army, and any prostitute not listed by model. All nine landed on the catch-all
• PED_TYPE_MISSION is the one that made it look universal: it is what peds created by other scripts generally are
• The catch-all is now stoic. An unrecognised ped is not a coward, it is unremarkable — and stoic was already fully specified in every provoke, reaction and mood table, so nothing else had to move
• Reactions_GetArchetype returned 'coward' for a ped that does not exist. Also stoic now

Added

• ArchetypeByPedType — consulted only when the category came back default, so dialogue, hails, street scenes and life points (which all branch on the category) are untouched. It changes how a ped reacts, nothing else. Medic → compliant, fireman → brave, dealer and criminal → aggressive, prostitute → cunning, SWAT and army → cop. SPECIAL and MISSION are left out deliberately: a mission ped is whatever another resource made it, so there is nothing honest to say about its temperament
• This is also the first time brave and cunning reach an ambient ped at all. The panel has always advertised seven archetypes; only four could ever be assigned
• Reactions_GetArchetypeWhy(ped) returns the archetype and the decision that produced it. The inspect panel now prints it under the archetype row: a persona that names one, the category, the raw ped type, or the fallback admitting it is a fallback
• /intel_archetypes — a census of everyone within 80 m grouped by archetype, by what decided it, and by GET_PED_TYPE. "Why is everyone the same?" is now a table rather than a hunch
• 22-check harness covering the resolution order, all nine previously-miscast ped types, and that every archetype named is one that actually exists

---

v1.32.0 — 2026-08-27

Fixed

• Crime scenes deleted themselves six seconds after the engine accepted them. /intel_scene_diag reported CreateIncidentWithEntity ... after 3s: valid=1 in the same session where /intel_scene_test printed "CREATE_INCIDENT would not take this scene". Both were right; the module's conclusion was wrong
• IS_INCIDENT_VALID is conclusive at exactly one moment: right after the create, where invalid can only mean refusal. Read later it is ambiguous — an incident the engine has finished with is retired and reads invalid exactly like one it dropped. The module re-read it at six seconds, treated the stale id as a refusal and called IntelNpcIncident_Close(...), which destroyed scenes the engine had accepted and was working
• Acceptance is now decided at the create. Nothing that happens afterwards can delete a scene that the engine took
• "Did anything actually turn up" is now measured instead of inferred. GET_VEHICLE_CLASS returns 18 for Emergency — ambulance, police and fire, from the native's own enum — so a scan of the vehicle pool answers it without naming a single model. /intel_scene_state reports the count of emergency vehicles standing at live scenes, separately from the wanted-level counter, which only ever counted units sent after you
• The refusal message no longer tells you to run a diagnostic that has already answered its question

Added

• /intel_scene_why — four probes, one variable each, for when scenes are accepted but nothing arrives. A bare incident; the same plus the SET_INCIDENT_REQUESTED_UNITS call; one anchored on a bystander instead of you; one raised while another is already open. Each samples IS_INCIDENT_VALID on a ladder out to twelve seconds and prints the millisecond it died at, then the verdict names which variable shortened it — or says plainly that none of them did
• Config.crime_scene.responder_scan_radius (default 140.0)
• Crime scenes now have a Try this group, and docs/NATIVE_AUDIT.md gains §8.7, which corrects §8.5

---

v1.31.0 — 2026-08-27

Added

• C4 · The street looks over. Shove somebody until they snap, or hit somebody, and the people around it now glance at you — then carry on with whatever they were doing
• Nothing is spawned and nobody is tasked away from what they were doing. TASK_LOOK_AT_ENTITY is a secondary task: head IK layered over the ped's existing task. A ped mid-scenario keeps its scenario and still turns to look. That is the exact opposite of the v1.29.0 crime-scene bug, where a turn task issued after a scenario silently cancelled it
• This is the cheap half of "people noticed". The crowd director (Config.crowd) is the expensive half — it recruits people, walks them into a ring and holds them there. Right for a body in the street, far too much for a shove that is over in ten seconds
• Verified, not announced. IS_PED_HEADTRACKING_ENTITY is a real getter, so /intel_lookat prints asked vs. engine-confirmed. A gap between the two is honest: the engine declined those
• Capped at 5 heads per moment within 16 m, with an 8 s per-ped cooldown, so it cannot be spammed into a staring crowd
• Config.look_at block, a module switch in F12 → Modules, a panel section under F12 → Actions, /intel_lookat and /intel_lookat_test
• Covered by a 28-check harness (cap, cooldown, eligibility, refusal reasons, that the confirmed count is the engine's and not the script's, and that no task capable of clobbering another one is ever issued)

---

v1.30.0 — 2026-08-27

Fixed

• The resource spiked to 0.25 ms in resmon, against a documented ~0.02 ms ambient budget. That was v1.23.0's basic 3D overlay, and it was mine. Making it the default was right; reading its contents inside the frame tick was not
• The basic overlay shows a dozen things per ped — three state latches, the irritation ladder against its threshold, per-ped rep, whether a voice was cast over the model's own, the driver archetype, in-combat, fleeing. Measured from the source: 21 state reads per ped. Inside a 60 fps frame tick with twenty pedestrians on screen that is 25,200 reads per second
• Drawing has to be per frame. Reading does not — none of it changes faster than a person can read a two-row label. The overlay now collects a snapshot on a 250 ms interval and the frame tick only draws it: 1,680 reads per second, a 15× reduction, with zero state reads left in the per-frame path. Both numbers are measured from the shipped source, not estimated
• client/mood_icon.lua had always worked this way — precompute on an interval, draw from the list. The overlay now matches it
• Config.debug_3d_refresh_ms (default 250) tunes it. 'full' mode stays deliberately uncached: you turn that on to stare at one NPC, not to walk down a street with it
• Costs nothing at all with Config.debug off, as before

---

v1.29.2 — 2026-08-27

Fixed

• Crime scenes never opened, and the diagnostic found out why. Measured on b3751 with /intel_scene_diag, both dispatch services, repeatable:

• | Form | valid immediately | valid after 3 s | |---|:--:|:--:| | CREATE_INCIDENT(svc, x, y, z, units, radius) | yes | no | | CREATE_INCIDENT(..., 0, 0) — 9-param | yes | no | | CREATE_INCIDENT_WITH_ENTITY(svc, ped, units, radius) | yes | yes | | CREATE_INCIDENT_WITH_ENTITY(..., 0, 0) | yes | yes |

• Our hypothesis was wrong. The native database's "NativeDB Added Parameter 8 / 9" note made the extra parameters the obvious suspect. Both arities behave identically — the arity is irrelevant. (The false, false variant raises bad argument #1 to '_ii' (number expected, got boolean): those parameters are ints in the Lua binding whatever they mean, so that form is dropped from the diagnostic.)

• The discriminator is entity versus coordinates. An incident on bare coordinates is valid for an instant and gone within three seconds; one on a ped stays valid. client/incident.lua now always uses the entity form, and a scene opened on a place borrows the nearest ped within anchor_search_radius as its anchor — at a crime scene that is a bystander, which is the right thing to point dispatch at anyway

• Dispatch health was confirmed alongside and was not a factor: CanCreateRandomCops() = true, GetMaxWantedLevel() = 5, all fourteen services enabled

• Recorded in docs/NATIVE_AUDIT.md §8.5, marked [NEEDS RE-TEST AFTER A GAME UPDATE] — this is build-observed behaviour, not documented behaviour, and /intel_scene_diag reproduces the whole table in about forty seconds

---

v1.29.1 — 2026-08-27

Added

• /intel_scene_diag — measure CREATE_INCIDENT instead of guessing at it. The native database lists CREATE_INCIDENT with seven parameters and then notes "NativeDB Added Parameter 8: Any p7 / Added Parameter 9: Any p8" — newer builds take two more than the published signature, and CREATE_INCIDENT_WITH_ENTITY gained two as well. Which arity a build wants is documented nowhere, and calling the wrong one fails silently
• The diagnostic calls every form — 7-param, 9-param with ints, 9-param with bools, and both arities of the entity variant — against both the ambulance and police services, prints each one's raw returns, and checks the incident immediately and again after three seconds. A form that returns true and stays valid is the one this build wants

Changed

• The "no scene" message now says what is actually wrong. It used to list things to go and check. It now asks IntelNpcEnginePolice_State() first and names the real cause: the engine police stack standing down and why, something on the server switching police off (with the resource named), the stack not having asserted dispatch yet, or client/engine_police.lua not being loaded at all. Only when dispatch genuinely looks healthy does it point at the native itself and at /intel_scene_diag

---

v1.29.0 — 2026-08-27

Removed

• The crime-scene dressing. client/incident.lua no longer spawns three peds on medic and investigation scenarios when CREATE_INCIDENT refuses. If the engine will not take the incident there is no scene, and the console says what to check: dispatch services on (Config.engine_police) and a road the engine can drive a vehicle down. Config.crime_scene.dressing and max_dressing are gone
• The scripted patrol walker. client/patrol.lua no longer walks a route from Lua when TASK_PATROL refuses the task — a scripted route-walker is not the engine doing it, it is us pretending the engine did. A guard the native refuses simply does not patrol, and /intel_patrol_diag measures all eight parameter combinations and reports whether any works on this build. Config.patrol.walker_fallback, walk_timeout_ms and arrive_radius are gone
• The script-side wanted level. client/police.lua no longer raises a star itself when REPORT_CRIME does not. The engine owns the decision — did an officer witness it, does it warrant a star — and if it says no, you do not become wanted. The wanted level is still read back afterwards, but only so the trace can report which happened. Config.police_crime_reporting and its 'script' / 'verified' modes are gone

Where the resource now stands on this

• Of the seven city-life modules, six spawn no peds at all and do their work entirely through natives — crowd, traffic, audio, collision, crime scenes and the engine police stack. client/patrol.lua is the only one that creates a ped, and only to populate a route you asked for or a test command you ran.

• The harnesses were rewritten to assert the new contract rather than the old one: a dropped incident produces nothing at all, a refused TASK_PATROL produces neither a scripted walk nor a substitute scenario, and the refusal is counted and reported in both cases.

---

v1.28.1 — 2026-08-27

Fixed

• The crime-scene peds stood doing nothing. dress() issued TaskTurnPedToFaceCoord after TaskStartScenarioInPlace, and tasks replace each other — so the ped turned to face the scene and the scenario was cancelled on the same tick. They now face the scene by spawn heading and no turn task is issued at all. Asserted, along with a sweep confirming no other module has the same ordering
• Every crime scene fell back to hand-dressing, even when the engine had accepted the incident. The verify required _GET_NUM_DISPATCHED_UNITS_FOR_PLAYER > 0, but that native counts units sent after the player — a wanted-level response — so an incident that has nothing to do with the player correctly reads zero there. IS_INCIDENT_VALID is the authority and is now the only condition; the unit counter is reported as context rather than used as a gate. This is why /intel_scene_state read "0 run by the ENGINE, 3 dressed by hand"
• NPC chatter was landing in the chat's SYSTEM channel. Config.integrations.chat.feed wrote every bubbled line with a plain chat:addMessage carrying a colour and two args and no template — and stock chat, qb-chat and ox_chat each decide for themselves what an untyped message is, with several filing it under system. A passer-by muttering about the weather showing up as a system message is worse than it not showing up at all, and it was the default. It now defaults to false and is strictly opt-in for a server that has checked where its own chat puts the line. The 3D bubble above the ped is the intended surface and is unaffected

---

v1.28.0 — 2026-08-27

Added

• Config.crime_scene (client/incident.lua) — A4, crime scenes. The brief described hand-placing a paramedic on CODE_HUMAN_MEDIC_KNEEL and an investigator on CODE_HUMAN_POLICE_INVESTIGATE: scenery that looks right and does nothing. Searching the natives first found an entire incident system underneath that
• CREATE_INCIDENT_WITH_ENTITY(service, ped, units, radius, &id) raises an incident on a body and the engine dispatches real units — an ambulance that drives there with its siren on, paramedics who get out and work the body, police who secure the scene. All pathed, animated and owned by the game, for one native call. SET_INCIDENT_REQUESTED_UNITS adds the police to the same incident rather than raising a second one
• Two getters make it honest. IS_INCIDENT_VALID says the incident still exists and _GET_NUM_DISPATCHED_UNITS_FOR_PLAYER says whether anything was actually sent, so "the engine handled it" is checked rather than announced. When the engine sends nothing — dispatch off, no road nearby — the hand-placed scenario dressing from the original design runs instead, and the trace and /intel_scene_state say which of the two you are looking at
• The onlookers are still ours: no native gathers bystanders around a body, so that goes to the crowd director, which borrows pedestrians who are already there
• /intel_scene_test and /intel_scene_state; also in Try this
• 22 assertions: the incident is raised on the body for the ambulance service, police join the same incident, nothing is hand-spawned while the engine is working, dressing appears only when it sends nothing, a refused CREATE_INCIDENT still produces a scene, closing deletes the incident and every ped it placed, caps hold, distance closes it, and disabling opens nothing

Changed

• One verified spawner for the whole resource (IntelNpcSpawn_Verified, published from client/spawn.lua). It validates the model, loads it and reads lib.requestModel's return, then checks the ped that came back is the model asked for — a substituted default civilian is deleted rather than put to work. client/patrol.lua now uses it instead of its own copy, so the bug that made the patrol test spawn passers-by has exactly one place it could ever come back from

---

v1.27.1 — 2026-08-27

Fixed

• The patrol test spawned civilians instead of guards. client/patrol.lua called lib.requestModel inside a bare pcall and threw the return value away — so it only knew the call had not errored, never whether the model had actually loaded. An unloaded model reaches CreatePed, and GTA quietly substitutes a default civilian. client/spawn.lua and client/life_points.lua had always done this correctly; the patrol module was the odd one out
• All three of its spawn sites now go through one helper that validates the model exists (IsModelInCdimage + IsModelValid), loads it and reads the answer, then verifies the ped that came back is the model that was asked for. A substituted ped is deleted rather than put to work
• Config.patrol.test_model names the model the test commands use
• One failed spawn stopped a route ever spawning again. A route whose model failed to load recorded an empty list against its id, which made the early-out at the top of the spawner permanent — a single streaming hiccup disabled that route for the session. The route is only marked as spawned if a guard actually was. Found by the harness, not in play
• /intel_patrol_diag now says what it is doing. It deliberately switches the scripted walker off so only the native is measured, which means most of the guards it spawns are supposed to stand still — that is the measurement. It said none of this, so a minute of guards standing around looked like a broken command. It now states that up front, prints progress per combination, and its verdict distinguishes "no combination works on this build" (a real answer, and the walker still handles it) from a failure

---

v1.27.0 — 2026-08-27

Added

• Config.audio (client/audio.lua) — D5, audio direction. Alarms, one-shot world sounds, venue music through static emitters, ambient-zone state and audio-scene mix ducking. Four native families, no permanent threads — only the ones that stop what they started
• Alarms are verified, not hoped for. An alarm name is a string the game either knows or does not, and a wrong one is a silent no-op — the classic way this feature "works" in a script and produces nothing in the world. But PREPARE_ALARM returns a BOOL and IS_ALARM_PLAYING is a real getter, so the configured name is prepared, the answer read, and the next candidate tried on refusal. Whichever the game accepts is remembered and tried first next time; if none is accepted the console says so rather than leaving you wondering why the shop is quiet
• An alarm is also an event. It goes into the ordinary perception pipeline as an audible one, so witnesses, memory and gossip follow without this module knowing anything about them
• Global state is restored. Static emitters and ambient zones are engine globals: leaving a venue's music switched off outlives the resource. Every emitter, zone and scene touched is recorded and put back on stop
• One-shot sounds use sound id -1, which GET_SOUND_ID's own documentation prescribes for fire-and-forget playback, so no sound id can leak
• Audio scenes report whether they actually started (IS_AUDIO_SCENE_ACTIVE) instead of assuming the name was real
• /intel_alarm_test and /intel_audio; also in the F12 panel's Try this
• 20 assertions in real Lua: a bogus name never reaches StartAlarm, an accepted one is used and remembered, the alarm reaches perception as the configured event type, it stops itself, perception can be opted out of, sounds are fire-and-forget, an unknown audio scene answers false, every global write is recorded for restore, and disabling writes nothing

---

v1.26.0 — 2026-08-27

Added

• Config.engine_police (client/engine_police.lua) — vanilla GTA police, on and kept on. SetCreateRandomCops, both scenario variants, all fourteen dispatch services, SetDispatchCopsForPlayer, SetPoliceIgnorePlayer(false), radar blips and the engine wanted ceiling are now asserted every few seconds instead of assumed
• This resource was part of the problem. client/ai_suppression.lua only ever wrote those natives inside two branches that are both off by default, so with the shipped config it never touched them at all — it just inherited whatever the last resource to load had decided. Most server templates (qbx_smallresources and friends) switch random cops and dispatch off at startup and nothing turns them back on
• It verifies the two things the engine will answer. CAN_CREATE_RANDOM_COPS() is a real getter: if it reads false right after we set it true, something is fighting us, and the console names the likely resource instead of leaving you to guess. GET_MAX_WANTED_LEVEL() reading 0 means you can never become wanted whatever any police module does — that one is shouted about
• Stands down where it should: Config.disable_ai_police wins, and it will not fight ai_suppression while that is deliberately suppressing dispatch
• State on the Police tab and /intel_engine_police
• 20 assertions in real Lua, including the override being detected and named, a zero wanted ceiling being reported, selective service disabling, and every stand-down path

Changed

• The current-scene panel can be scrolled, and says when it cannot show everything. It is pointer-events: none by design so it can never steal a click from the game — which also made it impossible to scroll, and with the trace feed now taking the bottom of that edge there is more content than room
• The body accepts the wheel only while the F12 panel is open, when NUI focus is already taken and nothing is stolen from the game
• When content is clipped, a sunset bar at the foot says so — and once scrollable, how much more there is
• Visual pass: the horizon rail and gradient title from the control panel, a visible thin scrollbar (one nobody can see is the same as none), a warmer near-opaque ground and more breathing room
• Measured at 1280×720, 1920×1080 and 2560×1440: overflow is announced with the panel closed, the body is inert then, and it scrolls with the panel open

---

v1.25.0 — 2026-08-27

Added

• Patrol routes work whether or not TASK_PATROL does. Two releases of coaxing the native produced a guard who stood still, and a feature should not be hostage to a native with three undocumented parameters and no read-back. The engine path is still tried first because it costs nothing; when the verify says it was refused, the route is now walked from script — go to the node, face its look-at point, play its scenario for its wait, go to the next one
• One 500 ms thread per walking guard, not per guard and not per frame, and it stops on release or death. Config.patrol.walker_fallback = false restores the old stand-at-your-post behaviour
• SET_PED_KEEP_TASK is now set before TASK_PATROL, so the engine cannot quietly drop the task it was just given
• /intel_patrol_diag measures the native instead of guessing at it. It spawns one guard per TASK_PATROL(p2, p3, p4) combination — all eight — on short routes laid out in front of you, watches which ones actually move, and prints the winner. If one works, those three values go in Config.patrol and the engine walks your guards again. If none does, that is a fact worth having rather than a third round of guessing
• The walker is switched off for the duration of the test, so only the native is being measured

Changed

• The debug trace feed is bottom-LEFT by default. The F12 control panel owns the right edge, so keeping the feed opposite it means both are readable at once, which is the point of having the feed open
• The current-scene panel is pinned down the same edge, so it now stops above the feed rather than overlapping it
• The step-aside the feed does when the control panel opens now only applies when the feed is on the right; a left-anchored feed was being pushed into mid-screen for no reason
• Measured at 1280×720, 1920×1080 and 2560×1440: the feed is bottom-left and the scene panel clears it at all three

---

v1.24.2 — 2026-08-27

Fixed

• The shipped patrol route spawned a prisoner. s_m_y_prismuscl_01 is the Bolingbroke inmate — prismuscl is prisoner muscle, not "muscular guy for the beach". The Vespucci route now uses s_m_m_security_01, a private security guard, and data/patrols.lua warns about the pair by name so the next person does not make the same read
• /intel_patrol_test put the guard on a route that was somewhere else. It spawned him next to you but assigned a route from data/patrols.lua, whose nodes are at fixed world coordinates. Stand anywhere but there and the guard has to path across the map before he can walk a beat — which looks exactly like "he just stands there"
• With no argument it now lays a 16 m square around where you are standing and spawns the guard on it, so you can watch him do a lap. Config.patrol.test_route_size sizes it
• With a route id it spawns him at that route's first node instead of next to you, for the same reason
• Repeating the test replaces the temporary route rather than stacking a new one each time
• The verify could call a working patrol a refusal. It measured movement verify_ms after tasking, but a guard stands at his first node for that node's wait before walking anywhere — so any route whose first wait was the longer of the two read as "TASK_PATROL did not take" and got the poor guard stood back down on a scenario. The wait is now measured from when he could first move: the first node's wait plus verify_ms
• Asserted: a route whose first node waits 9 s with a 4 s grace is no longer read as a refusal

---

v1.24.1 — 2026-08-27

Fixed

• /intel_patrol_test froze the player in place. It put the patrol route on the player's own ped. A player ped is driven by input, not by AI tasks, so TASK_PATROL did nothing — and then v1.24.0's own verify step read "he did not move", cleared the player's tasks, blocked his ambient events and dropped him into a guard scenario. That is a freeze with no way out, caused by the safety net rather than caught by it
• Patrol_Assign now refuses a player ped outright, with the reason
• /intel_patrol_test spawns a guard next to you and puts him on the route, which is the thing worth looking at anyway. /intel_patrol_clear removes the guards it spawned
• Four assertions added for exactly this: assigning a player is refused, no task is issued, and no scenario is forced on them
• /intel_unstick — an escape hatch, because a debug tool that can strand you needs one. Clears tasks, unblocks ambient events, unfreezes position and closes any open dialogue on your own ped. Also in the F12 panel's Try this tab
• client/focus.lua now refuses a player ped too. Focus blocks ambient events, clears tasks and can put its subject into a scenario — the same three writes that caused the freeze. No caller passes a player today, but "no caller does today" is precisely the reasoning that stranded one

---

v1.24.0 — 2026-08-27

Added

• Config.patrol + data/patrols.lua (client/patrol.lua) — D1, guards that walk a beat. The engine has a whole patrol system and almost nobody uses it, because its natives are underspecified in two ways that both make it silently do nothing:
• OPEN_PATROL_ROUTE's own documentation says the name "must start with miss_ to be properly created". A route named anything else is accepted by every call and then does not exist. Route ids in data/patrols.lua are plain names and the prefix is added for you, so it cannot be forgotten
• ADD_PATROL_ROUTE_NODE takes eight floats and the second three are a LOOK-AT POINT, not a second position. Reading them as a destination is the usual way this ends with guards facing walls. The data file names the two separately (coords and look) so they cannot be confused
• Links are directional: a cyclic route links the last node back to the first, a there-and-back route links each pair both ways
• Scenario names are validated against data/generated/scenarios.lua on build. A typo is named in the console and replaced, rather than producing a guard who stands doing nothing with no error
• Routes may spawn their own guards (model + count) with distance spawn/cull, or you can hand any ped to Patrol_Assign(ped, route_id)
• After TASK_PATROL the engine owns the guard — no thread follows him
• Assignment is verified, not assumed. TASK_PATROL(ped, name, p2, p3, p4) has three parameters nobody has ever documented and nothing can be read back, so a tasked guard is checked a moment later for having actually moved. One that did not is put on a scenario at his first node, so he stands post rather than standing idle in the road, and the trace says which happened. The three parameters are exposed as Config.patrol.task_p2/p3/p4 rather than buried, because they are what to try if guards refuse to walk
• Try it with /intel_patrol_test, check it with /intel_patrol
• Verified in real Lua — 25 assertions: the miss_ prefix is always present, the build order is open → nodes → links → close → create, the look-at triple is distinct from the position triple, a cyclic route closes its ring while a linear one links both ways, a bad scenario name is replaced, a one-node route and an unknown id are both refused, a route is built once and reused by later guards, a guard who moved is confirmed walking, one who did not is stood at his post, and release hands the ped back

Changed

• The crowd director and patrol routes have module switches in the F12 panel's Modules tab, and "Guards on a beat" is a new entry in Try this
• /intel_patrol and /intel_patrol_test joined the command allowlist; all 19 command buttons in the NUI are checked against it

---

v1.23.0 — 2026-08-27

Added

• Config.crowd (client/crowd.lua) — D3, the crowd director. One shared service rather than a feature: something happens and it gathers the pedestrians who are already there around it. A4 (crime scenes), D2 (news events) and D9 (fame) are all specified to consume it rather than each growing their own copy
• It borrows peds, it does not spawn them. Every recruit is an engine pedestrian who was walking past anyway, so a crowd costs no population budget and no model loading. The contract that matters is giving them back: /intel_crowd prints whether any were borrowed and never returned, and it says so in red if the count is ever non-zero
• Four profiles — watch (turn and look), film (plus the phone-filming scenario), gawk (approach to a ring, then watch), cheer (approach and applaud). Danger disperses any of them through TASK_SMART_FLEE_PED, the engine's own flee, releasing every recruit on the same tick
• Never recruits a persona, a ped already mid-reaction, a panicked or hostile one, anyone in a vehicle, or a ped another crowd already claimed
• API: CrowdDirector_Claim(anchor, profile, opts), _Release, _Disperse, _DisperseAll, _Counters. Try it with /intel_crowd_test [profile]
• Verified in real Lua against the module's own thread — 27 assertions, weighted at the give-them-back contract: caps hold, no ped is ever in two crowds, releasing restores the blocking flag and hands the ped to TASK_WANDER_STANDARD, a ped that was in a scenario is not forced to wander, every recruit of a dispersed crowd gets the flee task and is unblocked, a despawned recruit stops being claimed, crowds expire and end when you walk away or the anchor vanishes, and recruited == released exactly with nobody left claimed

Changed

• The 3D overlay above NPCs has a basic mode, and it is the default. Config.debug_3d_mode = 'basic' draws two rows: row 1 is identity, row 2 is only what is actually true right now — panic, hostile, busy, irritation against its threshold, per-ped rep, whether a voice was cast over the model's own, the driver archetype if they are in a car, fighting, fleeing. An empty row 2 means an ordinary pedestrian, so a busy one stands out. 'full' is the old everything-at-once wall, 'off' is nothing
• The dev-menu button cycles basic → full → off. It previously flipped Config.show_debug_3d, which since the mode key exists would have made the button do nothing at all
• The Tests tab is now "Try this". It was a 38-step checklist with pass/fail/skip bookkeeping that nobody ticked and that went stale the moment a module shipped. It is now one action and one observable result per entry, covering what actually ships — the zero-damage nudge, the survivable clip, the driver who answers when you rear-end him, unarmed aiming, the aim that fires once, persona voices, the red light without stopping, the non-lethal band, crowds, and trust on a stranger versus a persona. No bookkeeping

Fixed

• Two more panel buttons were refused. /intel_crowd and /intel_crowd_test joined Actions['command']'s allowlist; all 17 command buttons in the NUI are now checked against it rather than assumed

---

v1.22.0 — 2026-08-27

Added

• Config.traffic_personality (client/traffic.lua) — the drivers around you are people too. Vanilla ambient traffic is one driver repeated: same aggression, same ability, same style. Each car within radius now gets a personality from the same seven archetypes the pedestrians use, so the coward who brakes for you and the aggressive one who leans on the horn are the characters you already meet on foot — not a second, parallel personality system
• It is all engine. Three natives do the whole job: SET_DRIVE_TASK_DRIVING_STYLE (the flag composition, taken from data/generated/driving_styles.lua, which is built from the game's own flag table rather than hand-written constants), SET_DRIVER_AGGRESSIVENESS and SET_DRIVER_ABILITY. After those three writes the engine drives the car and nothing polls it again unless you provoke it
• Who does what: coward gives way and rarely honks · compliant obeys lights · stoic ignores you · cunning does not fight but notes you down, so a hit from you enters the ordinary witness pipeline, memory and gossip · brave honks nearly half the time · cop obeys lights with the highest ability · aggressive is reckless, almost always honks, and swerves at you
• Driving into a car now reaches its driver: client/collision.lua hands the contact to this module, which decides the reaction by archetype
• Network-correct. TASK_VEHICLE_TEMP_ACTION is documented as not applying to remote clones, so the swerve and brake reactions request control first and are skipped when it is not granted. The three personality writes are local and need no ownership
• Skipped by default: mission vehicles, and anything that is not street traffic (cycles, boats, helicopters, planes, trains)
• Honest limit, documented in the config: none of the three natives has a getter, so releasing a car writes the engine's own defaults back rather than whatever it had before
• Live state on the Police tab of the F12 panel and /intel_traffic
• Verified in real Lua by driving the module's own thread against a stubbed engine — 22 assertions: the three writes happen exactly once per car and are never repeated, the archetype is stable across scans, each archetype reacts in character, reactions are rate-limited, a remote clone is never given a temp action, mission vehicles / helicopters / empty cars / distant cars are all skipped, leaving the radius hands the car back, and disabling the module writes nothing at all

Fixed

• The collision panel's console button was refused. /intel_collision was added to the panel in v1.19.0 but never to Actions['command']'s allowlist, so pressing it answered "not one of this resource's dev commands". Both it and the new /intel_traffic are allowlisted, and all 13 command buttons in the NUI are now checked against the allowlist rather than assumed

---

v1.21.0 — 2026-08-27

Changed

• The whole UI is retinted to "Leonida" — the Vice look. Not a dark panel with pink in it; three things carry it and they are documented in nui/theme.css so a server retinting it keeps the identity:
• the ground is warm navy, never neutral black — every surface keeps a little magenta so nothing reads as grey
• the accent is a gradient, pink → orange → amber, and it sits on the type (--lr-sunset through background-clip) as well as on rails. The panel title, the NPC's name and a 2px horizon rail under the panel header all carry it. That is what makes it read as this rather than generic neon
• exactly one cold colour, the cyan, used sparingly — water, screens, investigation
• the sun in --lr-horizon is low and off to one side rather than centred, so a panel looks lit from somewhere instead of glowing on its own
• Measured, not eyeballed: rendered against a bright sunset backdrop at 1280×720 through 2560×1440. Nothing overflows and there is no horizontal page scroll at any of them
• The panel body is near-opaque now (was .86). The game blurs the world behind it, but blur is not darkness — measured against a bright sky the translucent version washed the hint text out completely. The sunset belongs on the accents, not through the card
• The two faintest text tiers were lifted (--lr-dim, --lr-faint) for the same reason: they were unreadable over anything bright

Fixed

• The speaker's name could render invisible. .npc-name set color: transparent unconditionally alongside background-clip: text — where the clip is unsupported that leaves nothing on screen. Both it and the new panel title declare a solid colour first and only go transparent inside an @supports guard

Docs

• "escrow" no longer appears in the README. Both mentions were denials ("no escrow"), but the resource is not sold escrowed and the word does not belong in the docs at all. The two lines now say what actually ships: unencrypted, unobfuscated, every file readable and editable

---

v1.20.0 — 2026-08-27

Added

• REPORT_CRIME — the engine decides the wanted level. GTA V already has a crime id for every trigger this module raises: 2 red light, 4 speeding, 12 assault on an officer, 15 pedestrian struck. Handing it the report hands it the whole decision — whether an officer really witnessed it, whether it earns a star, which dispatch answers — replacing our any_cop_within() radius scan and the chance_per_violation dice roll with the game's own answer
• REPORT_CRIME returns void and its crime table is a community decompilation, so it is not trusted blind. Config.police_crime_reporting ships as 'verified': report the crime, read GET_PLAYER_WANTED_LEVEL back after police_crime_verify_ms, and raise the star from script only if the engine did nothing. The trace names which acted — crime_native_took or crime_native_ignored. 'native' never second-guesses, 'script' never asks
• Prerequisite already met: IsNativeDispatchInCharge() has returned true since v1.17.0, so there is a live dispatch to report into

Changed

• Running a red light is detected from the engine instead of from a stop. There is no native that reads a traffic light's phase — re-verified across all 6,416 entries; SET_ENTITY_TRAFFICLIGHT_OVERRIDE writes one with no getter. But the phase does not have to be read: the map's own road graph flags the node (GET_VEHICLE_NODE_PROPERTIES, TRAFFIC_LIGHT = 1 << 8), and IS_VEHICLE_STOPPED_AT_TRAFFIC_LIGHTS on a car the engine is holding tells you that direction is red. Crossing a light-controlled node above the speed floor while a same-direction vehicle is held there is running a red
• Heading is what makes it correct. Cross traffic at a junction is also stopped — at its own red, while yours is green — so counting it would book the player for obeying the light. Only vehicles within same_direction_arc (45°) count
• This closes the gap the module shipped with and the audit recorded as unfixable: the old rule polled the native on your own car and fired when you pulled away, so it required you to have stopped first — blowing straight through, the actual offence, was the one case it could not see. The stop-then-go path is kept as a second detector for empty junctions
• No hand-built coordinate list: the junction data is the map's
• Verified in real Lua against the rules themselves — 14 assertions covering node-flag reading, the same-direction discriminator, cross traffic, oncoming traffic, range, and heading wraparound across the 360° seam
• docs/NATIVE_AUDIT.md §4 corrected. It claimed "a correct red-light detector is not buildable from natives", which assumed a detector must read the light. §8.1 records the correction and what remains genuinely unreadable. Its dismissal of REPORT_CRIME was answering the wrong question — it is not a detector but a decision, which §8.2 covers
• §8.3 gives the honest overall answer: the 3–5% replaceable headline stands. This lane is tens of lines, not thousands, and §4's list of what has no native equivalent is unchanged in every other respect

Fixed

• A pcall out-param offset that would have silently disabled the new detector. GET_VEHICLE_NODE_PROPERTIES returns a BOOL plus two out-params and pcall prepends its own status, so the flags are the fourth value. Reading the third gives density (0–15), leaving bit 8 permanently clear. Caught by asserting on the real signature before shipping
• A forward-reference that would have thrown at runtime. The cop-assault watcher is defined above the new crime-reporting function, so a local function there compiled as a nil global lookup. Forward-declared, and confirmed against the compiled bytecode that no _ENV lookup remains

---

v1.19.3 — 2026-08-27

Fixed

• Aiming a weapon at an NPC re-triggered him every few seconds and flooded the debug trace. The aim thread polls at 300 ms and called Reactions_Trigger on every tick the reticle was over a ped. Two things came out of that one line:

• the NPC re-reacted every time the reaction debounce expired, so keeping a gun on someone restarted his reaction roughly every four seconds instead of threatening him once;

• every debounced call still wrote a trace line, so one held aim produced about three debounced rows per second and buried everything else in the feed — exactly when you were looking at it.

• Aiming is now edge-triggered: it fires once when the reticle lands on a ped and not again for that ped until the aim has been off him for Config.aim_rearm_ms (6 s). Swinging onto somebody else fires immediately, because that genuinely is a new threat. Verified against the rule itself: the first aim fires, forty polls over twelve seconds fire zero more, a different ped fires at once, flicking straight back does not, and after the re-arm it does again

• The trace feed collapses repeats. Some call sites are polled rather than edge-triggered, and a poll reporting the same answer every tick should be one row with a count, not N identical rows. A repeat of the same system + event + ped + reason inside Config.trace.collapse_ms (2 s) now increments the count on the row already there — the panel shows debounced ×47 instead of forty-seven lines. Nothing is lost: the reason text is identical by definition, and a count plus a last-seen time is strictly more information than N copies. A different ped, a different reason, or a gap longer than the window all still get their own row, and collapse_ms = 0 shows every line

• The NUI updates the existing row in place rather than appending, so the collapsing holds on the JavaScript side too

• Verified against the real bus: 34 identical calls produce 1 row whose counts account for all 34, a second ped is never folded into the first, a different reason is never folded either, a repeat past the window starts a fresh row, and switching it off restores every line

---

v1.19.2 — 2026-08-27

Fixed

• Aiming at an NPC with bare fists made them run away. IS_PLAYER_FREE_AIMING is true whenever the aim button is held, weapon or not, and the aim reaction never checked. So right-clicking while unarmed fired on_aimed_at — the archetype's threatened reaction, which for most of them is panic and flee — on whoever was under the reticle, and every NPC you so much as looked at bolted. Aiming now needs something to threaten with. Melee counts: a bat or a knife pointed at someone is a threat, bare hands are not. Config.aim_requires_weapon = false restores the old behaviour. When an aim is ignored the trace says so, rate-limited, because the aim button is held rather than tapped

• Saying hello and goodbye to a random pedestrian built "trust" with them, and the toast was titled with an internal id. A polite close called Reputation_OnPoliteClose(session.memory_key), and for an ambient ped that key is ambient_<uid> — a runtime identifier for one pedestrian who will despawn in minutes. Three things went wrong from that one argument:

• It was written into PlayerReputation, which is persisted to the database. Every stranger the player was polite to left a permanent saved row that can never match a persona again, growing without bound

• It fired the trust toast, whose title falls back to the raw id when no persona matches — that is the "ambient ped" text on the trust popup

• It made the trust system look pointless, which was the fair complaint: a stranger you will never see again should not be building a relationship with you

• Now: a named persona earns the point exactly as before. An ambient ped earns nothing unless Config.reputation_ambient_polite_close is turned on, and even then it goes on the ped (NpcState_AddRep), where it decays and disappears with him — never into the saved store. Reputation_Add and Reputation_Set now refuse an ambient_* key outright with one console warning, so no other call site can pollute a persisted store either, and restore prunes the rows older versions already wrote. The toast never shows a raw internal key: an unmatched ambient id renders as "Stranger"

• Verified in real Lua against the module itself: a stranger earns nothing and writes nothing, Mahoney still earns his point and his toast carries his name, the cooldown holds, opting ambient standing back in puts it on the ped and leaves the store clean, both write paths refuse ambient keys, and an already-polluted save is cleaned while real personas survive

• A first-ever polite close was refused while GetGameTimer() was still below polite_close_cooldown_ms. PoliteCloseLastTickMs[id] or 0 made "never happened" indistinguishable from "happened at time zero". Same latent bug the collision harness caught in v1.19.0, in code that predates it

---

v1.19.1 — 2026-08-27

Fixed

• The dev panel's test pistol was confiscated the moment it was given. On an inventory-managed server — ox_inventory on qbox, qb-inventory on qb — the inventory owns your weapons, and a weapon handed over with GiveWeaponToPed is one the inventory has never heard of, so it strips it back off within about a second. v1.18.0 detected that and named the resource responsible, which explained the problem without solving it. The pistol now comes from the inventory on those servers (Adapters.inventory.AddItem, via a new Config.debug-gated, rate-limited server event), so it stays. The native give is used only where no inventory resource is running, and is still verified after the fact rather than assumed
• The item id differs by inventory and is resolved per bridge: WEAPON_PISTOL for ox, weapon_pistol for qb-inventory. ESX goes through addWeapon/removeWeapon first and falls through to the item route
• Taking the pistol back removes the same item it added, so the toggle still undoes exactly what it did and never touches a weapon of your own
• When the inventory has no pistol item registered, it now says so and names the resource to add it to, instead of failing silently

---

v1.19.0 — 2026-08-27

Fixed

• Every static NPC had the wrong voice, including Sergeant Mahoney. Config.default_gta_voice_name was handed to every persona that declared no gta_voice_name of its own — nine of the ten shipped — and written over the model's voice with SetAmbientVoiceName. Those models already owned a correct voice: s_m_y_cop_01, s_m_m_doctor_01, s_m_y_dockwork_01, a_m_m_genfat_01, a_m_m_business_01, a_f_m_business_02, s_f_y_hooker_01. The game picked each of them to match its model, so the override could only ever make things worse. It is now offered only to models that genuinely have no voice — freemode and player models, which ship with no pedvoicegroup at all and are silent without it — and it is sex-checked against the ped first, so the one shipped persona that needs it (Erika, mp_f_freemode_01) gets a female voice rather than the configured male one. This is the same reasoning v1.16.2 applied to ambient pedestrians ("keep their own voice") and never applied to personas. Verified in real Lua against the shipped data and the shipped persona list: all nine real-model personas keep their own voice, the freemode persona is never left mute, no forced voice is ever the wrong sex, and Config.force_persona_default_voice = true restores the old behaviour exactly. Extend the voiceless list with Config.voiceless_persona_models
• A persona declaring a voice of the wrong sex is now refused rather than applied. That is a config mistake, not an instruction: it is dropped with one console warning naming the persona, and the model keeps its own voice
• Config.police_ped_hit.protect_nearby_peds was dead config. Nothing has read it since the v1.17.0 police cut, so the health floor it advertised never ran no matter what you set it to. It is removed, and the annotation says where the behaviour actually lives now. fight_chance_by_archetype, female_fight_multiplier, fight_chance_range and driver_tail_reactions are dead in the same way; they are kept so existing configs still load, and are now marked as doing nothing

Added

• Config.vehicle_collision (client/collision.lua) — ships on. Two separate bugs behind one complaint:
• A light tap killed them. GTA applies a critical-damage multiplier to vehicle impacts, so a 15 km/h clip could be fatal and the driver of a car you barely touched could die in the crash. Below lethal_kmh (35) the victim is floored at survive_floor health (110) instead of dying, and the critical multiplier is removed from anyone near your moving vehicle — borrowed, and handed back the moment they leave the radius, you stop driving, or the resource stops. Above lethal_kmh nothing is floored
• They did not react when you drove into them, however many times. Every reaction path in this resource hung off a health drop, so a damage-free nudge produced nothing at all. Contact now comes from IS_ENTITY_TOUCHING_ENTITY, independently of damage — and for a ped in a car, from your vehicle touching theirs, because a driver you rear-end is not touching your car, the two cars are. That is why traffic never reacted
• Three tiers by your speed at contact: under nudge_kmh (8) a nudge (turns, curses, leans on the horn), under bump_kmh (25) a bump (provoked through the normal path, so the archetype decides), at or above a hit (reacts as a struck person). A nudge and a bump never make you wanted; the star on a hit is still client/police.lua's decision and still only when the police module is on — but the victim reacts either way, which with police off (the default) previously produced nothing whatsoever
• Live tiers, counters and a switch are on the Police tab of the F12 panel; /intel_collision prints the same thing
• Verified in real Lua by driving the module's own thread body against a stubbed engine: a zero-damage nudge reacts, the same victim does not re-react inside same_ped_cooldown_ms but does after it, a 20 km/h bump provokes rather than curses, a 20 km/h impact that would have killed is floored to 110 while a 60 km/h one stays lethal, a car-on-car tap reaches the driver without the two peds ever touching, an empty seat is never filled by the scan (GET_PED_IN_VEHICLE_SEAT creates an occupant in one), and enabled = false is genuinely vanilla
• Two bugs that harness caught in the module itself before it shipped: the tier was being decided from a speed read up to interval_ms before the contact, which made the same impact register as a nudge or a bump at random; and a victim's first-ever contact was suppressed while GetGameTimer() was still below the cooldown

---

v1.18.0 — 2026-08-27

Removed

• The police module is now the wanted level and nothing else — and it says ALPHA where you can actually see it: the F12 panel's Police tab, the README heading, and the boot warning. client/police.lua went from 3,529 lines to 546
• Gone: the pre-call window where the driver you hit walked over to talk, the apology / bribe / threaten panel, the responding officer who got out of his car and held a conversation, the bribe economy behind both (client panels and both server callbacks), the resource's own cruise and response patrols, the non-lethal band, and client/apology_quickkey.lua entirely
• Kept: the four triggers that decide when you should be wanted — hitting an officer, running a red light in front of one, hitting a pedestrian and being reported for it, and speeding past one — plus the clamp that stops this module pushing you past Config.police_max_wanted_stars. The victim of a hit still reacts, because that is the NPC simulation and it runs through client/reactions.lua like any other provocation
• The response is now GTA's own dispatch. That has a consequence worth knowing: Config.cops_passive_mode now defaults to false, because with it true the dispatch services are suppressed and you get a wanted star nobody ever answers. /intel_police_dump warns if it finds that combination
• This behaviour is not behind a config key — it is in git history at v1.16.7

Fixed

• The armed toggle wiped your whole loadout. toggle_armed — surfaced in the panel's Player & World tab as "toggle armed (pistol)" — called RemoveAllPedWeapons on its off-branch, so pressing it while carrying anything of your own took everything, not the test pistol it had given. It now gives and takes back only its own pistol; if you already carry one it holsters instead of confiscating, and says so

• Police shot you at one star again. That was a direct consequence of removing the non-lethal band in this same version — the band was exactly what held their fire. It is back as client/police_nonlethal.lua, but minimal: hold fire, nothing else. No conversation, no bribe, no spawning, ~250 lines against the 2,600 that were cut. It reads the same Config.police_nonlethal keys as before, so an existing config still applies

• Weather, time and the test pistol silently did nothing on a framework server. All three were fire-and-forget client-side calls that reported success regardless — so when a weather-sync resource or an inventory resource overwrote them a tick later, the button looked broken rather than outvoted. Each now applies, verifies, and reports the truth: weather and time check the value 700 ms later and name the sync resource that took it back, and the pistol checks whether it survived and names the inventory that stripped it. Weather and time also gained a hold variant that re-applies every frame for 15 s, which wins against a sync resource that pushes on an interval

Changed

• The debug now states the RULE, not just what happened. The Police tab opens with what is supposed to occur at each wanted level — below the ceiling police must not shoot, above it is vanilla, an officer you shoot leaves the band for good, band off means vanilla everywhere — then shows whether the rule currently applies and the sentence saying why not. Underneath, each of the four wanted triggers states its own condition, including the red-light known gap. /intel_nonlethal prints the same rule and the same live verdict, so the console and the panel cannot disagree

---

v1.17.0 — 2026-08-26

Fixed

• The debug trace stopped updating after a while. Its flusher was a single thread with an unprotected SendNUIMessage in the loop: one payload that would not encode killed the thread while tracing still read as ON — and because the toggle returned early when the requested state already matched, it could not be restarted. The flusher is now started once and lives for the resource's lifetime, idling while off, and a failed batch is reported and dropped instead of taking the loop with it
• Looking at an NPC changed its voice. /intel_inspect probes the voice system every refresh, and that probe ran the real casting path — which latches a fallback voice into the ped as a side effect. A debug surface must not alter what it reports on, so the observing path is now explicitly dry: it answers the same question and writes nothing. The speech path itself is unchanged and still latches as before
• The control panel and the current-scene panel both hung off the screen. Sized by content with a max-height cap, tall content grew the rendered box past its own computed height — measured in a real browser at 2560x1440, the control panel computed 1353px and drew 1805px, overhanging the top and the bottom. Both are now pinned to two opposite edges, so the viewport decides the height and no amount of content can change it. Verified by measuring every tab at 1280x720, 1366x768, 1600x900, 1920x1080 and 2560x1440: all inside, no horizontal page scroll
• The control panel's tab row was clipped. Eight tabs in a non-wrapping row need 705px inside the shell's 592px of usable width, and the shell clips — so Modules, Tests, Lab and Trace were rendered outside the clip and could not be clicked. The row wraps now
• The current-scene panel could run off the bottom of the screen. It carried a max-height on the shell and another on its body, so the body could exceed the shell. It is now a proper flex column: fixed header, scrolling body, bounded by the viewport

Changed

• No CSS backdrop-filter anywhere. It is not rendered reliably by FiveM's CEF. The control panel now blurs the world through the game's own TRIGGER_SCREENBLUR_FADE_IN/_OUT (Config.control_panel.blur_ms), and the two always-on surfaces are translucent with a text shadow rather than blurred

• The control panel opens on the right, not the centre, as a full-height sidebar, and no longer dims the screen — the backdrop is transparent and click-through

• The debug trace is smaller and defaults to the bottom-right, clear of the scene panel and of a left-hand chat. Position and size are configurable (Config.trace.side / vertical / margin / margin_y / width / height), and it steps aside to the left while the control panel is open so both stay readable

• The blue sphere over the inspected ped is off by default (Config.debug_inspect.marker). It read as a game marker rather than a debug aid, and the panel already names the ped handle

• The F12 keybind registers under a new name. defaultKey only applies the first time FiveM sees a keybind name; the old name carried whatever key was already stored against it on that client, which is why an F12 default could still open on another key

• DisableShockingEvents wrote ped config flag 281, which is DisableGoToWritheWhenInjured. The correct index is 294, confirmed against the 468-entry enum carried in SET_PED_CONFIG_FLAG's own documentation. The key has shipped false by default throughout, so no default install was affected — but anyone who turned it on was suppressing the wounded-crawl animation and never touching shocking events. The customer-facing comment in shared/config.lua named the wrong number too, and now names 294

• A ped you once fought stayed permanently hostile. configure_for_combat put the ped into LRR_DRIVER_RAGE — a group that hates PLAYER at level 5 — with no snapshot and nothing to restore it. The group is now snapshotted before the write and handed back on every combat-watchdog exit where the ped is still alive. Routing it through the ordinary hands-off wrapper would have been wrong: that wrapper skips borrowed engine peds, which would have left ambient NPCs unable to fight back at all, so a deliberately unconditional variant carries the snapshot instead. The restore is likewise its own function rather than the shared one — the shared restore writes its recorded value into both the current and the default group hash, which is right for the wrapper that sets both and wrong here, where only the current hash changes; reusing it would have overwritten a ped's default group with its pre-combat current group whenever the two differed. Verified against a stubbed engine: default preserved on restore, double-restore a no-op, and the shared path demonstrably corrupting the case the dedicated one protects

• The red-light detector's prop-scanning path had never once fired. It called GetTrafficlightState, which is not a FiveM native — it is MTA:SA's — and the pcall around it swallowed the nil call from the day it was written. The dead path and its prop-hash table are gone. Detection continues through IsVehicleStoppedAtTrafficLights, which is real and always did the actual work

• Two SetPedAsCop(c, false) calls removed. The native's own documentation states that toggling it false has no effect; both were no-ops sitting in cop-spawn paths and reading as though they did something

Removed

• ped_is_handsup in client/target_options.lua. It read ped config flag 296, which is NeverReactToPedOnRoof — and there is no hands-up flag anywhere in the 468-entry enum. The function was never called from anywhere in the resource, so it is deleted rather than repaired; inventing behaviour for dead code would have been the worse fix

Added

• /intel_menu — one NUI with everything in it (client/control_panel.lua, Config.debug only, bound to F12). Five tabs: Actions — all fourteen reactions on the ped you are facing, provoke, force a hail, every street and paired scene, the police module, the diagnostic commands, teleport to any persona. Modules — live on/off for every module and every debug surface, this session only, it never writes your config file. Tests — the checklist as clickable steps, each with what to do, what to expect, a prepare button that switches on the debug that step needs, and its automatic check. Lab — the sixteen engine experiments. Trace — per-system filters for the debug feed
• It is a front end for what already exists rather than a second copy: the actions call the same functions the commands call, the checklist is the same plan client/dev_test.lua owns, and the experiments are the same bench in client/dev_lab.lua. Nothing in it has its own private truth
• The only debug surface that takes NUI focus, released through IntelNpcNui_SetFocus which owns the shared cursor bag. ESC closes it
• The command action runs from a fixed allowlist of this resource's own dev commands — arbitrary text and anything chained past a ; is refused
• It carries the whole of the older ox_lib dev menu, verified rather than assumed: a coverage check maps every one of that menu's 74 actions onto a panel button and reports 74/74. Player state, wanted level, all seven weathers, all four time blocks, the four test-ped spawns, per-persona teleport / force-open dialogue / despawn / mood, the reputation and memory editors including wipe ALL, the news roller, the hail category switches, the four perception triggers, every police toggle and every force-a-reaction command. 139 clickable actions against the old menu's 74
• It drives client/dev_menu.lua's own helpers through a published IntelNpcDevOps namespace rather than reimplementing any of them, so the two surfaces cannot drift on what "toggle bloody" or "spawn a cop" means. The ox_lib menu itself is untouched and still on /intel_dev — F12 now opens the panel, and Config.control_panel_on_key = false gives F12 back to it
• Per-NPC decision tree and timeline — the NPC tab of /intel_menu. Pick the ped you are facing (or any NPC that has decided something) and read back exactly why it behaved the way it did, in two views:
• Tree — grouped under the event that caused them. One gunshot opens an episode; the witness scan, each witness's chosen reaction and the state each reaction left behind all hang off it. That is the causal chain, top-down
• Timeline — the same decisions in time order with the gap between each, for when the question is sequence rather than cause
• An episode is one root cause and everything it produced. Roots are opened where they actually are — the perception witness scan and the witness fan-out — and it expires (Config.trace.episode_ms, default 8 s) so a later unrelated event cannot be swallowed into it. No module had to learn about the tree: the bus stamps the current episode, and the views assemble it
• Bounded on both axes: ped_keep entries per NPC (default 40) and ped_max NPCs (default 24, least-recently-seen evicted), so a busy street cannot grow it for a session
• /intel_debug — the debug trace: WHY something happened (client/trace.lua). Counters tell you a reaction fired; they never tell you why that one. This does. A live feed of each decision with its reason and the numbers behind it:
• reactions — "on_aimed_at → beg_for_mercy (archetype 'timid' maps this trigger straight to it)", and when a random swap fires, which chance it beat. Also why nothing happened: debounced, no archetype, no mapping for that trigger
• perception — "gunshot: 3 of 9 nearby peds witnessed it. 6 rejected (out of 100m range, no line of sight, dead, or not human)", and whether the report roll beat perception_dispatch_chance
• witness — "backs the victim up: same set 'ballas'. Attacker 1 of 4 allowed." versus "only watches: he is gang 'vagos', the victim is 'ballas' — not his set, so no solidarity"
• gossip — which ped told which, about what, at which hop of how many allowed
• state — why a ped now refuses to talk, and for how long
• voice — own voice, cast fallback, or silent, with the reason
• Colour-coded per system, capped ring buffer, filterable at the source from the panel. Free while off: every call site is guarded and the bus returns on its first line, so a disabled trace costs one boolean read per decision. While on, entries are batched to the NUI every 250 ms rather than one message per event
• The instrumentation only reports what the code had already decided — no decision point was changed to produce a line
• /intel_test — the guided test flow (client/dev_test.lua, Config.debug only). Not another pile of dev commands: an ordered walkthrough of every mechanic in the resource, 38 steps across 18 groups, from boot and bridges through perception, NPC state, all fourteen reactions, gang witness fan-out, gossip, dialogue, voice, hails, life points, street and paired scenes, ambience, police, economy, persistence, the open engine questions, and shutdown
• Each step states what to do and what should happen, switches on the debug that belongs to it, and streams the relevant state live — printing only when something changes, so the console stays readable
• Steps that can be verified without you carry an automatic check: generated data present, life-point spawn/release balance, street-scene cast fully restored after an abort, police state actually reset to zero, gossip hops greater than zero, and — for the v1.17.0 fix — that a ped which once fought is no longer in LRR_DRIVER_RAGE
• pass / fail <note> / skip record and advance; report prints the whole table with every failure note. Progress persists across a resource restart, so a full pass can be spread over several sessions
• Inline actors so a step never makes you leave the flow: /intel_test react <name>, /intel_test provoke, /intel_test hail
• Step text follows Config.locale — English and Hungarian
• /intel_inspect — the single-ped inspector (client/debug_inspect.lua, Config.debug only). Everything knowable about the ped under your crosshair, in three columns: who it is, what THIS resource believes about it, and what the ENGINE will admit to. The third column is the point — and it ends with the questions the engine refuses to answer, named one by one: seeing range, hearing range, combat attributes, flee attributes and event blocking all have setters and no getters, and there is no native at all that reports which script task a ped is running. Those six gaps are the reason relationships.lua must snapshot before it writes, so the panel shows them rather than hiding them
• Because nothing reports the running task, the panel asks GET_SCRIPT_TASK_STATUS about each task this resource knows how to issue and reports whichever answers — an honest answer to a question the engine will not answer directly
• /intel_inspect pin locks the panel to the current ped so you can walk around it; /intel_inspect dump prints one full record to the console
• Costs nothing while closed: the frame tick is registered only while the panel is open, and every read is throttled to Config.debug_inspect.refresh_ms
• /intel_scene — the always-on current-scene panel (client/scene_panel.lua, Config.debug only). The world inspector to /intel_inspect's ped inspector: live counters for every module, the running street and paired scenes with their cast, the non-lethal band and how many cops it is holding, wanted level, dispatch state, zone, time block, and what the frame dispatcher is actually drawing right now
• It is a NUI surface, so the browser owns the redraw and Lua costs nothing per frame. The snapshot is compared against the last one and the message is skipped when they match, so a scene that is not changing sends nothing at all after the first tick
• The one genuinely expensive thing it can do — sweeping the ped pool to count NPCs by owning module — is behind /intel_scene deep, off by default
• It renders as a sibling of the dialogue root rather than inside it, so it stays visible whether or not a conversation is open, and it never takes NUI focus
• /intel_lab — the engine-audit experiment bench (client/dev_lab.lua, Config.debug only). Fourteen experiments, one command each, that settle the questions the audit could not answer from documents. Nothing runs until an experiment is started, every experiment self-stops after five minutes, and spawned test peds are always cleaned up. /intel_lab lists them, /intel_lab dump replays the log
• Run witness_entities first: it is the cheapest and can invalidate the largest proposed change on its own
• Where a native could not be confirmed to exist, the harness reports the gap rather than printing a plausible-looking value — NetworkGetEntityOwner is a Cfx addition absent from the R* native database, so ownership shows n/a rather than a misleading -1
• docs/NATIVE_AUDIT.md — the full audit: the replacement table, per-system verdicts with the refuted claims kept in (so nobody re-opens a settled question), the sequenced migration plan, and the explicit list of what has no native equivalent, so nobody deletes the reason the resource exists

Changed

• Config.police_redlight.extra_light_hashes is deprecated and ignored. It fed the dead prop scanner. The key still loads so existing configs do not break. The comment now records the known gap this leaves: a player who blows through a red without ever slowing is not caught — a case that was never actually caught in practice

---

v1.16.7 — 2026-08-26

Fixed

• A cop in the non-lethal band can no longer draw a shotgun. The band holstered the weapon and forbade switching, but the ped still OWNED the gun — and GTA's combat AI re-draws an owned weapon the instant it engages, which is exactly the shotgun coming out at one star. Firearms are now physically removed for the duration and the recorded weapon is handed back on release (Config.police_nonlethal.disarm, default true)
• The window a freshly dispatched officer could still fire in is narrower: the enforcement pass runs every 400 ms rather than 750. A cop dispatched into the band arrives armed and is disarmed on the next pass, so that interval is the honest width of the gap — it is not zero

---

v1.16.6 — 2026-08-26

Fixed

• Police no longer open fire on a player with no wanted level. nonlethal_should_apply began with if stars <= 0 then return false end, so the non-lethal band deliberately skipped zero stars and left every cop fully lethal against a player who had done nothing. The band now applies whenever stars <= max_stars, so at the default max_stars = 1 lethal force begins at two stars. The arrest task is unchanged from before — it is still only issued from one star up, so an innocent player walking past a cop is neither shot at nor grabbed
• max_stars is read through tonumber. Writing it as a string (max_stars = "2") threw inside the enforcement thread and killed the band for the rest of the session, which put police back to fully lethal at zero stars with nothing in the console pointing at the config

Added

• Config.police_nonlethal.self_defence (default true). A cop you shoot or ram drops out of the band immediately and fights back with everything, at any wanted level: his snapshot is handed back, CA_ALWAYS_FIGHT is set, fleeing is disabled and he re-draws a sidearm if the band had holstered him. He is also no longer handed an arrest task while he is fighting. The exclusion is latched at every point this resource consumes GTA's last-damage flag — the cop-attack scan, the reaction sweep, the damage attributor and both scene escalations — so a second thread clearing that flag can no longer erase the fact that you shot him. /intel_nonlethal now prints self_defence and how many cops it currently excludes

Changed

• max_stars = 0 no longer disables the band. It now means "band at zero stars only". Audit your existing value: use max_stars = -1 to keep the feature installed with the band switched off, or enabled = false to remove it entirely

---

v1.16.5 — 2026-08-26

Fixed

• The wrong-sex voice, for real this time. v1.16.3 was meant to stop a man being handed a woman's voice, but it edited an older shape of the function than the one actually shipping — the live sexed_pools still read male ~= false, which sent unknown-sex peds down the male branch, and still returned the unsexed pool (277 named story characters, several of them women) and the mixed pool (sorted female-first) as fallbacks behind it. Either could be reached. Now the function answers with exactly one pool — the ped's own sex — or nothing at all, in which case the ped speaks in its own voice. Proven against the shipped data: no voice appears in both the male and the female pool, no female-named voice sits in a male pool or the reverse, and an unreadable sex is never handed a pooled voice

---

v1.16.4 — 2026-08-26

Fixed

• An NPC no longer says the same line twice. While the dialogue panel is open it already types every line the NPC speaks, but the same line was still being pushed out as a floating bubble and written into the chat feed — so one reply arrived two or three times over. v1.15.0 suppressed only the built-in floating copy and left the chat bubble and the feed writing. Now, for the ped you are actually talking to, the panel is the only place the line appears; ambient lines, gossip and street scenes are untouched and still bubble and log as before

---

v1.16.3 — 2026-08-26

Fixed

• A known sex is never handed another sex's voice. The sexed pools themselves were clean, but the fallback chain behind them was not: a male ped that found no male entry for a context dropped through to the unsexed pool — 277 named story characters, several of them women — and then to the mixed pool, which is alphabetically female-first. Now, when the ped's sex is readable, only that sex's pool is consulted; nothing matching means the ped speaks in its own voice instead. Only a ped whose sex cannot be read still sees the unsexed pool. A latched fallback of the wrong sex is dropped rather than reused. Verified over 4,000 simulated peds: zero wrong-sex picks

---

v1.16.2 — 2026-08-26

Fixed

• The spoken panel stops saying the same thing every time. tone_contexts mapped each reply tone to exactly ONE speech context, so every greeting was GENERIC_HI and every conversation line CHAT_STATE forever — flatter than the ambient speech this resource has always used, which picks from a pool per category. A tone may now be a single context or a pool, the shipped map is pools throughout, and the pick avoids what was said last, sized to the pool so a two-entry pool strictly alternates instead of repeating

---

v1.16.1 — 2026-08-26

Fixed

• Closing a conversation no longer disarms the ped you were talking to. end_focus restored the shared behaviour snapshot with combat = true, and that snapshot is written by whoever touches the ped first — for a brave, aggressive or cop archetype that is spawn-time brave_always_fight, recorded as "was off". So every conversation with such a ped silently cleared CA_ALWAYS_FIGHT, re-creating "punch him and he walks on" for that whole class of ped. The dialogue camera now releases exactly the two locks it took (the task hold and, when enabled, CA_DISABLE_BULLET_REACTIONS) and leaves everyone else's snapshot alone. It also hands a persona back its own blocking value instead of a hardcoded false
• A cop released from the non-lethal band is handed back correctly. nonlethal_restore forced CA_ALWAYS_FIGHT on for every released cop — including engine dispatch cops that never had it — and never cleared CA_CAN_BUST, so each one-star encounter left permanent state on engine-owned police. The four attributes the band writes are now recorded per cop before the first write and replayed on release: CA_CAN_BUST cleared, CA_ALWAYS_FLEE and CA_PERFECT_ACCURACY back to the engine default, and CA_ALWAYS_FIGHT restored only on cops this resource spawned and set it on
• A melee lock-on can no longer fabricate an assault victim. Perception_ResolveMeleeVictim consulted GET_MELEE_TARGET_FOR_PED (with a 7 m tolerance) before the "is the player actually swinging" gate, so raising your fists near a stranger tagged him was_assaulted and fired his on_hit reaction. Both the lock-on channel and the forward cone are now behind that gate, which is what shared/config.lua and the v1.16.0 notes always claimed
• The struck ped is reliably excluded from his own witness list. Two threads raced over GTA's last-damage flag: the reaction sweep cleared it every 500 ms while the perception resolver read it every 750 ms. The resolver now consults a short-lived cache of the ped the sweep actually saw take damage (Config.perception_victim_memory_ms), and the melee-fight witness sweep waits Config.perception_melee_witness_delay_ms (600 ms) so the punch has landed before witnesses are collected — a swing edge-triggers before any damage exists, which is why the victim used to end up in his own witness list
• victim_by_damage no longer counts vehicle damage as a punch. HAS_ENTITY_BEEN_DAMAGED_BY_ENTITY's third argument was true, so a ped clipped by your car and still standing was returned as the melee victim
• persona_block_events and persona_never_flee are live keys again. client/spawn.lua passed them only as the hands-off allow key, which is short-circuited for resource-owned peds, so their values were never read. They now gate the write the way the life_point_* keys already did
• Config.police_nonlethal.interval_ms = 0 no longer produces a permanent per-frame thread. In Lua 0 or 750 is 0; the read site now clamps to a 100 ms floor
• lethal_dispatch_services used the wrong eDispatchType ids. The default list disabled undefined service 12 and never disabled PoliceBoat. Corrected to { 2, 4, 8, 13, 14, 15 } (2 PoliceHelicopter, 4 SwatAutomobile, 8 PoliceRoadBlock, 13 SwatHelicopter, 14 PoliceBoat, 15 ArmyVehicle) against ENABLE_DISPATCH_SERVICE's own published enum, in both shared/config.lua and client/police.lua
• was_assaulted is no longer spread by gossip. Gossip copies an event onto the neighbour under the same key, so a first-person "I was assaulted" record was landing on peds who were never touched — the exact inverse of what the key documents. It ships false in Config.gossip_worthy_events; bystanders still get saw_assault from the witness sweep
• The /intel_dev menu's "Spawn test ped" entries assign their relationship group again. The demo ped was never marked resource-owned, so the assignment silently no-opped
• /intel_native_behaviour tells the truth. It printed every override as APPLIED whenever the config table was missing or the master switch was off; it now evaluates each key's real call-site gate, and flags the six keys whose call site only ever runs on peds this resource spawns

Changed

• Anna is a reporter and Denny is a mechanic in data/personas.lua. Every line either of them speaks was already written that way — Anna introduces herself as "Anna Vargas, Tribune", Pete's referral topic calls her "the reporter", and all 33 of Denny's greetings are shop talk — but role said "a bookkeeper at the pier" and "a cafe owner with ears everywhere", which is what {persona_role:...} renders mid-conversation
• was_assaulted has lines behind it. The tag was live in the dialogue engine but nothing in data/ required it, so the victim-memory feature was invisible in play. Civilian, gang, cop, homeless, working-girl and default ambient trees now greet the player who hit them
• Ambient greeting pools filled out further (thinnest is now 12 lines), and Anna and Denny each got a sixth evening greeting

Documentation

• shared/config.lua, CHANGELOG.md and INSTALLATION.md claimed that deleting Config.native_ped_behaviour falls back to "the v1.15.3 tuning exactly as it shipped". It does not — every key is read with a call-site fallback and those fallbacks are the v1.16.0 defaults, so deleting the table gives you the shipped defaults. All three now say so, and shared/config.lua lists the eleven key values that produce a genuine v1.15.3 rollback
• INSTALLATION.md §5.7 said you could ship the new Lua without the new config blocks "without any behaviour change". The opposite was true: the non-lethal band and the anti-repeat picker are both on when their config is absent. The section now says so and spells out the minimal paste for a true no-change upgrade
• Corrected the v1.16.0 content figures: ambient dialogue 1108 → 1768, static personas 647 → 965, single-variant pools 44 → 28 (not "none remain"), thinnest ambient greeting pool 3 → 12, and "six to eight" evening/night greetings for the four personas that had one of each
• routine_night_seeing_range / _hearing_range no longer imply a real snapshot: GTA exposes no getter, so the resource writes back a fixed 30.0 when the night block ends. The same caveat is now stated for the cleared flee bitfield
• assign_relationship_group / assign_block_events are documented as reserved for callers who invoke IntelNpcRelations_AssignToPed on a borrowed ped — nothing in the shipped resource does
• README.md's non-lethal paragraph now describes what is actually restored on a released cop

Added

• Config.perception_victim_memory_ms (default 1500) and Config.perception_melee_witness_delay_ms (default 600), both documented in shared/config.lua
• Perception_NoteStruckPed(ped) — the reaction sweep hands the resolver the ped it just saw take damage, before it clears GTA's last-damage flag. Call it from your own damage handler if you task melee damage yourself

---

v1.16.0 — 2026-08-26

Fixed

• Punch a ped and he no longer walks on. data/ped_flags.lua's combat-attribute numbers were wrong, verified against PED::SET_PED_COMBAT_ATTRIBUTES (0x9F7794730795E019) in FiveM's own native database: CanUseCover was really CA_ALWAYS_FIGHT, and DisableBulletReactions was really CA_ALWAYS_FLEE. So configure_for_combat — the function every single fight reaction goes through — was setting always flee on the ped it was about to task into combat, and the gang-toughness sweep was never setting always fight at all. Every key name is unchanged; the numbers are corrected and the file now carries the full verified enum
• The ped you hit is no longer recorded as a witness of his own assault. saw_assault was landing in the victim's own memory because the melee watcher collected every ped in visual range and the victim is by definition in visual range. The struck ped is now resolved properly (GET_MELEE_TARGET_FOR_PED, a damage read, and a lock-on and forward-cone fallback that only fire while the player is genuinely swinging, so a mere melee lock-on cannot fabricate a victim), excluded from the witness sweep, and given his own was_assaulted memory tag with a 6 h TTL, which ambient civilians, gang members, cops, homeless and working girls now have lines for. It is deliberately not gossip-worthy: gossip copies an event onto the neighbour under the same key, so spreading a first-person "I was assaulted" record would land it on peds who were never touched
• Being punched now produces the victim's own reaction. A gang member fights back, a coward flees, a cop moves to arrest — chosen by the victim's archetype, through the same on_hit trigger as before. It no longer depends on the ped taking damage, so damage-proofed ambient peds react too, and the victim is no longer swept into bring_witnesses_to_face's task clear, which was separately cancelling his reaction
• Reaction cooldowns are tracked per trigger. Aiming a weapon at an NPC no longer swallows the punch that follows a second later. on_hit gets its own shorter cooldown (Config.reaction_hit_debounce_ms, 2500 ms)
• cop_engage_combat was clearing CA_ALWAYS_FIGHT on responding officers one line before tasking them into combat
• Ambient peds are no longer shipped with five stacked "ignore the world" flags. IntelNpcRelations_AssignToPed was setting blocking-of-non-temporary-events, disable-shocking-events (config flag 281), disable-bullet-reactions and a wiped flee bitfield on every ped it touched, and life points additionally had alertness pinned to 0 and critical hits switched off. A ped carrying all of those cannot notice being punched. All of them are now opt-in override keys under Config.native_ped_behaviour, defaulting to GTA's own values
• Config.block_temporary_events works again. IntelNpcRelations_AssignToPed slammed it back to a hardcoded true nine lines after client/spawn.lua had read the key, so setting it false had no effect at all
• Peds you talk to are handed back to the engine unchanged. client/focus.lua cleared the flee bitfield and set disable-bullet-reactions on every ped a conversation opened on — including engine-owned pedestrians — and never restored either. Every random ped you had ever spoken to was left permanently unable to flee. Both are now off by default on borrowed peds and snapshot-restored on every exit path, hostile and panicked included
• A witness that cowers stops cowering. The ForceCower flee flag was set on every civilian witness and never cleared, so a ped that cowered once stayed cower-flagged for the rest of its life. It is cleared after Config.perception_cower_ms (8 s)
• Stopping the resource while it was suppressing police no longer leaves the session broken. client/ai_suppression.lua could exit with dispatch services dead and SetPoliceIgnorePlayer(true) still set; it now restores them on stop, and only if it actually suppressed anything
• {player_name} expands in ambient dialogue. render_topic_menu built its mention context from session.persona_id, which is nil for an ambient ped, while every other line in the file already used session.memory_key — the key the player's name is actually stored under. Introduce yourself to a pedestrian and his greetings degraded to "friend" from then on
• Conversations stopped sounding monotonous. The line picker was a bare math.random over the pool with no memory of its last pick — measured over 400 draws, a 3-line pool repeated itself back-to-back 34% of the time and a 5-line pool 20%, which is what made large pools sound small. Every pool now keeps a short ring of the lines it just used and re-rolls while the pick is still in that ring; measured back-to-back repeats drop to zero on every pool the player actually hears

Added

• Config.native_ped_behaviour — one table, one rule: engine-owned pedestrians keep GTA's own pedpersonality tuning, peds this resource spawns are configured by this resource. Every key is an override switch whose annotation names the native default, so vanilla behaviour is one line away, and everything this resource does change on a borrowed ped is snapshotted before the write and restored when the ped is let go. Deleting the whole table does not restore v1.15.3: every key is read with a fallback at its call site and those fallbacks are the v1.16.0 defaults, so you get the shipped defaults (GTA's own reaction defaults on ambient, dialogue and life-point peds). The table's own block comment lists the eleven keys to set for a genuine v1.15.3 rollback
• Config.police_nonlethal — police never use lethal force at or below a configurable wanted level (default 1 star). GTA's own levers first: lethal dispatch services off, optional SET_WANTED_LEVEL_DIFFICULTY, cops forced to WEAPON_UNARMED with weapon switching blocked and accuracy 0, CA_ALWAYS_FIGHT cleared, CA_CAN_BUST set and TASK_ARREST_PED at close range. This is a band, not a pacifier — above max_stars police are unchanged. Every touched cop is snapshotted and restored, and the whole thing no-ops when another resource owns the police (yield_to_resources, require_police_system, or native dispatch being in charge)
• Config.line_no_repeat_depth / Config.line_no_repeat_tries (default 3 / 6) — the anti-repeat line picker. Depth is capped automatically at half the pool size, so small pools alternate instead of cycling in a fixed order. 0 restores pure-random picking
• Config.perception_victim_enabled / _range / _cone_dot / Config.perception_cower_ms and Config.reaction_hit_debounce_ms, all documented in shared/config.lua
• 660 new ambient dialogue lines and 318 new static-persona lines (ambient 1108 → 1768, static 647 → 965). Single-variant pools are down from 44 to 28 — every greeting, farewell and response pool the player hears in normal conversation now has multiple variants, and what is left are rob/mug outcome and counter-question stubs. The thinnest ambient greeting pools went from 3 lines to 12+, and every static persona that had exactly one evening and one night greeting now has six to eight
• Mood tags are live in dialogue. Config.mood_pool was rolled, displayed on the panel and applied to the face, but across 1108 ambient entries not one carried a mood tag — so every civilian spoke in one voice regardless of the badge. 221 ambient and 126 static entries are now mood-written, and ambient dialogue also uses the memory tags (first_time, met_recently, long_time_no_see, frequent_visitor, known_to_npc) and perception tags (saw_assault, heard_saw_shooting, …) that it previously ignored entirely
• refusal.prostitute in both language packs — working girls fell through to the 3-line refusal.default. The other five refusal.* pools were expanded too, with existing lines kept verbatim, and refusals are the single most-heard ambient string set on the server (Config.ambient_refusal_chance is 0.75 for gang and 0.85 for cop)
• was_assaulted in Config.gossip_worthy_events (shipped false — see above) and Config.action_memory_event_ttl_ms
• New globals for anyone extending the resource: IntelNpcBehaviour_* (apply + snapshot + restore), IntelNpcOwnedPedSet, IntelNpcCombatAttr (the verified eCombatAttribute names), pick_fresh in shared/locale.lua and Utils.pick_contextual_raw for the un-wrapped original picker
• Dev commands /intel_native_behaviour and /intel_nonlethal (both need Config.debug)

Changed

• Life-point peds react like ordinary pedestrians. They flee, flinch, take critical hits and can become alert. shared/config.lua always said life points are deliberately not static personas, "which is what lets hail / perception / gossip / trauma treat them like any engine ped" — the decoration contradicted that. For the old statue behaviour set life_point_block_events, life_point_never_flee and life_point_disable_explosion_reactions to true, life_point_suffers_critical_hits to false and life_point_alertness = 0
• A ped this resource tasks into a fight now flinches when it is hit. CA_DISABLE_BULLET_REACTIONS in configure_for_combat is behind Config.native_ped_behaviour.combat_disable_bullet_reactions, off by default — a hostile ped that shows no reaction to being shot is the visual half of "he walks on"
• IntelNpcRelations_AssignToPed(ped, group_name, opts) takes an optional third argument ({ block_events = bool }). The two-argument call is unchanged and still follows Config.block_temporary_events
• The night-routine block no longer pins persona alertness to 0 during the day, fighting the engine's own dynamic alertness on every tick; it restores the pre-night value instead. Its values are exposed as routine_night_alertness / routine_night_seeing_range / routine_night_hearing_range

---

v1.15.3 — 2026-08-26

Fixed

• Paired scenes no longer degrade every time. The walk-in required the player to move less than 0.5 m and turn less than 35 degrees while the NPC covered the distance — nobody stands that still, so the handshake aborted on degraded_drift before it started. The gate now asks the question it meant to ask: are you still with this NPC — close enough, still roughly facing them, and not wandered off from where you began
• No more teleport after a paired scene. A life-point ped left its scenario spot to shake your hand, and the re-task watchdog then warped it back the instant the scene released it. It walks back now instead

---

v1.15.2 — 2026-08-26

Fixed

• Ambient NPCs keep their own voice. Config.dialogue_speech.fallback_for_unknown_voice shipped true, which cast a pool voice over every ped the resource had not cast itself — but the game had already given that ped a voice matching its model, correct in sex and character. Overriding it is what put a woman's voice on a man, and v1.15.1's sex-split pools only narrowed the damage instead of removing the cause. It ships false: an untracked ped speaks in its own voice, or stays silent if that voice has no take for the line. Personas, whose voice this resource does cast and can therefore check, still fall back within their own sex

---

v1.15.1 — 2026-08-26

Fixed

• A man gets a man's voice. The fallback voice pools in data/generated/voice_contexts.lua are now split by sex (_by_context_m / _by_context_f / _by_context_x) and the pick is made against IsPedMale. The old single pool was capped alphabetically, so every AF name sorted ahead of every AM one and a 24-name GENERIC_HI pool ended up entirely female — every man who needed a fallback line got a woman's voice
• Config.default_gta_voice_name is no longer handed to female personas unchanged. It ships as a male voice, so the three shipped female personas that declare no gta_voice_name of their own (Erika, Anna, Candy) were given it at spawn — and because SetAmbientVoiceName was already male, the new sexed fallback could never correct them. The default is now checked against the ped at spawn and swapped for that sex's voice when it provably does not match. A default whose name encodes no sex, or a persona that names its own voice, is left exactly as configured
• A fallback voice no longer changes between lines of one conversation. The pick was stable per context, not per ped, so the same NPC could say hello as one person and goodbye as another. The chosen voice is now latched to the ped and reused for every following line it has a take for
• A missing sexed pool no longer silences every NPC. The _m -> _x -> _by_context fallback chain was walked with ipairs over a table that could hold nil, which stops at the first hole and did nothing at all when the first pool was absent. The chain is walked explicitly now, and a data/generated/voice_contexts.lua older than this change prints one clear warning telling you to regenerate it
• Every whitelisted speech context now has a male and a female pool. GENERIC_FUCK_YOU is supported only by named story characters, whose names carry no sex, so both sexes fell through to one mixed pool where roughly a third of the entries were women. The generator now sexes those named voices
• Config.simpleasf.rep_rank = false no longer silences two other surfaces. The flag early-returned out of the whole rep-change hook, which also killed the trust-down toast and the trust-tier promotion achievement banner that Config.simpleasf.achievements still advertised as on. It now gates the screen-centre rank/XP overlay and nothing else — with it off, a trust change outside the dialogue panel is a quiet toast, and promotions still raise their achievement

Changed

• Config.simpleasf.rep_rank ships false. The XP-style rank banner after a conversation reads as a game-y overlay on a roleplay server. The dialogue panel header's trust bar carries the same signal without covering the NPC's face. Turn it back on with Config.simpleasf.rep_rank = true
• /intel_paired picks the ped you are looking at with the same forward-cone search the quick-talk key uses, instead of a hairline camera ray that missed a ped standing slightly off-centre and reported "no ped in front of you"
• tools/generate.js is v1.2.0. The generated header's counts now cover all four pool tables instead of only _by_context, and the metadata-key note names all six keys. Output is byte-identical across re-runs, as before

New

• Config.paired_scenes.dev_target_range (12.0 m) and Config.paired_scenes.dev_target_min_dot (0.5, ~60°) — the search radius and cone that decide which ped /intel_paired acts on

---

v1.15.0 — 2026-08-26

Changed

• Every city-life module ships on. Config.scenario_groups, Config.street_scenes, Config.paired_scenes and Config.dialogue_speech join life_points and world_ambience — a feature nobody can see is not a feature. Each one is still a single enabled = false away from off, and every sub-toggle and cap is unchanged
• README and INSTALLATION restate what ships on, and the spoken-panel section says plainly what to listen for before going live: the bark is a canned English line, not your written text

---

v1.14.0 — 2026-08-26

Changed

• Config.world_ambience ships on, with its car radios, ambient boats and garbage-truck rounds all enabled — the layer did nothing on a fresh install, which is not what an ambience feature is for
• Config.debug ships on, so /intel_dev, the F12 dev menu, every /intel_* command and the debug overlays work the moment the resource starts. Turn it off for production with setr lastresort_intel_npc:debug 0 in server.cfg — the convar overrides the config file, so you never edit it back

---

v1.13.0 — 2026-08-26

New

• Street scenes (Config.street_scenes, ships OFF) — authored two- and three-ped conversations that play out on the pavement between peds that were already standing there. Nothing spawns: the module borrows peds out of the live population, plays real GTA ambient speech through their own voices, puts the resource's normal bubbles over their heads, and hands every borrowed ped straight back to the ambient AI
• Seven scripts ship in data/street_scenes.lua — corner gossip, a street argument, a lost tourist, an evening corner deal, a three-hander shift change, a panhandler, and two officers killing time — in the same commented style as data/life_points.lua, with the full entry schema documented in the file header
• Speech and bubbles never overlap. One line at a time, one speaker at a time; the next line cannot begin until the previous bubble has expired, and the previous speaker's audio is stopped explicitly when the speaker changes. A line whose voice has no take for its context (which fails silently in the engine) holds for a length derived from its own text instead of stalling the scene
• A line marked gossip_payload performs a real gossip hop at the moment it is spoken — the speaker's newest gossip-worthy memory is pushed into the rest of the cast through the same NpcState_AbsorbGossip path the gossip loop uses, hop count and confidence decay included. A line with a bubble_seen variant switches to it when the cast actually remembers the player
• You can cut in. Inside the entry's interject.radius a prompt appears (help box, floating text3d, or none); taking it ends the scene, restores the whole cast and opens the normal dialogue panel on the nearest speaker
• Every abort path restores every cast ped — damage, death, despawn, gunfire, panic, hostility, fleeing, ragdoll, combat, entering a vehicle, a cast ped leaving its leash, player death, teleporting away, the config being flipped off mid-scene and resource stop all route through one teardown: tasks cleared, blocking flag cleared, busy cleared, back to the ambient AI. A wall-clock watchdog and a guarded tick chain cover the rest: a scene that outlives its own line budget, or a tick that throws, tears the whole cast down instead of stranding it
• A scene is client-local. No event, no state bag, no server call — each player sees it on their own copy of the population
• Paired synchronized interactions (Config.paired_scenes, ships OFF) — trust made physical. A greeting from an NPC who trusts you becomes an actual handshake, a familiar gang contact gets a dap, and giving an item, bribing or tipping becomes a real hand-over: the NPC walks into the slot in front of you and both of you play the two halves of one synchronized animation. A hug ships as flavour, disabled
• It is a cosmetic and nothing else. It never gates, blocks or changes an interaction outcome. The NPC cannot reach the slot, the ground is not flat, you turned away, the anim dictionary would not stream, the ped got scared — every one of those degrades silently to exactly the behaviour of the previous version, and the dialogue panel opens either way: after the handshake when there was one, immediately when there was not. A half-played handshake looks worse than no handshake
• Initiator-only by default. networked = false uses the local synchronized-scene family, so only the player who triggered it sees the two peds animate — no network traffic and no way to desync anyone else's view of the ped. networked = true widens it when you want it
• Both peds are handed back on every path — tasks cleared, look cleared, keep-task off, blocking flag off, busy cleared. A watchdog armed the moment the NPC is tasked ends a scene whose poll chain died, and the module being flipped off mid-scene ends it on the next poll. A ped that was in a scenario is left for the engine to put back, a persona pulled off its authored spot is walked back to it, everything else goes to the wander AI. player_in_scene = false keeps the player's own ped out of it entirely
• data/generated/anims.lua now carries validated animation pairs. Every dict / clip_a / clip_b named in Config.paired_scenes — including the fist-bump alternative the config comments document as a one-line swap — is checked at build time against the reference anim data, and a typo fails the build instead of shipping a T-pose. The table was empty until now
• /intel_scene_play — street-scene status, every registered scene with its preset, weight, role and line counts, remaining cooldown and whether it is allowed right now, plus a live row per running scene. /intel_scene_play <id> force-starts one past chance, cooldowns, time block and the distance floor; /intel_scene_play stop aborts every live scene and restores every cast ped. Gated on Config.debug
• /intel_paired <kind> — force the named paired interaction on the ped you are looking at, past the enabled flag, trust tier, category and cooldown, and report the outcome or the refusal reason. Gated on Config.debug
• /intel_status grows a counter block for each module — scenes registered and dropped, live runs, cast peds, scans, attempts, cast failures, lines with own-voice / fallback / silent / timed-out splits, bubbles, gossip hops and interjections for street scenes; requests, starts, completions, every refusal gate, every degrade path and the last kind and reason for paired interactions
• New client globals — IntelNpcScenes_AbortAll(reason), IntelNpcPaired_Try(ped, kind, opts, on_done), IntelNpcPaired_Eligible(ped, kind), IntelNpcPaired_IsActive(ped), IntelNpcPaired_Abort(reason), and the event lastresort-intel-npc:client:pairedScene
• New locale keys — street_scenes.*, scenes.*, paired.*, status.street_scenes_header and status.paired_scenes_header (en and hu shipped)

Changed

• A hail no longer fires at a ped another module is already using. All three hail candidate scanners (personas, ambient peds and the prostitute scanner) now skip a ped marked busy, which closes the window where a hail could re-task a ped mid-street-scene and spin them away from the conversation
• The life-point scenario watchdog leaves a borrowed ped alone, the same way it already left a hailing ped alone: it now also stands down while the ped is marked busy or is in a live paired interaction, so it cannot re-task a ped out from under a scene it did not start
• Opening an ambient dialogue tries the dap and then the handshake before the panel opens. When one is accepted the panel is skipped for that press — the handshake is the greeting — and the paired scene fires before the focus camera freezes the player, which a synchronized scene cannot survive. With Config.paired_scenes.enabled = false (the default) both calls return immediately and the panel opens exactly as before
• Giving an item, bribing or tipping fires the hand-over after the interaction has already succeeded, so the animation never sits between the player and the result
• The city life layer is now five modules, not three. shared/config.lua, the README and INSTALLATION all describe it that way; life points remain the only one that ships on

---

v1.12.0 — 2026-08-26

New

• Spoken dialogue panel (Config.dialogue_speech, ships OFF) — every line the dialogue panel types can be paired with a tone-matched GTA ambient bark in the NPC's own voice, and the typewriter's completion is tied to the audio instead of to the character count. The line's tone (greet, farewell, kick, bribe, threaten, investigate … the same tone keys the panel colours its choice chips with) maps to a speech context through Config.dialogue_speech.tone_contexts
• The audio and the text start together. The panel tells the client the moment the typewriter actually begins, so the bark no longer leads by the length of the "…typing" pause
• It cannot hang. The written typingSpeed is the floor — audio only ever makes the text hold on its last character or drain faster (catch_up_ms) to catch up, never type slower. The panel enforces its own max_wait_ms deadline independently of the client, so a bark that never starts (very common — a voice with no take for a context fails silently) or one that runs long still completes the line. SPACE and ESC both cut the audio
• No permanent threads. IsAmbientSpeechPlaying is polled on a poll_interval_ms timer that only exists while a line is actually speaking
• Persona voice validation (Config.validate_persona_voices, ships ON) — every persona's gta_voice_name and Config.default_gta_voice_name are checked at boot against the shipped voice list. A name GTA does not have makes SetAmbientVoiceName a silent no-op and leaves the NPC mute forever with nothing in the console to explain it; now it produces one clear warning naming the persona and the bad value, and falls back to a valid voice instead of being silently wrong
• Per-context fallback voice casting — no voice in the game covers every context this resource uses, so there is no single "does everything" fallback. Each context has its own pool of voices known to have a take for it, preferring ordinary ambient civilian voices, and the pick is deterministic per ped so the same NPC always falls back to the same voice. Exposed as IntelNpcVoice_ForContext(ped, context) → supported, fallbackVoice; the answer is cached per ped and swept when the ped is gone
• data/generated/voice_contexts.lua — generated reference data shipped with the resource: which ambient voice names are real, and which of 17 ambient speech contexts each of them has a take for. Client-side only, nothing fetched or parsed at runtime
• /intel_voice <context|tone> — for the ped you are looking at: the voice this resource assigned it and whether that name is real, whether the context is checkable, whether the ped's own voice has a take for it, the fallback that would be cast, and the exact native call that would be made. Gated on Config.debug
• /intel_status grows a voice/speech counter block — validation results, per-ped cache hit rate, own-voice vs fallback vs degraded answers, and how the last spoken lines ended (natural, never started, timed out, skipped)
• New locale keys — status.voice_header and the voice.* family (en and hu shipped)

Changed

• Maggie's gta_voice_name was A_F_M_BUSINESS_02_BLACK_FULL_01, which does not exist — that variant was never shipped by the game, so SetAmbientVoiceName silently did nothing and she has been falling back to whatever her model came with since she was written. Corrected to A_F_M_BUSINESS_02_WHITE_MINI_01, the real ambient voice for her a_f_m_business_02 model. The new boot check is what found it
• While a panel line owns an NPC, the older per-pool speech is suppressed for that NPC (Config.speech_on_dialogue_open, speech_on_topic_select, speech_on_farewell) so the two cannot cut each other off. Those flags still drive every speech outside the panel, and with Config.dialogue_speech.enabled = false nothing changes at all
• data/generated/ is described as build-time reference data shipped with the resource in README, INSTALLATION, CHANGELOG, shared/config.lua and the generated files' own headers — one consistent description everywhere: committed Lua tables, built offline by a developer-only step, never fetched or parsed at runtime
• The developer-only build tooling was tidied and renamed — the fetch step is now tools/fetch_refs.sh and writes to the git-ignored tools/refs/; tools/README.md, tools/generate.js, its error messages and the regenerate line in every data/generated/*.lua header all follow. Nothing loaded or executed changes — tools/ is still absent from fxmanifest.lua and server owners still never run it. The generated tables' data is unchanged; only their headers were rewritten, and a re-run of the generator is byte-identical. tools/ is now documented as excluded from the release package rather than as something the buyer may delete

---

v1.11.0 — 2026-08-26

New

• Red-light posts (red_light_district life-point preset) — night-only working girls on the kerb in Strawberry, Davis, Mission Row, Textile City, Cypress Flats, La Mesa and Banning, and a higher-class scenario uptown in West Vinewood, Rockford Hills, Vespucci Canals and Del Perro. They stand on the world's real bus-stop pavement points, not hand-typed coordinates
• The prostitute hail lines finally fire. The dedicated scanner, the 14 authored lines, the per-category cooldown and the service flow have all shipped since v1.5.0 — what was missing was anyone to hail from, because the vanilla population almost never spawns a working girl. Mechanics only; no new adult content
• Config.life_points.presets_enabled.red_light_district turns the whole preset off in one line

Changed

• Config.life_points now ships ON. It was off by default since v1.9.0, which meant nothing spawned and the red-light preset above could never fire on a stock install. max_active is unchanged at 12 — that hard ceiling is still the performance budget, so lower it to 6 (or set Config.life_points.enabled = false) if your server is already heavy
• *furniture.enabled now gates only the four `furniture_` presets**, as its name and its own comment always claimed. It used to switch off every zone-form entry, which would have silently taken the red-light preset with it
• Bus-stop waiters are day-only (time_block morning/day/evening). They share the generated bus-stop points with the red-light entries, and in the zones that hold exactly one stop a waiter parked there in the evening blocked the kerb all night
• A hailing ped is left alone by the scenario watchdog, so a working girl no longer turns away mid-line when the 15 s re-task tick lands inside the 8 s bubble
• The prostitute hail bubble uses the localised speaker name (ambient.prostitute) instead of a hardcoded English "Working Girl", so the Hungarian pack reads correctly

---

v1.10.0 — 2026-08-26

New

• Provoking an NPC now has a physical answer chosen by their character — past the snap they either throw hands, bolt, or fall through to their archetype's own reaction (beg, curse and walk off, or square up), instead of the old silent walk-off. Config.provoke_flee_chance is the new roll (cowards 0.80, the brave and the armed 0.00), taken only when the fight roll does not win
• The fight and flee outcomes now leave a record — trauma, fear, the persona reputation hit and the memory tag are applied on all three post-snap branches, not just the fall-through one

Changed

• NPCs are easier to push over the edge. Archetype provoke thresholds drop (coward 6 → 4, brave 4 → 3, everyone else 5 → 3, gang 3 → 2, cop unchanged at 3) and Config.npc_default_provoke_threshold follows 5 → 3
• The two-jab floor and the first-provocation guard both still stand — Config.npc_min_provoke_threshold and Config.npc_first_provoke_never_snaps are unchanged, so the first jab of an encounter always lands at least one step short of the snap and nobody swings on a single click. The extra ease comes from the lowered thresholds, not from removing the guard
• More of them fight back — Config.provoke_fight_chance raised across the board (compliant 0.15 → 0.35, cunning 0.10 → 0.25, stoic 0.35 → 0.55, brave 0.65 → 0.85, default 0.15 → 0.35)
• A provoked cop warns before drawing — the fight branch routes the cop archetype through its own arrest_warning instead of straight to draw_and_fight
• The dev menu opens with F12, not F7 (Config.dev_menu_key)
• A slimmer trust and composure readout in the dialogue header — fixed-width labels, 3px tracks and tighter rows, so the two bars stop competing with the NPC's name

---

v1.9.0 — 2026-08-26

New

• The city life layer — three modules, all shipping OFF — Config.life_points, Config.scenario_groups and Config.world_ambience. No permanent per-frame threads: every loop runs at one of the resource's existing cadences (15 s hail tick, 30 s routines tick)
• Life points (data/life_points.lua, client/life_points.lua) — declarative "extras casting": 16 authored entries across five presets (Vespucci beach, downtown tourists, gang blocks, labor, night life) plus four that seat peds on the world's own furniture — ATMs, benches, parking meters, bus stops — read from the generated world-point tables, 20 in all. They are tagged with a category, so hail, perception, gossip and trauma pick them up like any engine ped; they are not personas and have no dialogue tree, persistence or blip
• Life-point safety rails — hard max_active ceiling, 80 m/140 m spawn-cull hysteresis, minimum gap to the player and to other peds, per-zone counts scaled by Config.density_manager.by_zone, and four independent release paths (teleport jump, distance cull, proximity-point exit, death/respawn). Every scenario name is validated at boot against the generated scenario table and every model against IsModelInCdimage/IsModelValid; anything that does not resolve is dropped with a console warning naming the entry. IsScenarioTypeEnabled is checked separately on every spawn attempt — a globally disabled type rotates the entry's pool instead of dropping it, and surfaces as the disabled-type skip counter in /intel_status
• Life-point scenario re-task (Config.life_points.retask_enabled, on by default) — life points are deliberately outside the static-persona set, so perception, witness reactions and the reaction layer clear their tasks when they turn a bystander to face you. The scan tick now checks whether a ped has fallen out of its scenario and puts it back, so an authored preset survives the first player interaction instead of leaving everyone standing. Counted as re-tasks in /intel_status
• Persona seat warp (Config.life_points.routine_seat_warp, off by default) — a static persona whose scheduled spot lands within a few metres of a real seat point sits on it instead of playing a standing animation beside it; wired into both the spawn path and Routines_TrySoftRelocate
• Dormant scenario groups (Config.scenario_groups) — flips on the ambient content Rockstar ships switched off (the blimp, LSIA airliners, cinema queues, bank ATM crowds, the Ammu-Nation clerk, impound cops). Nothing spawns; the module only writes the switch. Names are validated against the generated group table and DoesScenarioGroupExist, matched case-insensitively, and each group's original state is recorded and restored on resource stop
• World ambience (Config.world_ambience) — ambient NPC car radios tuned to real stations and audible from outside (never your car, another player's car, a mission entity, a resource-created vehicle or a car carrying a persona; prior radio state recorded and restored, capped and faded in), plus ambient boat traffic and garbage-truck rounds re-asserted against engine resets
• data/generated/ — committed, human-readable reference tables built at build time from reference data: scenario names with their kinds, 223 scenario group names, radio stations, driving styles, and world prop coordinates pre-bucketed by zone. Client-side only, and only the ones a module actually reads are listed in fxmanifest.lua — driving_styles.lua and its table are staged for a later phase and are not loaded. The tools/ pipeline that produces them is developer-only — server owners never run it
• New dev commands — /intel_life_reload (re-validate and re-register life points without a full restart), /intel_scenario_groups, /intel_ambience and /intel_ambience release. All gated on Config.debug
• /intel_status grows two counter blocks — one per city life module, pcall-guarded so a disabled or absent module cannot break the command
• New locale keys — status.life_points_header, status.world_ambience_header (en and hu shipped)

Changed

• shared/config.lua grew to ~2,400 commented lines — the three new blocks sit next to Config.density_manager, Config.disabled_scenario_types and Config.persona_blocking_area_radius, with every threshold, count, distance and cooldown exposed and annotated

Known trade-off

• Config.disabled_scenario_types still ships with 'WORLD_HUMAN_MUSICIAN' disabled (the "street musicians at the docks intel drop" fix). The Vespucci boardwalk-performer life point detects this at spawn and rotates to its other scenarios, so it runs in a degraded state until you remove that line — deliberately left as the operator's call
• Releasing a touched vehicle radio always clears the loud flag: the game exposes no getter for it, so a car another resource had set loud comes back un-loud

---

v1.8.0 — 2026-08-26

New

• New locale keys — nui.ends_chat, nui.tone_* (22 tone labels), dialogue.body_provoked_high / low, fx.snapped (en and hu shipped)

Changed

• The picked reply stays visible — choosing a reply (mouse or 1–9) lights that row pink and recedes the rest while the answer round-trips, instead of swapping the whole list for a spinner
• The sentence leads every reply row — choice text now sits above the metadata chips, the generic dialogue/topic tone chip and the ever-present "Continue" chip are gone, and the row that ends the conversation is the one that gets a marker (nui.ends_chat); raw tone keys (introduce_self, …) render through the locale pack (nui.tone_*) instead of leaking underscores
• Chat stream de-cluttered — the real-world wall-clock timestamp on every bubble is gone and the speaker label only renders when the voice changes, so an NPC's bubbles read as one grouped voice under the header
• Legibility pass, computed against WCAG — the recent-choices trail moves to full-strength tone colours at 11px (was ~2.8:1, now ≥5.5:1), disabled rows keep their lock-reason chip at full strength instead of dimming the whole row to 0.42, system messages move from 11px tracked mono to the display face at 12px muted, the 1–9 key numerals step up to 17px warm white, and the choice subtitle drops the italic triple de-emphasis
• Every remaining status merged top-right — the impatience warning moves from floating over the choices into the NPC header under the composure bar; the provoke escalation and mid-conversation trust-rank overlays no longer render screen-centre while the panel is open (the header trust bar and chat-stream notes carry them); money / item / trust-down toasts anchor to Config.simpleasf.dialogue_toast_position (top-center) during dialogue; the built-in floating bubble no longer duplicates panel lines over the in-session NPC's head; the mood-icon rects pause while the panel is open
• The header paints complete on open — composure and patience are seeded in the open payload instead of popping in ~300 ms later mid-entrance, and the witnesses + patience pills share one chip row so the header stays balanced; the witnesses pill only turns warning-orange when someone is actually watching
• Long choice lists announce themselves — rows past the fold dissolve into a scroll fade, rows 8+ join the entrance stagger, and choices/topics are keyboard-focusable (Enter activates, the focus ring finally renders)
• Reduced-motion players see trust deltas — the +/- popup shows statically for 1.5 s instead of living only inside the disabled float animation
• Spacing normalised onto the token scale — the ad-hoc 5/6/7/9/14/15 px gaps across the header, stream, topics and choices move to --lr-space-*
• Hungarian covered — the provoke path's hardcoded English (Furious, body-language lines, They snapped!) routes through the locale packs (dialogue.body_provoked_*, fx.snapped, mood.*)

---

v1.7.0 — 2026-08-26

Changed

• The conversation status lives in the header — a teal composure bar under the trust bar and an hourglass patience chip beside the mood badge, refreshed live during the conversation; the floating bottom-centre notify card is now off by default (Config.simpleasf.conversation_card = true brings it back)
• A more readable chat — taller message area, wider bubbles with looser line-height, a teal edge on NPC bubbles so the two voices separate at a glance, softer tracking on the small-caps labels
• Reply rows lost their echo — the intent chip no longer repeats the reply text when the two were identical; it falls back to the tone name
• New locale keys — nui.composure, nui.patience (en and hu shipped)

---

v1.6.0 — 2026-08-26

Changed

• One HUD surface instead of two — the top-left corner stack (location, witnesses, duration) is gone; the dialogue screen carries a single panel in the top-right
• Witnesses live in the NPC header — an amber eye chip under the mood badge, hidden while the count is unknown; location and time were already in the header's tag line, and the duration counter is retired
• A calmer header — flatter background wash, tighter spacing, smaller avatar without the pulsing dot, so the identity, mood, witness count and trust read at a glance

---

v1.5.0 — 2026-08-26

New

• lastresort_chat integration — while the chat resource is running, every floating NPC line (hails, gossip, dialogue replies, police chatter) renders through its 3D speech bubble, and the line lands in the chat feed as speaker: line on the overhearing client
• Built-in fallback — with lastresort_chat absent the built-in bubble renderer takes over on the very next line, and the feed write speaks the stock chat:addMessage event so the default chat resource understands it too; a player who turned speech bubbles off in the chat settings keeps that choice
• Config.integrations.chat — master toggle, separate bubbles / feed switches, the bubble's chat mode (say / loud / gentle) and the feed colour
• While the chat renders the bubble, its speechBubbles settings govern lifetime and styling — the per-line durations and the gold speaker sub-line apply only to the built-in renderer
• shared/adapters/chat.lua — the whole integration is one pcall-wrapped adapter, probed per line, so a chat restart mid-session needs nothing from this resource

---

v1.4.0 — 2026-08-26

Changed

• The dialogue panel wears the Vice look — deep purple-black night ground, hot pink accent, the four-stop sunset gradient (pink → rose → orange → gold) on the panel's leading edge and display type
• Teal is the one cool accent — info and telemetry colours move off generic blue
• The trust meter fills gold, and every reply-tone colour is re-cast into the same palette
• Notify-card accents now match the panel, so both surfaces read as one product
• nui/theme.css defaults re-documented — the token notes in the override sheet reflect the new palette
• The NPC tag is a condensed uppercase eyebrow — display face at 11px with 0.18em tracking in the accent colour (was 13px muted body text), and the message-header tracking widens from 0.16em to 0.18em
• The docs say what is true: no escrow — the README no longer claims Tebex asset escrow; every file ships readable and editable, and the licensing section says so plainly

Removed

• escrow_ignore from fxmanifest.lua — inert on an un-escrowed install and it contradicted the docs
• The Keymaster entitlement troubleshooting entry — that error cannot occur on an un-escrowed resource

---

v1.3.1 — 2026-08-12

Fixed

• A stuck cursor after closing the dialogue panel — the panel now always releases its own NUI focus on close, even when another suite resource has signed the shared lrNuiOwner state key

---

v1.3.0 — 2026-08-11

Changed

• General improvements and internal cleanup
• Stability and consistency fixes across the dialogue panel and the config
• README and INSTALLATION brought back in line with what ships

Fixed

• Assorted minor bugs found in testing

---

v1.2.0 — 2026-07-26

New

• NPC errands — personas offer authored jobs from data/jobs.lua, with a HUD tracker, map blip and /intel_jobs
• Errands are server-validated — every step, and the run survives a restart; expiry or abandon costs trust
• Bounty board — broker personas take a stake-funded price on another player; /intel_bounties reads the shared board
• Bounty payouts settle server-side on a confirmed kill, and standing NPC contracts settle off the rob/mug flow
• Trade pricing — shop prices scale with reputation tier (Config.trade)
• Haggling — a server-rolled attempt wins a session discount or insults the persona
• Routines build-out — hidden off-shift blocks, in-place re-tasking, night alertness, a night mood skew, per-block arrival lines
• New config and tables — Config.npc_jobs, Config.bounty_board, Config.trade, Config.routines, the npc_jobs and global tables, the bounty_broker flag

Changed

• Purchases charge the quoted per-player price, not the flat catalog number; the menu shows the tier and any discount
• Persona proximity accepts every spot in that persona's schedule, so a routine can never strand an interaction

---

v1.1.0 — 2026-07-26

New

• Language packs — locales/*.lua selected by Config.locale, with hu shipped fully translated
• SQL persistence — Config.persistence.backend = 'sql' moves memory, reputation, quests and bribes into oxmysql
• Graceful degrade — a missing oxmysql falls back to KVP with one console line
• nui/theme.css — open override sheet for the dialogue panel
• lastresort_levels bridge — quest completions and validated rep gains award bonus minutes; a silent no-op without it
• Drug-use and explosion perception, a witness-report TTL, a default ambient voice and concurrent backup units
• New exports — IntelPolice_HasWaitingPed(), IntelPolice_OwnsDispatch(ped), PersistenceAdapter.Backend()

Changed

• Every player-facing string moved into the locale packs — a pool left in config still overrides its locale key
• The dialogue panel carries no English in its markup — the label pack rides in the NUI open payload
• Persistence flushes on state change (debounced) instead of only on the 5-minute checkpoint
• The Discord webhook convar is read first, config second
• shared/config.lua is English throughout — napszak_bounds → time_of_day_bounds, both old names still honoured
• Zero permanent per-frame threads, and 13 whole-pool ped/object walks became spatial queries
• police_ped_hit.protect_nearby_peds ships disabled and restores every max-health value it borrows
• NUI focus is arbitrated across the suite on the lrNuiOwner state key
• lastresort_npc_chat is stopped automatically at boot in either start order

Fixed

• Surrender, the one-press apology, dispatch suppression and IsInPoliceScene were dead code — their locals were declared below their first read
• Peacefully resolved 911 scenes leaked two cops and a cruiser, and the response-patrol handler was a no-op
• Quick-talk aiming read an async shape test on the frame it started
• Explosions were bound to a game event that never reaches Lua
• Entity ownership is acquired before tasking or deleting a networked ped
• Rob, mug and pickpocket payouts are validated against the real ped by network id and burned with a replicated state
• 3D text is clamped to the engine's 99-byte limit and glyph-mapped
• Personas with no gta_voice_name are audible, a witness can report more than once, and Pete's "off the record" topic is gated correctly

Removed

• Every external network request from the NUI — the Font Awesome link and the iconify runtime, replaced by a vendored Lucide font
• The per-frame head-IK thread during dialogue
• The unused "WIP" notify placeholder and Erika's inert gated demo interaction

---

v0.53.0 — 2026-07-23

Changed

• Production defaults restored — Config.debug and Config.verbose_server_log ship as false
• *The F7 dev menu, /intel_dev and every `/intel_test command** are off on a default install;setr lastresort_intel_npc:debug 1` turns them on
• The debug convar override runs on both runtimes, so server gates and client tooling always agree
• /intel_gangtest goes through the shared dev-command wrapper like every other test command
• NUI focus is released unconditionally on stop, so the cursor can never stay stuck

Fixed

• setr lastresort_intel_npc:verbose_server_log was documented but never read

---

v0.52.0 — 2026-07-23

New

• Framework bridges — Qbox, qb-core, ESX Legacy and standalone, auto-detected for framework, inventory, notify and target
• Built-in target fallback — look at an NPC and press E, with no target resource running
• Standalone mode — in-memory session ledger, item flows that succeed without a backend, license-keyed persistence
• News and street context — data/news.lua feeds small talk, and rumour-mill gossip carries hop-decayed confidence
• lastresort_notify integration — mood toasts, conversation card, provoke meter, trust bars, wanted stars, dispatch cards, minigames
• Facial expressions — archetype and persona baselines, session-mood faces, panicked and hostile overrides, ambient sweep
• Cast-aware witness reactions — gang backup, gang witnesses mocking civilians, cops warning or drawing, civilians fleeing
• Composure system — one 0–100 nervousness score per NPC, feeding dialogue, refusals and the point where they stop talking
• Zone density manager — per-zone ambient multipliers shaping the engine's own population, with scenario blocking around personas
• Discord webhook logging — batched, rate-limit-aware embeds with per-category webhooks and per-event toggles
• Server-side persistence — KVP snapshots of memory, reputation, quests and bribes, restored on join
• Police additions — sight-aware cop placement with fade-in, a wanted-level watcher, roaming cruise patrols
• More police controls — a configurable star ceiling, per-archetype car-hit reactions, a flee-the-scene warning phase, the one-press apology (B)
• Static persona roster grown from 1 to 10 — Maggie, Erika, Pete, Joe, Tony, Doc, Denny, Anna, Sergeant Mahoney, Candy
• Quality of life — quick-talk hotkey (G), NUI auto-scaling, dialogue drift grace, idle gossip, mood carry-over, ops metrics, vehicle NPC helpers

Changed

• Renamed lrr_intel_npc → lastresort_intel_npc — exports, event prefix, callbacks, convars, KVP keys and keybinds all moved with it
• Author → LastResort Development (intelnpc.com)
• Hard dependencies reduced to ox_lib only — qbx_core, ox_target and ox_inventory are optional bridges now
• Ambient spawning delegated to the game population — the resource only spawns static personas and set-pieces
• The police module ships disabled with an explicit alpha warning, toggleable live without a restart
• Persona shops default to a built-in server-validated menu — the ox_inventory shop UI is opt-in
• Config surface reorganized — use_ox_target → target_enabled + bridge.target, and friends; the wanted cap is configurable
• Reputation tuning — threaten −3, provoke −2, a new topic nudges +1 with an anti-farm guard, polite closes cap at Familiar

Removed

• The dynamic persona pool — the script-side crowd of random NPCs is replaced by the game's own population
• Hard dependencies on qbx_core, ox_target and ox_inventory
• The separate lrr_wanted requirement — its triggers are hosted in the police module; the relay events remain

---

v0.38 — Initial Tebex release (as lrr_intel_npc)

• Every NPC is a person — categories, archetypes, session moods, per-NPC memory including witnessed crimes
• Recursive dialogue trees in a chat-style NUI — typewriter lines, mood badge, live trust meter, conditional responses
• Six ambient categories routed by ped model — Civilian, Gang, Cop, Homeless, Prostitute, Default, each with its own refusal rate
• Seven personality archetypes — coward, compliant, brave, aggressive, cunning, stoic, cop — with tunable patience, thresholds and bribe prices
• Reputation on a −10..+10 scale across six tiers, moved by actions rather than chatter
• Social intelligence layer — witness reliability tiers, disguise scoring, NPC-to-NPC gossip with per-hop decay, alibi windows, trauma, informant leaks, bribes
• Police system (alpha) — car-hit reactions, the pre-call talk-down window, the bystander witness mechanic, a calmly responding RP unit, a seven-choice cop scene
• Police triggers — red-light and speeding detectors, cruise patrols, star-scaled bribes, server-validated cash flows
• Operator-first — ~1,300 lines of commented config, master toggles for every module, a dev menu and dev command suite
• Integration surface — client exports, public server events and validated server callbacks
• Full source, no obfuscation

Download an older version

1. v1.63.0LatestSeptember 24, 2026

   New — AI conversations through the optional lastresort_intel_npc_ai add-on

   This resource still contacts no external service. When the separate add-on is running and has its owner's API key, the conversation panel becomes free talk and the add-on's model directs the NPC; without it nothing changes.

   • Free-typed replies. A text field above the replies; any letter key starts typing, ENTER sends. AI reply suggestions sit on 1–3 with a suggested tag, the scripted topics stay under them (Config.ai_bridge.keep_scripted_topics). A FREE TALK chip in the header, a teal typing cue while the NPC thinks, the NPC's name in the header once a random pedestrian introduces themselves
   • The NPC acts on the model's call: emotion to GTA facial idles and the mood badge, the delivery to a GTA speech context through the speech-synced panel (new tone ai_goodbye → GENERIC_BYE), a gesture as a secondary upper-body animation, and the closing reaction — ends it, walks away cursing, curses, flips you off, flees, hands up, begs, calls the cops, attacks, draws, arrest warning — through the existing reaction set, with the NPC marked panicked or hostile before the dialogue hold is released so the reaction is not cleared

   Full notes in the changelog

2. v1.62.1September 5, 2026

   Fixed — your saved standing is no longer announced as a fresh loss

   Spawning in threw a trust toast at you for every persona you had a stored reputation with — "Maggie · Trust down (−10)" for something that happened days ago, and a screen-centre rank overlay for a saved positive. Nothing had changed; the restore was reporting itself.

   • A restore is not a change. client:persistRestore pushed every saved row through Reputation_Set, which sees the fresh table at 0, calls that a move and fires IntelFx_OnRepChange. The saved set now replaces the table through Reputation_Restore instead: same numbers, same clamp to −10..+10, no toast and no overlay. A move made in the session still announces itself exactly as before, and the panel's trust bar is untouched
   • Legacy ambient_<uid> rows are dropped by the restore itself. They were handed to Reputation_Set, which refuses an ambient key — so the prune pass that ran afterwards always found nothing to drop and reported nothing, while the refusal printed a yellow console warning on every single load. The rows are now counted and dropped where they arrive, and the line in the console says how many
   • tests/reputation.test.lua — first harness for this module: boots client/reputation.lua and client/persistence.lua against a stubbed engine

   Full notes in the changelog