fix: handle tileset-specific sortie modifiers #1958
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "hazards"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #1956
@ -311,1 +306,4 @@
];
const pushTilesetModifiers = (tileset: string): void => {
switch (tileset) {
case "SORTIE_MODIFIER_HAZARD_FOG":
I think there should be
GrineerForestTileset
notSORTIE_MODIFIER_HAZARD_FOG
Does this exclude Fire Hazard condition from Grineer Shipyard tile? Because in yesterday's Sortie it was on that tile, even though the wiki states:
Can only occur on the Corpus Ship or Grineer Galleon tileset.
https://wiki.warframe.com/w/Sortie
Aside of that, the wiki also mentions Radiation Hazard:
This modifier cannot occur with Interception missions.
And about Melee only:
This modifier cannot occur with Assassination missions.
And the Dense Fog exclusive to Grineer Forest tile is apparently only during night. Idk if this must be handled by the server.
And then the typical mission types intended to it (idk if all get currently generated): Rescue, Spy, Defense, Interception, Excavation, Survival, Exterminate, Defection, Hijack, Assassination, Plains of Eidolon, Disruption, and Assault (strangely not listed in the wiki but it shows apparently still up on Live these days as mission type on Kuva Fortress).