chore: allow MT_CAPTURE for sorties (#1792)
e.g. `SolNode1` is a capture mission but it should still be a valid node for sorties. Not that the mission will actually be a capture. Reviewed-on: #1792 Co-authored-by: Sainan <63328889+Sainan@users.noreply.github.com> Co-committed-by: Sainan <63328889+Sainan@users.noreply.github.com>
This commit is contained in:
parent
15aaa28a4f
commit
f3601ec43e
@ -263,7 +263,6 @@ const pushSortieIfRelevant = (worldState: IWorldState, day: number): void => {
|
|||||||
sortieFactionToFactionIndexes[sortieBossToFaction[boss]].includes(value.factionIndex!) &&
|
sortieFactionToFactionIndexes[sortieBossToFaction[boss]].includes(value.factionIndex!) &&
|
||||||
value.name.indexOf("Archwing") == -1 &&
|
value.name.indexOf("Archwing") == -1 &&
|
||||||
value.missionIndex != 0 && // Exclude MT_ASSASSINATION
|
value.missionIndex != 0 && // Exclude MT_ASSASSINATION
|
||||||
value.missionIndex != 5 && // Exclude MT_CAPTURE
|
|
||||||
value.missionIndex != 10 && // Exclude MT_PVP (for relays)
|
value.missionIndex != 10 && // Exclude MT_PVP (for relays)
|
||||||
value.missionIndex != 21 && // Exclude MT_PURIFY
|
value.missionIndex != 21 && // Exclude MT_PURIFY
|
||||||
value.missionIndex != 22 && // Exclude MT_ARENA
|
value.missionIndex != 22 && // Exclude MT_ARENA
|
||||||
|
Loading…
x
Reference in New Issue
Block a user