Medina/VersionHistory

When a fire event occurs, examine carefully which enemy could be the target (possibly a probability distribution estimation).
When a hit event occurs, examine carefully which enemy could be the target using the previous calculated probabilities.
Handle bullet-hit-bullet event.

Tweak MEA and bandwidth?
Improve fire-and-hit detection and use enemy interpolation everywhere (apply hard OOP here).

???
- First release.
- Very simple fire-and-hit detection, a lot of room to improve.
- Wave hit during danger evaluation is very stupid, waves are single-tick, often off-by-many-ticks and there is no accurate bot-wave intersection.
- Quickly tested, brand new and hand-weighted minimum risk + true melee surfing, which is for now used in 1v1 as well.
- It's not too optimized, it's a bit slow for now, and probably memory hungry. The only optimizations are stats caching and discarding irrelevant logs (like from an enemy which is too far from me for its data to change anything in my decisions).
- Surfing views are really simple, accel + velocity + distance for now.
- Minimum risk component is based on Monk's, but simpler: perpendicularity, distance and being one of the closest to an enemy are taken into account.
- Initial movement is too simple, it's getting constantly cornered (unfortunately, during the game as well, but this is a harder issue).
- Using traditional MEA everywhere, maybe since the movement in melee is really restricted, this can be improved.
- Enemy logs interpolation only when detecting a hit (not when firing, causing a lot of off-by-many-ticks waves).
- Bullet-hit-bullet events are not used.
- Every time an enemy gets hit, it's inferred it surely was the target.
- Every scan is inversed by distance because it's the most obvious way I can think to weight the chance of each enemy to be a target.
- Guns from Monk.

Navigation menu