Yes, you are right. I made a mistake. I will check the attack priorities and threat levels for BfMe1. I'll get back to ya...
Edit: Allright, here it is:
Every nonhorde unit and every horde, if capable of attacking, has a set of attack priorities. It is determined like this:
Object IsengardFighterHorde
...
Behavior = HordeAIUpdate ModuleTag_HordeAIUpdate
...
AttackPriority = AttackPriority_Infantry
End
...
End
or this
Object MordorFellBeast
...
Behavior = GiantBirdAIUpdate ModuleTag_GiantBirdAI
...
AttackPriority = AttackPriority_FellBeast
End
...
End
Every unit with AI behavior has some sort of '...AIUpdate' which contains the AttackPriority set used.
The sets are defined in the file 'data/ini/default/aidata.ini', like this
AttackPriority AttackPriority_FellBeast
Default = 35
Target GondorTrebuchetWall = 50
Target GondorTrebuchet = 50
Target GondorGandalf = 50
Target GondorGandalfGrey = 50
Target GondorGandalfWhite = 50
End
A fellbeast would therefore attack every target equally (default priority = 35), unless a trebuchet or Gandalf are in sight, in which case it would target them exclusively (priority = 50).
Since your unit presumably has a new object name and since you probably did not add this object name in the AttackPriority lists, any unit in the vicinity of your new unit will use the default priority, which is in every case slightly or considerably lower than any of the listed ones. This might be the cause of no unit targeting your new objects. Probably when testing this you also had standard units around. And the standard units would in this case always have a higher priority.
Hopefully adding your new units the the priority sets will cause your problem to go away.
Edited by Sûlherokhh, 22 December 2008 - 05:58 PM.
