BUILD #: 40874
OS: Windows 10
Resource 210 controls among other things, the ability to reveal relics to the player :
- New AMOUNT_REVEAL_CLASS added as #210: set a class to reveal gaia units.
However, instead of simply spawning a temporary map revealer over the desired units, the bonus instead reveals the whole area covered by the line of sight of these units. This is particularly noticeable with wolves, where a very large area will be revealed due their very large line of sight. On the opposite, gaia units with no line of sight like trees will never be revealed.
Instead, just like in UserPatch or with the Vietnamese bonus, the effect should be to just spawn a temporary map revealer over the unit.
FREQUENCY OF ISSUE
100% of the time / matches I play (ALWAYS)
Here’s the steps to reproduce the issue:
- Set Resource 210 to 10 (Predator class).
- Start the game : very large areas of the map will be explored, much more than intended
IMAGE & ATTACHMENTS
Thank you for the report @TriRem! I’ve compiled the information you provided and passed it along to the team for investigation.
Hey there @TriRem! The team could use some additional information on this issue:
- What Condition/Effect are you using?
- Are you selecting Resource 210 from a drop-down or setting the Item ID?
Let me know and I’ll get this information passed along to the team!
Sure, the reproduction steps are easy:
Using AGE, change resource 210 for any civ and set it to 10 (Predator Class).
With said civilization load any scenario or random map containing wolves. The vision given over the units is as large as the line of sight of the wolves themselves, in our case over 12 tiles. The intended effect should be to only explore a 3x3 square over the unit, similar to how Relics are revealed for Burmese.
Using the scenario editor and a trigger to edit the resource won’t have any effect, due to another bug regarding this resource ( Resource 210 (Reveal Relics) not firing after the start of the game ).
Was this issue solved? (i’ve been keeping it on my list for a long time and maybe there’s a chance it was already fixed but i didnt notice)