Page MenuHomeFeedback Tracker

Explosives such as land mines will be considered detection of the player once they explode.
Closed, ResolvedPublic

Description

If a trigger (for example) is dependent on opfor detecting blufor. Then opfor setting off a landmine placed by blufor is considered detection of blufor forces.

This seems pretty off considering that these sorts of weapons are meant to be entirely anonymous.
{F20615}

Details

Legacy ID
1562992543
Severity
None
Resolution
Open
Reproducibility
Always
Category
Design-Mission
Steps To Reproduce

Make a switch trigger dependent on opfor detecting blufor in a certain area.

Place AT mine on road.
Drive away very fast into a far away position (you being able to see the explosion is completely irrelevant.)
Wait for Ifrit to drive over mine.
Ergo this.

If you wish to make your own mission/test to investigate this trigger please do; it might help me make my own mission and try and get around this (presumably a) bug.

Apparently I cannot attach .pbo mission files in error reports. So instead I have uploaded a .rar file containing it.

Additional Information

Its fully understandable for the AI to enter a combat reaction when an AT mine goes off, but for it count as detection of an enemy force seems too much.
EG; In one mission I am trying to create, if Opfor spot Green-Army units they will call in some pretty heavy helicopter support. However the mission is centered around a convoy ambush and so weapons like AT mines are vital to the teams success.

Also seems to include "knowsabout" condition.

Event Timeline

Abokasee edited Steps To Reproduce. (Show Details)Jul 2 2013, 5:44 PM
Abokasee edited Additional Information. (Show Details)
Abokasee set Category to Design-Mission.
Abokasee set Reproducibility to Always.
Abokasee set Severity to None.
Abokasee set Resolution to Open.
Abokasee set Legacy ID to 1562992543.May 7 2016, 3:14 PM

Damn bunny rabbits are setting of our landmines again... Upvoting

MadDogX added a subscriber: MadDogX.May 7 2016, 3:14 PM

Mass closing ancient tickets with no activity for > 12 months; assume fixed or too trivial.

If this issue is still relevant in current dev build, please re-post.