d22tny

Hi. From my knowledge there is not a 99 limit. You're dealing with either native misuse / race conditions on natives. I'll test right now and come back with some...

Yup, exactly. More than 99 unique blips names ( everything is fine ) :  More than 99 entries for the same named blips ( still everything fine ) ...

> With [this PR](https://github.com/citizenfx/fivem/pull/3223) merged, you should be able to have 133 named blip categories and then 120 more unnamed ones. > > Keep in mind that as of writing...

If i remember correctly, the issue happens because this gets called a lot on the same ticks. ``` BeginTextCommandSetBlipName("STRING") blipName = blipName or string.format("My Custom Blip %d", blipId) AddTextComponentString(blipName) EndTextCommandSetBlipName(blip)...

No, it's not. In the same logic, adding Wait in a coroutine would be absurd. It is normal to give time for the code to run. And loading the blips...

with a setter for _GET_CURRENT_RADIO_TRACK_PLAYBACK_TIME you can do it with a script. you can get and set the radio, track, and i saw some undocumented natives for tuning forward, so...

Really great job! Nice one. ``` constexpr bool canLengthHack = #ifdef STATE_RDR3 true #else true #endif ``` i think you should remove the ifdef entirely here

Does it happen on Canary ?

Yeah, ok. https://github.com/citizenfx/fivem/issues/3213 It's a duplicate of this.

https://github.com/citizenfx/fivem/blob/91bd18e26c425d8316e98f0f7abbc7630b54e092/code/components/gta-streaming-five/src/ModKitIdRelocation.cpp#L56 about carcols