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
The ability to effectively track players firing while in vehicles takes priority over the actions of remote-controlled units. Unless we want to devise a potentially unstable way of juggling event handlers at control switch of units, this is a side effect.
OCAP2/OCAP#37
- adds remote-controlled unit detection if firer was >50m away from initial projectile position
OCAP2/OCAP#9
- adds setting for optional BIS_fnc_respawnTickets tracking, will automatically track missionNamespace + faction score counts every 30th frame
- adds system for optional custom score tracking by a set of sides, a custom counter separate from BIS_fnc_respawnTickets
- pending testing of debug drawIcon for units being recorded
OCAP2/OCAP#37
- adds remote-controlled unit detection if firer was >50m away from initial projectile position
OCAP2/OCAP#9
- adds setting for optional BIS_fnc_respawnTickets tracking, will automatically track missionNamespace + faction score counts every 30th frame
- adds system for optional custom score tracking by a set of sides, a custom counter separate from BIS_fnc_respawnTickets
- pending testing of debug drawIcon for units being recorded
remove userconfig
The source of the line is the player not the remote controlled unit
The text was updated successfully, but these errors were encountered: