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
Refactor projectile tracking to use lightweight array format (#43)
- Replace hashmap with flat positional array for projectile data
- Remove JSON encoding overhead when sending to extension
- Replace non-existent :TIMESTAMP: extension calls with diag_tickTime
- Rename variable from dataHash to projectileData
This reduces per-projectile data size and eliminates unnecessary
encoding/decoding overhead for high-frequency fired events.
Array structure documented in fnc_eh_fired_client.sqf with indices 0-18.
Copy file name to clipboardExpand all lines: addons/database/fnc_eh_fired_clientBullet.sqf
+44-33Lines changed: 44 additions & 33 deletions
Original file line number
Diff line number
Diff line change
@@ -7,12 +7,18 @@ if (isNil "_projectile") exitWith {
7
7
WARNING("Projectile EHs: _projectile is nil");
8
8
};
9
9
10
+
// Projectile data array indices:
11
+
// 14: positions
12
+
// 16: hitParts
13
+
// 17: sim
14
+
// 18: isSub
15
+
10
16
// first, we need to verify simtype & whether this was a submunition or not.
11
17
// if this is NOT a deployed submunition itself but the simType of the ammo is "ShotSubmunition", then we need to skip the Deleted EH and leave the Deleted registration to the submunition itself. This will ensure we're tracking start to finish multiple actual projectiles from things like shotguns, cluster artillery, mixed-belt machineguns, etc.
0 commit comments