Markus

seems like as of now there are no GitHub actions runners for Apple silicon, so this probably won't happen for a while it also runs fine on M1s due to...

I really like this idea tbh, great thoughts! I actually ran some numbers with the data we expose in demoinfocs-golang and it seems like it wouldn't even be the worst...

and by let's do it I mean I probably won't find time for doing much for a while but I'm always here to support :sweat_smile:

thanks for the detailed analysis @sjaanus - I think this may indeed be worth re-implementing. PRs welcome, otherwise I'll see if/when I can get to it.

I would say this is the key bit ``` float flMovementInaccuracyScale = RemapValClamped(pPlayer->GetAbsVelocity().Length2D(), fMaxSpeed * CS_PLAYER_SPEED_DUCK_MODIFIER, fMaxSpeed * 0.95f, // max out at 95% of run speed to avoid jitter...

the code you linked seems to cover all these areas I think

we can't call any source-engine code from this library. it has to be re-implemented in Go. but I think the data is all there, e.g. `m_fAccuracyPenalty := weapon.Entity.PropertyValueMust("m_fAccuracyPenalty")` etc. let...

fair enough @sjaanus :sweat_smile: - yeah most new features are pretty tricky now, the easy stuff is mostly done :disappointed: I'll see if I can get to this soon :tm:...

cheers @billfreeman44 :pray: those props from demofile might come in handy. I guess it's just really hard to know at what point all scenarios are covered :thinking: Might just start...

thanks @saul - great input!