You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It would be nice if serverside event onVehicleDamage would be the same as clientside event onClientVehicleDamage so we would have the attacker, used weapon, positions etc params on serverside as well. Scripters wouldn't need to rely on client code.
Example usage:
Imagine a gamemode where you collect some money, xp etc on your charachter but if you die you lose it.
Players don't want to lose progress so they'll do anything against that, for example disconnecting from the server when they take damage.
We built up a system where you can't disconnect in the next 15 seconds if you take damage (from players). (you can, but you will get a surprise)
Problem is that if the player is in a vehicle we can't retrieve why the vehicle got damaged. For example if the driver just collided with a wall etc. We would need to use the clientside variant of the event but relying on client code today is not efficient. Cheaters can stop client code executing and all other malicious stuff.
Is your feature request related to a problem? Please describe.
It would be nice if serverside event
onVehicleDamage
would be the same as clientside eventonClientVehicleDamage
so we would have the attacker, used weapon, positions etc params on serverside as well. Scripters wouldn't need to rely on client code.Example usage:
Imagine a gamemode where you collect some money, xp etc on your charachter but if you die you lose it.
Players don't want to lose progress so they'll do anything against that, for example disconnecting from the server when they take damage.
We built up a system where you can't disconnect in the next 15 seconds if you take damage (from players). (you can, but you will get a surprise)
Problem is that if the player is in a vehicle we can't retrieve why the vehicle got damaged. For example if the driver just collided with a wall etc. We would need to use the clientside variant of the event but relying on client code today is not efficient. Cheaters can stop client code executing and all other malicious stuff.
Describe the solution you'd like
Describe alternatives you've considered
clientside variant of the event works
Additional context
No response
Security Policy
The text was updated successfully, but these errors were encountered: