[Bug] gameEventTriggered with CEventNetworkPlayerEnteredVehicle Broken

[Rikiborn]

Summary

In previous versions, gameEventTriggered actually triggered for CEventNetworkPlayerEnteredVehicle. It's not working anymore.

Issue type

Client

Repro rate

Always

Server build version

b156

OS

No response

CPU

No response

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

Windows

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

No

Hosting provider

Self-hosted

Machine type

None

/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

on("gameEventTriggered", (CEvent: string, CArgs: any[]) => {
    if (CEvent !== "CEventNetworkPlayerEnteredVehicle") {
        return;
    }

    console.log("Does this actually work?");
});

Expected Behavior

"CEventNetworkPlayerEnteredVehicle" is supposed to be triggered when a player enters a vehicle.

Actual Behavior

Nothing happens.

Evidence

No response

Additional Context

No response

[Nobelium-cfx]

It indeed got broken in the last patch. The issue is identified and the fix is ready. It will be released soon.

[Nobelium-cfx]

I dont think so. The bug was very narrow and just causing gameEventTriggered event in particular to never be sent to the scripts. Not affecting anything else.

[MrGonzy]

Hmm i see, okay then. Thought its similar issue. But okay, seems that EmitServer is having issue transmitting or invoking event on server sided

[Nobelium-cfx]

If not already - please create a new rfc report (ideally with reproduction steps) and we will try to fix it

[MrGonzy]

I have already created a new bug report. #558

[Gogsi]

Just noting the this issue is a duplicate of #552 but since this one was replied to first, I'll close the original one.

[Nobelium-cfx]

Should be fixed now

[Rikiborn]

Yeah, it is fixed. Thanks!