0000266: Crash when trying to move Troll

View Revisions: Issue #266		[ Back to Issue ]
Summary	0000266: Crash when trying to move Troll

Revision	2009-12-01 00:15 by Zamolxis
Description	VCMI crashed whey I tried to move a Troll in battle. It could be though that the crash has nothing to do with the Troll, but perhaps be caused by a combination of two known bugs: - VCMI already calculating the next AI moves (an losses) before our creature moves - Crash in killing last enemy creature in retaliation My Troll was the last creature to move in the turn. After his move, the enemy had just one (weak) stack, which probably would have been killed in retaliation. But as I've noticed VCMI tends to already calculate AI's next move even for the 2nd round (while the last creature of round 1 still has to move), I suspect that may be the cause of the bug.

Revision	2009-12-01 00:24 by Zamolxis
Description	VCMI crashed whey I tried to move a Troll in battle. It could be though that the crash has nothing to do with the Troll, but perhaps be caused by a combination of two known bugs: - VCMI already calculating the next AI moves (an losses) before our creature moves - Crash in killing last enemy creature in retaliation My Troll was the last creature to move in the turn. After his move, it was the turn of enemy's last remaining stack, which probably would have been killed in retaliation. And as I've noticed VCMI tends to already calculate AI's next move (even for the 2nd round while the last creature of round 1 still has to move - not the case here though), I suspect that may be the cause of the crash.

Revision	2010-07-13 10:52 by Zamolxis
Description	VCMI crashed whey I tried to move a Troll in battle. It could be though that the crash has nothing to do with the Troll, but perhaps be caused by a combination of two known bugs: - VCMI already calculating the next AI moves (an losses) before our creature moves - Crash in killing last enemy creature in retaliation My Troll was the last creature to move in the turn. After his move, it was the turn of enemy's last remaining stack, which probably would have been killed in retaliation. And as I've noticed VCMI tends to already calculate AI's next move (even for the 2nd round while the last creature of round 1 still has to move - not the case here though), I suspect that may be the cause of the crash.

Site | Forums | Wiki | Slack | GitHub