Unity = green arrows. RB = blue arrows
[FDB] rev977 [Gameplay] Evaders movement path
Moderators: Slitherine Core, FoG PC Moderator, NewRoSoft
-
ianiow
- Lieutenant Colonel - Panther D
- Posts: 1224
- Joined: Fri Apr 27, 2007 11:24 am
- Location: Isle of Wight, UK
[FDB] rev977 [Gameplay] Evaders movement path
There is something different in the way RB and U calculates the geometry of Evade Moves. From comparing the two, it looks like U is not taking into account the direction of the enemy charge (i.e. the starting hex of the enemy charger)
Unity = green arrows. RB = blue arrows
Unity = green arrows. RB = blue arrows
Re: [FDB] rev977 [Gameplay] Evaders movement path
Actually, FoG(U) does take into consideration the direction of the enemy attack, it just computes this direction in a different way than FoG(RB).
While FoG(U) computes the direction of the attack as the vector between charge hex and charged unit hex'es centers, it seems that FoG(RB) considers the vector between charging unit hex and charged unit's hex'es centers (1) or charging unit charge path penultimate hex and charging unit charge path charge hex'es centers (2) (though less much probably).
Considering the direction vector starts from:
- charging unit (turn phase) start hex'es center is too much exposed to long paths direction variation (doesn't take the charge path into account)
- charging unit charge hex'es center is exposed to hex map lattice's variation (in here a vertical attacks must end either in a FL or FR hex, and hence the charge vector varies due to hex map's characteristic)
Neither of them is particularity good, all of them having strengths and weaknesses. The ideal case is probably considering the vector between charging unit penultimate hex and charged unit hex'es centers.
The right side of the picture display this. Charging from A, you can take 3 different paths to attack the same unit: a, b and c. A FoG(RB) direction vector from A to C (charged unit hex'es) won't account for the completely different a, b and c paths.. A direction vector from the charge hexes C's FL/FR to C is especially wrong when considering the charge starting from B1 (and going vertically ahead, but because of hex map's lattice, has to end in either C's FL or FR hex). Again a direction vector starting from charge path's penultimate hex to C seem to be the best:
- a charge path is from B2 (ie A's FL) to C
- b and c charge paths's is from B1 (ie A's FR) to C
- FoG(RB) evade direction 02.jpg (323.61 KiB) Viewed 3662 times
Considering the direction vector starts from:
- charging unit (turn phase) start hex'es center is too much exposed to long paths direction variation (doesn't take the charge path into account)
- charging unit charge hex'es center is exposed to hex map lattice's variation (in here a vertical attacks must end either in a FL or FR hex, and hence the charge vector varies due to hex map's characteristic)
Neither of them is particularity good, all of them having strengths and weaknesses. The ideal case is probably considering the vector between charging unit penultimate hex and charged unit hex'es centers.
The right side of the picture display this. Charging from A, you can take 3 different paths to attack the same unit: a, b and c. A FoG(RB) direction vector from A to C (charged unit hex'es) won't account for the completely different a, b and c paths.. A direction vector from the charge hexes C's FL/FR to C is especially wrong when considering the charge starting from B1 (and going vertically ahead, but because of hex map's lattice, has to end in either C's FL or FR hex). Again a direction vector starting from charge path's penultimate hex to C seem to be the best:
- a charge path is from B2 (ie A's FL) to C
- b and c charge paths's is from B1 (ie A's FR) to C
Re: [FDB] rev977 [Gameplay] Evaders movement path
Modified for rev1032 (v2.5.00.1032 GM2 build)