Random assault encounters have complex AI package management that involves a series of preset "Links" aliases. These aliases are used to prevent the encounter from starting before the player approaches, and then to start and manage the encounter once the player is near enough. Actors spawned or used by the encounters are expected to be forced into the links aliases, and may misbehave when not included in one. For example, attackers not included in a links alias will typically stand at their spawn point indefinitely rather than participating in the assault.
In the case of REAssaultCC01, aliases 64, 65, 66, 67, and 68 are being forced into the wrong links aliases. Judging by the alias IDs, the developer who made this quest deleted the original attackers and defenders except for Attacker01 and Defender01, configured the remaining two, and then copied them and changed their spawn point without changing their links alias. This results in a case where VicDog01, VicDog02, and Bloodbug01 are not linked to the encounter handling and are likely to misbehave. In order to fix this, the following changes should be made:
- VicDog02 (alias 64) should be forced into Attacker02Links rather than Attacker01Links.
- VicDog03 (alias 65) should be forced into Attacker03Links rather than Attacker01Links.
- Bloodbug02 (alias 66) should be forced into Defender02Links rather than Defender01Links.
- DeadScavenger01 (alias 67) should not be forced into any alias, as they are meant to be dead. Force into NONE rather than Defender01Links.
- DeadScavenger02 (alias 68) should not be forced into any alias, as they are meant to be dead. Force into NONE rather than Defender01Links.
Issue Data
Issue #36026: REAssaultCC01: Mishandled aliases