271
edits
OBD talk:AKVA/0x24: Difference between revisions
Sorry for double save. Misclick ^_^'
No edit summary |
(Sorry for double save. Misclick ^_^') |
||
| Line 88: | Line 88: | ||
---- | ---- | ||
THESE are some observations made with pathfinding grid | THESE are some observations made with pathfinding grid for others to see, because adjusting of some BNVs is IMO neccessary part of modding levels and this info can help. Some statements may be wrong, so please correct mistakes if you find any. | ||
:'''RED tiles (impassable):''' | :'''RED tiles (impassable):''' | ||
:* ignored when AI2 is in MELE mode (AI2 character will chase you into "red field", that is some larger area filled with red tiles, if it is close enough to you to be in MELE mode) | :* are ignored when AI2 is in MELE mode (AI2 character will chase you into "red field", that is some larger area filled with red tiles, if it is close enough to you to be in MELE mode). That is why sometimes happen that you are close behind wall and AI2 character desperately runs towards wall on the other side - red tiles, indicating some obstacle, are ignored as AI2 char is in MELE mode. | ||
:* leave AI2 ability to fully run its MELE profile if you are close enough | :* leave AI2 ability to fully run its MELE profile if it is in "red field" and you are close enough | ||
:* block pathfinding completely (if you trap AI2 character somewhere in "red field" and you "teleport" away, it gets stuck and won't be able to chase you unless you come close enough to make it run some MELE move so it can move). This applies on both ''pathfinding'' (chasing enemy thanks to the flags) and ''vector-forced movement'' (so AI2 character can't dodge firing spreads if it is inside "red field") | :* block pathfinding completely (if you trap AI2 character somewhere in "red field" and you "teleport" away, it gets stuck and won't be able to chase you unless you come close enough to make it run some MELE move so it can move). This applies on both ''pathfinding'' (chasing enemy thanks to the dynamic flags) and ''vector-forced movement'' (so AI2 character can't dodge firing spreads if it is inside "red field") | ||
:* if AI2 is not inside, then impassable tiles | :* if AI2 is not inside "red field" and you are not close enough (so AI2 is in ''pathfinding'' or ''patrol'' mode), then red (impassable) tiles work as a wall for AI2 chars. Where are red tiles there AI2 NEVER runs (again, never if you are NOT TOO CLOSE) and it tries to find its way around it if these red tiles are in the way. If no other way is possible, then AI2 simply stops right before the red line. That is what makes AI2 characters stop near wall (and stare into it until gunfire stops) when they are dodging projectile ranges/firing spreads. They want to go this direction but there is wall. Because pathfinding mode is not active when AI2 chars are dodging gunfire, they get stuck near wall as red tiles are in way and calculated vector of movement still points towards wall. | ||
:* BUT if angle between vector of movement (for gunfire dodging) and these red tiles is small, AI2 can "slide along" the line of red tiles. I don't know how big this tolerance is ^_^. | |||
ONLY a theory | |||
:* Also it looks like these red tiles are taken as "wall" when it comes to projectiles/spreads. So maybe (unconfirmed) AI2s try to run so some line of red tiles is between them and shooter. | |||
/ONLY a theory | |||
rest will be added later | |||
--[[User:Loser|Loser]] 21:41, 16 July 2008 (CEST) | |||