Minimap reveals shroud prematurely when vision points are less than MP (GNA #25622)

[wesnoth-bugs]

Original submission by shiki on 2017-03-23

(Reproduced on Archlinux)
Release: 1.12 / 1.13.7+dev
Priority: 5 - Normal
Severity: 3 - Normal

[wesnoth-bugs]

Modified on 2017-03-23

shiki wrote:

When a unit has more movement points than vision points, it is showing the shrouded area on the minimap too.

I think it is good that it's not revealing the shroud, but the minimap shouldn't do so either.

I submitted this to early, can someone adjust change the title?

(file #29900)

shiki added attachment: minimap.png

[wesnoth-bugs]

Modified on 2017-03-23

shiki wrote:

Note: The unit has to be selected for this.

[wesnoth-bugs]

Modified on 2017-03-23

wedge009 wrote:

How does a unit see more than it can move? I thought that is a standard game-play rule. Is this from a custom unit? The only time I can think that movement would be impaired is if an enemy is in your way, but the vision should be impaired too.

I did a quick check of the above scenario and found the mini-map followed the main map in its shroud-revealing behaviour.

wedge009 changed title: Minimap -> Minimap reveals shroud prematurely

[wesnoth-bugs]

Modified on 2017-03-24

shiki wrote:

It's the other way around, she can move more than she can see.

For the unit_type exists the movement key and the vision key. By default that is the same, I doubt that really somebody is using the vision key. In this case I gave her more moves with debug mode.

[wesnoth-bugs]

Modified on 2017-03-24

wedge009 wrote:

Ah, debug mode thing. That's why I couldn't test it.

But yes, standard rule is movement = vision.

[sevu]

I just saw that this doesn't happen in 1.12

[CelticMinstrel]

We should try to get this fixed for 1.14.

[jostephd]

Submitted #2150

[jostephd]

An easy way to test this is by running 'wesnoth -t' and clicking on the Elvish Rider at (8,11).