Ticket #646 (new defect)

Opened 3 years ago

Last modified 23 months ago

Units should detect if enemies are nearby

Reported by: k776 Owned by:
Priority: Should Have Milestone: Backlog
Component: Core engine Keywords:
Cc:

Description (last modified by k776) (diff)

Current Problem

Currently, if a unit is doing something (like chopping wood, or farming), that unit doesn't detect that enemies are approaching. This means that unless the player notices the attack, the enemy can wipe out a large part of the persons units without them knowing, because the units keep working on what they were told to do.

Also, if enemies are chasing a unit, they will not attack anything that gets near them, but ignore it, and keep following the unit they want to attack, so as long as the unit keeps moving, those units end up worthless. Ideally, if they are attacked by a unit, they go and attack that unit, instead of changing a unit they can't catch up with.

A classic example of this: Enemy is attack fortress then BAM, player lets 20 units out of it to attack. Enemy doesn't fight back, but continues to fight fortress, and then dies.

Recommended Fix

If the unit is a women, that women should seek protection in the nearest building she can garrison inside. If one cannot be found, she should run back toward the town center and garrison inside that.

Discuss: If that happens (an attacked women flees to town center), should the closest idle infantry be summoned to the town center to defend it?

If the unit is an infantry unit, they should act as if they were idle. Stop what they were doing, and go and attack the enemy. What they were doing should be stored though, so that if the unit survives the attack, and no more enemies are approaching, the unit should resume what they were doing (chopping wood, farming etc).

Discuss: If the worker is killed, should nearby infantry be called to that spot?

Implementation

Attack priorities? strongest -> weakest -> buildings. So heros before normal infantry, then women, then buildings. Sound possible?

Change History

comment:1 Changed 3 years ago by k776

  • Description modified (diff)

comment:2 Changed 3 years ago by k776

  • Description modified (diff)

comment:3 Changed 2 years ago by k776

  • Milestone changed from Alpha 3 to Alpha 4

comment:4 Changed 2 years ago by k776

  • Owner Philip deleted

comment:5 Changed 2 years ago by k776

  • Priority changed from Must Have to Should Have

comment:6 Changed 2 years ago by k776

  • Milestone changed from Alpha 4 to Alpha 5

comment:7 Changed 2 years ago by k776

  • Milestone changed from Alpha 5 to Alpha 6

comment:8 Changed 2 years ago by k776

  • Milestone changed from Alpha 6 to Alpha 7

comment:9 Changed 23 months ago by k776

  • Milestone changed from Alpha 7 to Backlog
Note: See TracTickets for help on using tickets.