David Durst

See https://github.com/phanrahan/magma/issues/351 for the matching magma issue.

Duplicate id's happen quite frequently (seems like 5-10% of grenades). In the [old version of my parser](https://github.com/David-Durst/csknow/blob/5d3906bbb232a09a2bbcff30d8f4c7f5d549f654/demo_parser/parse.go#L484-L675), I kept a list of duplicate ids and assumed that grenades exploded in...

Here's another demo https://drive.google.com/file/d/1ajifwQNd0BPPg9CXl038NfNrjrOmwTr4/view?usp=sharing. It's much newer (so no demo file structure issues), but it has the same problem. In particular, see IngameTick 35082. Niko's first flash explodes just after...

I'm not seeing it on the same tick. I'm filtering out those duplicate events on same tick and still seeing the duplciate id issue. The flashbang thing makes sense. I've...

Which demo are you using?

Is there a way to make uniqueid actually unique? like create a new one for each "flashbang bullet"?

The goal is to record the ticks when a grenade is thrown, destroyed, it's effect is active, and it's effect expires. I also want to link the grenade to it's...

There certainly are other approaches (like matching the trajectory starting points of the grenades), but the cleanest for me would be using `Grenade.UniqueId()`, so hoping there's a solution using that.

Understood, thanks for your help! Previously, I solved this by assuming that flashes had a constant fuse length. This enabled me to deduplciate the ids by assuming explosion order =...

https://davidbdurst.com/blog/csknow_flashbang_length.html fuse length is constant. I'll use this hack if nothing better comes up.