maybegreat48

unk_0x195 is the base64 encoded version of the current `rlSessionInfo` aka "gsinfo" unk_0x218 is most likely matchmaking group

> Idk why my implementation of this doesn't work -> [commit](https://github.com/cristyanul/YimMenu/commit/6637c21c10251f03ed7e492b892392200efe995b) You have to call the original first then modify the node later, changes will not be visible locally so...

I will help where I can. FiveM has probably covered the most important stuff though

unk_0x230 is a "account id" might be another RID leak (not tested)

> I have updated the class with the debug names of the variables from here: [Pastebin of NodeCommonDataOperation classes from an Xbox dump](https://pastebin.com/raw/iaehSAws) > > > ... Ah now I...

Now that I think about it, how do the admins ban you anyway? The game is P2P and you can spoof your name, SCID, can use a VPN to hide...

Yes I realized a while back that hooking send_net_info_to_lobby alone won't hide RID. Basically every script event, netevent, packet that sends a `rage::rlGamerHandle` is leaking your actual RID. There are...

You can try hooking `48 8B C4 48 89 58 08 48 89 70 10 48 89 78 18 4C 89 70 20 55 48 8B EC 48 83 EC...

See https://github.com/citizenfx/fivem/blob/92cbb7abb99312b114c532475455a6526241481f/code/components/citizen-server-impl/src/state/ServerGameState.cpp#L4138 Example: ```c++ bool scan_explosion_event(rage::datBitBuffer* buffer) { uint16_t f186; uint16_t f208; int ownerNetId; uint16_t f214; ExplosionTypes explosionType; float damageScale; float posX; float posY; float posZ; bool f242; uint16_t f104;...

This seems to work, and does not break anything so far: ```c++ static inline script_global gpbd_fm_3(1893551); *globals::gpbd_fm_3.at(self::id, 599).at(1).as() |= (1