View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004032 | Spring engine | General | public | 2013-10-07 02:43 | 2013-10-07 15:31 |
| Reporter | PepeAmpere | Assigned To | Kloot | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 94.1.1+git | ||||
| Summary | 0004032: when modrules:unitMethod=0 and enemy reclaim eneabled, you can disable enemy unit just with recalim touch | ||||
| Description | modrules:unitMethod=0 has different behavior then modrules:unitMethod=4 for example. The difference is not just in steps/linear reclaim, but modrules:unitMethod=0 disable unit. Is it planned behavior? | ||||
| Steps To Reproduce | Set modrules:unitMethod=0 and try to attack some unit with reclaim ability, which try to reclaim attack unit | ||||
| Tags | No tags attached. | ||||
| Checked infolog.txt for Errors | |||||
|
|
This is intentional. Please nobody change anything, it currently works. unitMethod=0 turns the reclaimed unit into a nanoframe. Clearly this should disable anything which is touched. |
|
|
Are you saying the actual behaviour is different to what the wiki says? The behaviour of unitMethod=n is *supposed* to be different for all n. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-10-07 02:43 | PepeAmpere | New Issue | |
| 2013-10-07 10:39 | Google_Frog | Note Added: 0011710 | |
| 2013-10-07 11:46 | silentwings | Note Added: 0011711 | |
| 2013-10-07 15:31 | Kloot | Status | new => closed |
| 2013-10-07 15:31 | Kloot | Assigned To | => Kloot |
| 2013-10-07 15:31 | Kloot | Resolution | open => no change required |
