271
edits
Talk:AI: Difference between revisions
Response for Iritscen
(I don't really know, just a guess) |
(Response for Iritscen) |
||
| Line 31: | Line 31: | ||
---- | ---- | ||
Thanks for all your work, Loser. "'''Minimal shooting distance (MinShootingDistance) - [..] for some unknown reason, value from this field is divided by 2.'''" Could it be that the engine considers this setting to be a diameter and not a radius? The AI would be at the center of a circle of diameter MinShootingDistance, so it would take effect if an enemy gets less than 0.5*MinShootingDistance in any direction from them. Of course, if the other "distance" variables don't work that way, then this could still count as a bug, I suppose. --[[User:Iritscen|Iritscen]] 21:51, 25 September 2011 (CEST) | Thanks for all your work, Loser. "'''Minimal shooting distance (MinShootingDistance) - [..] for some unknown reason, value from this field is divided by 2.'''" Could it be that the engine considers this setting to be a diameter and not a radius? The AI would be at the center of a circle of diameter MinShootingDistance, so it would take effect if an enemy gets less than 0.5*MinShootingDistance in any direction from them. Of course, if the other "distance" variables don't work that way, then this could still count as a bug, I suppose. --[[User:Iritscen|Iritscen]] 21:51, 25 September 2011 (CEST) | ||
:All other fields related to distances (be it in ONCC, CMBT, MELE, EINO, other values in ONWC and so on) use radius as a value. So my assumption is that Minimal shooting distance field is somehow bugged when processed and is taken as a diameter.--[[User:Loser|Loser]] 17:21, 28 September 2011 (CEST) | |||