MantisBT - VCMI
View Issue Details
0000833VCMIMechanics - Battlespublic2011-10-29 00:312014-05-30 17:40
Zamolxis 
Warmonger 
normalmajoralways
closedfixed 
0.86c 
0.87 
0000833: Can't attack enemy if it stops over the corpse of a friendly creature (could also be related to spell casting before)
This is new since 0.86c (always reproducible now, never in 0.86).

I'm actually not sure of the cause of this bug, but my best bet is the fact that the enemy stays on top of a friendly corpse. But it could be more particular (like only applying to 2-hex creatures, the killed Nomad, or even the Death Ripple before). I hope the below steps are enough for you to figure this out, else let me know and I'll try to create more tests to narrow this down.
- Take the map from 0000707, attack Sorsha (Orange) with Sir Mullich and cast Death Ripple
- Then attack remaining Phoenix with your Phoenix (or just use Wait on your Phoenix)
- Then enemy Phoenix will fly over Nomand's corpse and attack your Ballista
- From this moment on, you can't attack the enemy Phoenix anymore with any creature or Ballista. The cursor shows as if you can move on its hexes (though you can't), but it doesn't turn into a sword and does not attack if you click
- The Phoenix can still be killed with spells, but if you don't have enough spell points left, you're pretty much stuck, at least until the Phoenix decides to go for another target, moving away from above the Nomad.
No tags attached.
jpg 2011-10-29_CantAttackPhoenixAfterDeathRipple&PhoenixDuel.jpg (245,946) 2011-10-29 00:31
https://bugs.vcmi.eu/file_download.php?file_id=822&type=bug
jpg
Issue History
2011-10-29 00:31ZamolxisNew Issue
2011-10-29 00:31ZamolxisStatusnew => assigned
2011-10-29 00:31ZamolxisAssigned To => Tow dragon
2011-10-29 00:31ZamolxisFile Added: 2011-10-29_CantAttackPhoenixAfterDeathRipple&PhoenixDuel.jpg
2011-10-29 00:31ZamolxisIssue generated from: 0000831
2011-10-29 06:03WarmongerAssigned ToTow dragon => Warmonger
2011-11-06 17:40WarmongerNote Added: 0002131
2011-11-06 17:40WarmongerStatusassigned => resolved
2011-11-06 17:40WarmongerFixed in Version => 0.89
2011-11-06 17:40WarmongerResolutionopen => fixed
2014-05-30 17:40beegeeStatusresolved => closed

Notes
(0002131)
Warmonger   
2011-11-06 17:40   
Fixed in r2463.

The issue was caused by game finding dead stack first. Now it will prioritize alive stacks over dead ones.