Thread history

Fragment of a discussion from User talk:Xor/Thoughts on movement
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
No results

Isn't DiveProtection and BotWidth calculation a type of risk source.

Dsekercioglu (talk)19:18, 8 September 2017

DiveProtection is a technique to avoid low distance ;) Therefore covered by Distance;) BotWidthCalculation is covered by PreciseIntersection ;)

Xor (talk)01:09, 9 September 2017

Sorry for really bad english. What I mean by Bot width calculation is the bins that are covered by the robot. For Dive Protection you are right.

Dsekercioglu (talk)14:40, 9 September 2017

isn't bins covered by robot already done by PreciseIntersection? I think most bots will base that on BotWidth.

Xor (talk)15:58, 9 September 2017

As I know Precise Intersection is about when the wave will it since it is intersection but I may be wrong.

Dsekercioglu (talk)16:01, 9 September 2017

PreciseIntersection is basically SuperBotWidth ;) The real bot width of hit instead of imaginary ;)

Xor (talk)16:03, 9 September 2017
 

Yep, the complete width of your (moving) bot while the wave iterates over your bot. So it can be close to 60 pixels for a bot on full speed and a full power bullet. (Botwidth 36 + 3 ticks of 8 wide). How you record it is up to you, bins or angles. Next to that, getting closer to an enemy makes your botwidth relatively larger compared to the Maximum Escape Angle you have.

GrubbmGait (talk)17:02, 9 September 2017