View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0004916 | Spring engine | General | public | 2015-07-26 20:39 | 2015-07-26 20:39 | ||||||||
Reporter | lhog | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | Severity | feature | Reproducibility | always | ||||||||
Status | new | Resolution | open | ||||||||||
Product Version | 100.0 | ||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0004916: CMD.FIGHT implementation is too rigid | ||||||||||||
Description | Engine implementation of CMD.FIGHT is rigid. The current implementation is so, that CMD.FIGHT issues CMD.ATTACK command to the euclidean nearest unit, that formally qualifies as target. Obviosly that target could be not the best or completely not appropriate at some stage of the game. Issues are: 1) No targetting priorities are queried during the selection 2) It's impossible to invalidate that target from unitscript or gadget Proper implementation of CMD.FIGHT (for fighting domain) should 1) select target according to a priority returned by AllowWeaponTarget 2) also it should be possible to invalidate the current target, so re-targeting (according to priorities) is done. | ||||||||||||
Tags | No tags attached. | ||||||||||||
Checked infolog.txt for Errors | |||||||||||||
Attached Files |
|
![]() |
|||
Date Modified | Username | Field | Change |
---|---|---|---|
2015-07-26 20:39 | lhog | New Issue |