A.I. exempt from locked Fog Of War.

Avatar
  • Views 6 824
  • обновлен
  • Отклонен

In my map. I have created areas only accessible to each Underlord. Each Underlord has an Underminer that is behind a possession door. The doors are closed and do not allow A.I. control. The locked For of War is touching the doors as you can see from the second image but whenever I try to test my map in skirmish, the A.I. is still able to detonate their Underminers at the start of the map and the permanent Fog of War is gone but my areas are still locked and working as they should as you can see from the first image, also note the mini map.


output_log.txt


Image 2927


Image 2928

Game Version:
Steam Public
Platform:
Windows
Avatar
anonymous

Hey Electrolight,


Unfortunately after reviewing this issue with the Code Team today this issue is not going to see a fix within the remaining development of WFTO. There's a number of reasons for this but primarily it's simply a matter of resources spent vs value of fix, we're not entirely sure as to the cause of this issue but one thing is sure; the issue is deeply ingrained and to resolve it would require considerable resources that unfortunately will not be available to us moving forwards compared to spending our resources on other higher priority issues or new features.


We didn't want to leave this in limbo so as such we're now going to close this ticket as not fixable.

We know it's not desirable for issues like these to remain in game and we want to always endeavor to ensure that player experience is the best it can be. But realistically there are some issues which we won't be able to address so we want to ensure that expectations from our community align with that.


Thanks for the report and I apologize that we will not be fixing this issue. Please feel free to get in touch if you have questions. 


Avatar
Scott Richmond Programmer & Producer
  • Отклонен
Avatar
anonymous
  • Accepted

Hey Electrolight,


Unfortunately the AI are currently not programmed to take the new FOW locking into account. I would expect this to be fixed in the 2.0 patch when we overhaul the AI.