[Bug] AddConvarChangeListener does not fire when a convar is created (first set)

[lilabyte]

Summary

A convar change listener (including a wildcard one) is never invoked for the SET that creates a convar. Only subsequent sets fire it. From the listener's perspective the transition from nonexistent to a value is the most significant change a convar can make, and a wildcard subscriber has no other way to learn about new convars. This silently breaks any config system that reacts to convars: an operator typing the first set my:config:flag true at the live console sees no effect, while the identical command typed a second time works. Nothing in the convar documentation describes this behaviour.

Issue type

Both / Unsure

Repro rate

Always

Server build version

FXServer-early-access b168 linux

OS

Windows 11 Pro 10.0.26200

CPU

13th Gen Intel(R) Core(TM) i5-13600KF

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

Linux

OS version / distribution

Debian 13

CPU

No response

RAM

No response

Using txAdmin?

Yes

Hosting provider

Self-hosted

Machine type

VPS

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

Repro resource (JS, no dependencies):

fxmanifest.lua

fx_version 'cerulean'
games { 'gta5' }
server_script 'server.js'

server.js

AddConvarChangeListener('*', (name) => {
  console.log(`[repro][wildcard] convar changed: ${name} = "${GetConvar(name, '<unset>')}"`);
});

AddConvarChangeListener('repro_creation', (name) => {
  console.log(`[repro][exact] convar changed: ${name} = "${GetConvar(name, '<unset>')}"`);
});

RegisterCommand('repro_get', (_source, args) => {
  console.log(`[repro][server] ${args[0]} = "${GetConvar(args[0], '<unset>')}"`);
}, false);

Steps (server console, nothing else needed):

1. ensure the resource.
2. set repro_creation a - NOTHING is logged by either listener (bug). The convar did get created: repro_get repro_creation prints repro_creation = "a".
3. set repro_creation b - BOTH listeners log the change: [repro][wildcard] convar changed: repro_creation = "b" and [repro][exact] convar changed: repro_creation = "b".
4. set repro_creation b again (same value) - nothing is logged, so the listener clearly fires on value changes. The creation in step 2 was a value change too (nonexistent to "a") and still produced nothing.
5. Same result with a replicated convar: setr repro_creation2 a is silent, setr repro_creation2 b logs.

Expected Behavior

Step 2 should invoke the listener: the convar's value changed from nonexistent to "a", and a wildcard listener in particular is the only mechanism a script has for discovering newly created convars.

Actual Behavior

The creating set is silent and only the second and later sets fire the listener. Scripts that cache convar-driven config and refresh it from the change listener permanently miss the first value unless the convar was declared in server.cfg before they started.

Evidence

No response

Additional Context

No response

[lilabyte]

May be related: #587

[Gogsi]

Hello,
A fix for this issue has been implemented in November 11 patch for FiveM for GTAV Enhanced. Please try again and let us know if the issue persists. Thanks for your help!