| 1 |
I am aware of this behavior by CAI and willing to ignore it, given that it's very minor and:
|
1 |
I am aware of this behavior by CAI and willing to ignore it, given that it's very minor and:
|
| 2 |
1) It's possible to detect the same with WeaponFired or UnitDamaged callins in native AI (either by inferring firing unit position from projectile creation point, or from direction parameter of UnitDamaged).
|
2 |
1) It's possible to detect the same with WeaponFired or UnitDamaged callins in native AI (either by inferring firing unit position from projectile creation point, or from direction parameter of UnitDamaged).
|
| 3 |
2) All units except Spectre already exhibit this behaviour where they become visible while shooting in AirLos.
|
3 |
2) All units except Spectre already exhibit this behaviour where they become visible while shooting in AirLos.
|
| 4 |
\n
|
4 |
\n
|
|
|
5 |
If it turns out that CAI does more than that, it'll have time until submission deadline to be fixed.
|
|
|
6 |
\n
|
| 5 |
Shard also technically attempts to cheat but i'm not disqualifying it because this behaviour seems to be agressively blocked by non-cheating AI's (at least when hosted on the same machine). I may disqualify it later if its maphack starts working.
|
7 |
Shard also technically attempts to cheat but i'm not disqualifying it because this behaviour seems to be agressively blocked by non-cheating AI's (at least when hosted on the same machine). I may disqualify it later if its maphack starts working.
|
| 6 |
\n
|
8 |
\n
|
| 7 |
\n
|
9 |
\n
|
Tourney players replaced with robots