View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000525VCMIMechanics - Battlespublic2010-07-10 10:542018-01-22 16:11
Assigned ToAVS 
PlatformAMD 5600+OSWindowsOS VersionXP SP3
Product Version0.81 
Target VersionFixed in Version 
Summary0000525: Selection of Resurrection target with mutiple dead creatures on a hex
DescriptionYou can use Sir Mullich in the map attached to 0000515 and attack the Orange player and follow the below steps to reproduce:
Steps To ReproduceRound 1
- Use defend on all your troops. The enemy Phoenix will kill the Sharpshooter

Round 2
- Use defend on all your troops. The enemy Phoenix will kill the Enchanter

Round 3
- At start the enemy Phoenix will kill the Nomad
- Use Resurrection on Sharpshooter or Enchanter
- When the turn comes for Sharpshooter/Enchanter, move it in front of the Ammo Cart (just above the hexes where the the body of the Nomad is)

Round 4
- Enemy Phoenix will move above the dead Nomad, to kill your Sharphooter/Enchanter
- Attack the Phoenix with your Phoenix & Crystal Dragon. That should kill it.
- Try to cast Resurrection on the Nomad
Additional InformationNote: Probably obvious, but the fix should take care both left and right player can resurrect. I'm just thinking we should avoid that by fixing this we end up blocking the AI from resurrecting their troop in that very same hex.

There's another difference: in H3, if 2 or more of our stacks were dying in the same hex, resurrection was starting with the last one which died. In VCMI it seems it start with the first one (or else random). In the above mentioned map, I had the Enchanter killed in the same hex where Sharpshooter was killed before. Resurrection raised the Sharpshooter first.

SUGGESTION: It would be great if in case 2 or more stacks died in the same spot, Resurrection would first open a window asking us which of the dead stacks we prefer to resurrect. I think the fans would consider it a welcomed surprise feature, without having the feeling that it really affects the original gameplay. But I understand that even if you like the idea, this would require extra code plus graphics for a totally new choice window, so this should of course not prevent moving this into Resolved once the reported bug is fixed.
TagsNo-harm enhancement
Attached Files

- Relationships
related to 0001763closedAlexVinS Game crashes when attempting to resurrect 
related to 0002862assignedAVS Resurrection - it does not work if the units were killed in the same hex 

-  Notes
majaczek (reporter)
2012-03-01 09:10

Well only a code. We have multi-use choice window graphics - just the same as town portal choice popup.
Warmonger (administrator)
2014-05-17 20:12
edited on: 2014-05-17 20:13

Targeting was fixed in issue 0001763. The other remaining suggestions look more like a feature. Edited report info.

- Issue History
Date Modified Username Field Change
2010-07-10 10:54 Zamolxis New Issue
2010-07-10 10:54 Zamolxis Status new => assigned
2010-07-10 10:54 Zamolxis Assigned To => Tow dragon
2010-07-10 11:19 Zamolxis Additional Information Updated View Revisions
2010-07-10 11:20 Zamolxis Tag Attached: Suggestion
2010-07-10 11:20 Zamolxis Description Updated View Revisions
2010-08-01 13:58 Zamolxis Tag Renamed Suggestion => No-harm enhancement
2012-02-27 12:16 Warmonger Assigned To Tow dragon => Warmonger
2012-03-01 09:10 majaczek Note Added: 0002257
2014-05-17 20:07 Warmonger Relationship added related to 0001763
2014-05-17 20:11 Warmonger Assigned To Warmonger =>
2014-05-17 20:11 Warmonger Severity minor => feature
2014-05-17 20:12 Warmonger Note Added: 0004666
2014-05-17 20:12 Warmonger Status assigned => new
2014-05-17 20:13 Warmonger Note Edited: 0004666 View Revisions
2014-05-17 20:14 Warmonger Summary If an enemy stack dies in the same hex(es) where one of our stack died before, we cannot cast Resurrection on our stack anymore => Selection of Resurrection target with mutiple dead creatures on a hex
2014-05-18 19:38 AlexVinS Assigned To => AlexVinS
2014-05-18 19:38 AlexVinS Status new => assigned
2014-06-11 03:38 AVS Assigned To AlexVinS => AVS
2018-01-22 16:11 AVS Relationship added related to 0002862

Site | Forums | Wiki | Slack | GitHub

Copyright © 2000 - 2024 MantisBT Team
Hosting provided by DigitalOcean