Loading...
  OR  Zero-K Name:    Password:   

Post edit history

Cloakbot Imp

To display differences between versions, select one or more edits in the list using checkboxes and click "diff selected"
Post edit history
Date Editor Before After
6/1/2020 8:35:29 AMLynx before revert after revert
6/1/2020 8:34:48 AMLynx before revert after revert
6/1/2020 8:33:44 AMLynx before revert after revert
6/1/2020 8:32:21 AMLynx before revert after revert
6/1/2020 8:31:43 AMLynx before revert after revert
Before After
1 I would like to propose that consideration is afforded to Cloakbot Imp behaviour. 1 I would like to propose that consideration is afforded to Cloakbot Imp behaviour.
2 \n 2 \n
3 Suppose a user gathers a selection of Imp units for the purpose of EMP'ing a large unit. Suppose they are all fairly close together. Now suppose, with all of them selected, the user issues an attack command on the large unit. What is expected from the issuance of this command is that you will see a synchronised detonation and massive EMP injection. 3 Suppose a user gathers a selection of Imp units for the purpose of EMP'ing a large unit. Suppose they are all fairly close together. Now suppose, with all of them selected, the user issues an attack command on the large unit. What is expected from the issuance of this command is that you will see a synchronised detonation and massive EMP injection.
4 \n 4 \n
5 What instead the user sees is that the first of the bunch detonates, stunning the rest of the bunch, which sit there doing nothing and die. Which is rather a disappointment. 5 What instead the user sees is that the first of the bunch detonates, stunning the rest of the bunch, which sit there doing nothing and die. Which is rather a disappointment.
6 \n 6 \n
7 How about either: 7 As an example of the poor behaviour, please see:
8 \n
9 http://zero-k.info/Battles/Detail/902031
10 \n
11 I created about half a dozen Imps, with the expectation rightly or wrongly that this would be enough to stun a detriment. I had a bunch selected and managed to sneak up to the otherwise occupied detriment under cover of a bombardment of all manner of units form my team mates. I believe I got a clump very close to the detriment and that I issued an attack command with said clump selected. Rather than massive injection of EMP, one Imp detonates stunning the rest, which was rather disappointing.
12 \n
13 So that is the problem. For the solution, how about either:
8 \n 14 \n
9 1) EMP stun of Imp effects detonation; or 15 1) EMP stun of Imp effects detonation; or
10 \n 16 \n
11 2) Imps within proximity of each other that have attack order active will give rise to synchronised detonation? I suppose this could be achieved by enabling 1) with live attack order. 17 2) Imps within proximity of each other that have attack order active will give rise to synchronised detonation? I suppose this could be achieved by enabling 1) with live attack order.
12 \n 18 \n
13 As an example of the poor behaviour, please see:
14 \n 19 \n
15 http://zero-k.info/Battles/Detail/902031
16 \n
17 I created about half a dozen Imps, with the expectation rightly or wrongly that this would be enough to stun a detriment. I had a bunch selected and managed to sneak up to the otherwise occupied detriment under cover of a bombardment of all manner of units form my team mates. I believe I got a clump very close to the detriment and that I issued an attack command with said clump selected. Rather than massive injection of EMP, one Imp detonates stunning the rest, which was rather disappointing.