fheroes2
fheroes2 copied to clipboard
ihhub
Adventure map, Hero, revealed area
In fheroes2, the area revealed by the hero is reduced compared to the original game.
In original game:
In fheroes2:
Similar issue: https://github.com/ihhub/fheroes2/issues/1434.
Hello @vincent-grosbois,
If I understand, it's said in #1434 that it is intentional ?
Yes, this was done intentionally in fheroes2. Here is another case to show that this different mode of operation from the original game causes annoying problems for the player by diminishing the visibility of the original game. :)
Ok I see In that case, what do we do with this ? this is marked as 0.9 , but I'm not sure I can do anything for this issue
@vincent-grosbois.
Ok I see In that case, what do we do with this ? this is marked as 0.9 , but I'm not sure I can do anything for this issue
A discussion would be planned for this. For the time being, it would be necessary to know if this is considered urgent. So, @ihhub and @Branikolog is this urgent?
For my part, I vote for an operation as in the original game. Every square that is uncovered counts and this may change the strategy to be adopted. :)
Hello, @vincent-grosbois and @LeHerosInconnu ! The nearest release is AI/logic oriented. I believe, we can postpone this issue a little bit, so we can more deeply discuss here the problem and the solition.) But the last word is for @ihhub, surely. :)
On subject:
I really don't understand, why do we have such hexagon-like shape of area. Why couldn't we make it more round-shaped? Can we make a compromise solution between these two variants? Just by adding a small revealed area in this places....
Heroes 2 players are used to it working this way:
Why change that? Not to mention all the scenarios created with the game's original mode of operation.
Reveal area should be the same as in the original game as it's closer to circle shape and old maps depend on this shape. This is the method void Maps::ClearFog( s32 index, int scoute, int color ) which should be modified.
@ihhub, as mentioned by @a1exsh, I think we can close this issue.
Unless there is something else to do?
