Opened 8 years ago

Closed 8 years ago

#3564 closed defect (worksforme)

Siege should not attack when ordering a capture request

Reported by: elexis Owned by:
Priority: Should Have Milestone: Alpha 19
Component: UI & Simulation Keywords:
Cc: Patch:

Description

Since the introduction of capturing this has been one of the biggest issues with the capturing logic.

Reproduce:

  1. Select 20 units and 1 ram
  2. Rightclick an enemy building

Result: The building will be captured and destroyed simultaneously, yielding a heavily damaged captured building. Expected result: The building is either only captured or only attacked by the selected units, i.e. the units capture it and the ram waits in front of it.

Since the 'bug' occurs automatically, every player does it by default and one would have to explain it to the allies upon every attack.


The attack order will be:

cmd 1 {"type":"attack","entities":[501,503,505,507,509,527],"target":150,"allowCapture":true,"queued":false}

It should have another attribute "allowAttack":false.

Change History (4)

comment:1 by Lionkanzen, 8 years ago

But is haré avoid, that, so, units not should perform a capture if other units are attacking. Or capture or attack , Because the game becomes a volley or capture flag gaming or capturing tower game.

comment:2 by elexis, 8 years ago

Alternative proposal: ffm suggested that weakened buildings could be captured faster. (If you can kick in the door it will be easier for your units to takeover the building).

In that case having the mixed attack would make sense.

comment:3 by Lionkanzen, 8 years ago

But capturing houses... Is not great attractive in late game attacking the last CC.

comment:4 by leper, 8 years ago

Resolution: worksforme
Status: newclosed

See Attack.js which already does this. It could however happen that the building is destroyed before it is captured.

Note: See TracTickets for help on using tickets.