Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#2 Stack amount boxes can overlap (0.7#71)

open
Mateusz B
Battles (16)
5
2009-05-13
2009-04-14
No

Originally reported by Aidis:

#71 Creature stack number frames in battle can overlap when standing close to each other.
OH3: http://s5.tinypic.com/1ilh87.jpg
VCMI: http://s5.tinypic.com/348oaq1.jpg

http://vcmi.antypika.aplus.pl/forum/viewtopic.php?p=1846#1846

Discussion

    • summary: Stack amount boxes can overlap --> Stack amount boxes can overlap (0.7#71)
     
  • Radu
    Radu
    2009-07-11

    Please see this screenshot for stack number frames behavior: http://i4.photobucket.com/albums/y104/Zamolxis/VCMI/VCMI%2007/090711-H3CStackNumberssample.jpg

    The rules are:

    1. The creatures in the attacking army (left side of the battlefield) have the default position of the stack number box in the lower part of the hex in front of them, attached to the line separating their (front) hex and the hex in front containing the box (see Monks, Pikemen, etc in the screenshot)

    2. The creatures in the defending army (right side of the battlefield) have the default position of the stack number box in the upper part of the hex in front of the, attached to the line separating their (front) hex and the hex in front containing the box. The purpose of that is that when there's an empty hex between a friendly and an enemy creature, both boxes can be displayed without overlapping (see 1 Archangel facing 2 Gold Dragons in the upper right side of the screenshot)

    3. When the hex in front of a creature is occupied by any type of obstacle (other creature, war machine or terrain obstacle), the stack number box moves inside the hex of the creature, centered (see Paladin in screenshot). For 2-hex creatures, it is placed in the front hex of that creature, but again centered (see 1 Archangel facing 2 Diamond Dragons)

    Notes:
    - If a creature is in one of the hexes on the opposite side of the battlefield, the end of the battlefield is not considered as an "obstacle", hence their stack number box is still shown in front of them (out of the hexed area, still attached to the side of creature's hex).
    - Dead creatures are also ignored, so we may have a stack number box in the hex of a dead stack
    - Castle Walls are considered an obstacle, but moats (or similar) are not.
    (I forgot to include these 2 situations when I prepared the screenshot below)