#75 : New crash when attacking a Green Dragon that used (Wait+)Defend in the previous round. I discovered this while playing the same battle which was subject to bugs #71 & 72. I don’t know if it’s related to #72, as behavior is quite different (no Angel freezing, or failed attack leading to the disappearance of the mouse cursor).
Here are the steps that led to it:
- Load game 2009-Jul-11-171057 (in the attachment below)
- Attack Angels with Sephinroth, Angels make the first move coming closer
- Lightning Bolt on Angels, Green Dragons Wait
- Double shoot with Grand Elves, who got morale and could double shoot again
- Shoot with Beholders, Harpies Wait, Attack with Dwarves from behind (Angels retaliate)
- Attack with Troglodytes, then with Harpies and Green Dragons
- Round 2: Angels attack Grand Elves (unless Elves got the morale extra shot previous round, Angels kill all Elves now)
- Lighting Bolt on Angels, Green Dragons Wait, Shoot with Beholders, Harpies Wait
- Attack with Dwarves (Angels retaliate), then with Troglodytes & Harpies
- Green Dragons defend (ending round 2)
- Round 3: If you’re lucky, Angels attack Green Dragons now, causing the crash
Of course, it may not always happen that Angels attack Green Dragons in round 3, especially if they manage to kill all Grand Elves in round 2, so you may need to replay the battle a few times, always applying Defend on Green Dragons at the end of each round starting with round 2. But if AI decides to strike the Green Dragons in this situation, then the crash is always reproducible (3 out of 3 attempts on my side) - see screenshot & attached logs.
i4.photobucket.com/albums/y104/Zamolxis/VCMI/VCMI%2007/th_090712-CrashwhenAngelsattackedDrago.jpg
EDIT: Probably an important note - It seems the bug is pretty much related to the Dragons. I tried Wait+Defend on Grand Elves in round 1, but the game didn’t crash when Angels attacked them in the round 2. That, while for Green Dragons is always reproducible as I said. On the other hand, I hope that’s not misleading information - maybe it’s not related to Dragons per se, but to attacking a 2-hex defending creature,… or something else. If you don’t manage to identify the cause, I’ll try to reproduce it in the future with other creature types (other 2-hex, other dragon types, etc).
#76 : And a small detail (not even sure if it’s a bug or meant as a feature), regarding the mini status window, the lower right box in the game interface, with brief information about the selected hero or updates (new day; size of resource picked; etc). In H3, in the beginning of a new day/week/month, we have a short specific animation. When the animation ends, the content of the box changes to info about the 1st hero (selected) in the hero list. In VCMI, the box remains frozen on the last frame of the new day animation. Moreover, even if we select another hero in the list during the Autosave, the box will still remain frozen on that last frame of the animation (see screenshot below, I selected Sephinroth during Autosave, and the info box did not change). Only after Autosave is completed, we can click on one of the heroes to have the box content changing.
i4.photobucket.com/albums/y104/Zamolxis/VCMI/VCMI%2007/th_090712-Statuswindownotchangedalsoif.jpg
Now, I don’t really mind that the box does not change immediately at the end of the new day animation (I always felt it was kind of short in H3). But I would expect that it changes at least at the end of the Autosave process, and/or at least when I click on another hero in the list, even if the game is still Autosaving. But again - this is just a detail, a small difference from H3 - I don’t think anybody would mind if it’s not fixed.
090712 - Crash when Angels attacked Dragons which Defended previous round.zip (104 KB)