Home
last modified time | relevance | path

Searched refs:could_hit (Results 1 – 8 of 8) sorted by relevance

/dports/games/xconq/xconq-7.5.0-0pre.0.20050612/kernel/
H A Dconq.h418 extern int could_hit(int u, int u2);
H A Dcombat.c293 could_hit(int u, int u2) in could_hit() function
3090 && (could_hit(unit2->type, unit->type) in mobile_enemy_threat()
H A Dplan.c1634 if (!could_hit(u1, u2) && !(victimflags & VICTIM_ENCOUNTERABLE))
2061 && could_hit(tmpunit->type, u2)
/dports/games/xconq/xconq-7.5.0-0pre.0.20050612/changelogs/
H A DChangeLog-EMCDONALD_AI1547 (could_hit): Likewise.
1596 (could_hit): New function. Could u hit u2 by attacks or fire?
H A DChangeLog-1995868 (could_hit): Add test of uu_fire_hit.
H A DChangeLog-1999158 * combat.c (could_hit): New function, was macro.
159 * game.h (could_hit): Remove macro.
H A DChangeLog-2003237 * combat.c (could_hit): Add correct handling of defaulting
324 (could_hit): Check ACP to attack and fire as well as
H A DChangeLog-20047872 * kernel/combat.c (could_hit): Rewrite in terms of 'could_attack'