Client (production/canary) and FXServer version:
Production & Canary. Any FXServer
What you expected to happen:
The native should return valid X, Y, Z values (as it has already returning before)
What actually happens:
Recently, when you use this native, you can receive a vector3 with a valid X value, but with Y & Z positions being zero. Seems like this depends in which values you are using in the offset (see below in the reproducible steps)
Category of bug (eg. client, server, weapons, peds, native):
Client/Native
Reproducible steps, preferably with example script(s)
This reminds me of another report a while ago that a) wasn’t even reproducible and b) was even closed as ‘oh yeah doesn’t happen’ by the author… but I also can’t find that report at all, either.
In this case, however, I have a theory as to what happened - mitigation for this abusive code execution/memory reading ‘anticheat’ thing that likely ended up clearing 2nd/3rd result fields if the first one was marked as ‘equal’. The annoying part here is that we don’t have any reproduction code for the exploit itself at all, so it would be difficult to even find out if, say, a special case of this for result-as-vector cases doesn’t somehow reintroduce the issue for any other case.
Seems like there’s another way to still achieve the same inconsistency, but now using vector3 instead of numbers as parameters (results in X being zero):
