Wednesday, February 9, 2011

Mount Upgrade Bug

There's a bug in mount upgrade. When a mount is upgraded while it is equipped on a hero, the hero will be "damaged" and have a lower troop speed. This sorts of offset the upgraded mount. The mount however, is not affected, it continues to improve.

So until hithere fixes the bug, please do the following :
1. Unequip the mount
2. Upgrade the mount
3. Re-equip the mount

That way, your hero will not be "damaged".

How do you determine if a hero is "damaged"? I'll refer to this post by crumpet that contains the image of a damaged hero.
http://forum.hithere.com/viewthread.php?tid=44293&page=8#pid2513967

In that post, you can see that the hero is trooped with Inf-6. The base speed of Inf-6 is 40, and therefore the speed should never be lower than 40. But the image shows that the speed is 37. That means the hero is damaged by the bug.

Remember, if a hero has never visited your main since they introduced Training Center, that hero cannot be damaged. The easiest way to determine if a hero is damaged is to :
1. Unequip any mounts.
2. Remove all troops from the hero.
3. Add to the hero a troop that is NOT in the hero's specialty.

The speed should correspond to the following table :

Troop Speed
Infantry-1 40
Infantry-2 20
Infantry-3 50
Infantry-4 30
Infantry-5 30
Infantry-6 40
Cavalry-1 60
Cavalry-2 40
Cavalry-3 30
Cavalry-4 50

That's the base speed of the troops, and your speed should never be lower. If the hero's specialty does not include that type, then the speed should be exactly equal to the base speed.

If you have a damaged hero, I'll like to test the following methods of "resetting" the damage.
1. Unequip the mount, and send the hero to his/her death, let it recover in hospital. (Tested by crumpet, did not work).
2. Unequip the mount, reroll the hero's aptitude. (If this work, the easy way out is for hithere to give every player one card of relearn for every hero).
3. Unequip the mount, refresh the hero's specialty.

If you do test any of the above, please message me in w5 (my id is 'Sisland').
Thank you.

Update (2/10/11) :: Bug has been fixed in today's unannounced maintenance.

No comments:

Post a Comment