FANDOM


Hotfix 19.6.1
  • Fixed recasting Nidus’ Ravenous not refreshing Duration.
  • Fixed Nidus losing a Mutation Stack after falling into a pit.
  • Fixed Nidus being able to use Parasitic Link on disabled Corpus Security Cameras and Turrets.


Update 19.6.0

  • Increased the base health of Nidus’ Maggots to 1k.
  • Increased Nidus’ Mutation Stack consumption from 10 to 15 when knocked into a bleedout state/death. The task of regaining 10 Stacks is quickly obtainable, making this consequence for dying too light. Although 15 Stacks is not a huge jump, we’re hoping it’s closer to that sweet spot!
  • Entering a Nullifier bubble will now drain down Mutation Stacks the longer you are in the bubble.
  • To increase the visibility of Nidus' Maggots, holding down Nidus’ Virulence will now display a HUD marker on them. Keep in mind that casting Virulence on Maggots cause them to detonate!
  • Nidus’ Ravenous Maggots no longer auto detonate when feasting on enemies. Previously the Maggots could do a majority of the grunt work and you were able to watch the carnage and gain Stacks at the same time. Now to pop the Maggots you’ll need to cast Virulence on them and rejoice in your hard earned Stack accumulation. It’s also worth noting that with testing by our team, the Stack rhythm before and after this change wasn’t noticed at all.
  • Improved the FX of Maggot explosion to better represent the intended area of explosion.
  • Nidus’ Ravenous Maggots will still attack but no longer latch on other Infested Maggots or Kuva Jesters due to awkward animations.
  • Fixed FX, Maggots, & Health regeneration while in Ravenous staying around forever if cast by a Client who leaves.


Hotfix 19.5.7


Hotfix 19.5.5

  • Fixed a crash that would sometimes occur by Nidus’ Maggots exploding when latched onto an enemy.


Hotfix 19.5.4

  • Changed Nidus’ Parasitic Link and Ravenous ability stat description from ‘ADAPTATION STACKS COST’ to ‘MUTATION STACKS COST’.
  • Increased the brightness of both Nidus’ Ravenous Maggot tails and their death FX to improve visibility.
  • Improved Nidus’ Maggot visibility if performance was suffering.
  • Nidus’ Larva will now release an enemy if it fails to ragdoll them within 3 seconds. Before, enemies that were considered ragdoll immune (not including enemies trapped in Bastille) resulted in the inability to cast Larva again due to Larva staying perpetually latched to the enemy.
  • Nidus’ Larva no longer latches enemies trapped in Vauban’s Bastille.
  • Fixed a crash caused by Nidus’ Parasitic Link ability.
  • Fixed Nidus' alternate animation sets displaying placeholder text.
  • Fixed Nidus’ Larva getting destroyed by high damage Quanta alt fire.
  • Fixed being able to heal Defense Targets with Nidus’ Ravenous ability.
  • Conclave:
    • Increased Nidus’ Virulence width to 3m in Conclave. This also improves the ability to better hit enemies moving through it.


Hotfix 19.5.2

  • Quest:
    • Fixed The Glast Gambit not properly registering alignment choice.
  • Conclave:
    • Increased the heal rate of Nidus’ passive in Conclave.
  • Fixed Virulence going through enemies without hitting them.


Hotfix 19.5.1

  • Quest:
    • Fixed colony door messages not showing for clients in The Glast Gambit.
    • Fixes indestructible tumors for clients in The Glast Gambit.
    • Partial fix for a prog stopper in The Index.
    • Fixed a progression bug when aborting in The Glast Gambit.
    • Fixed improper enemy scaling in the colony portion of The Glast Gambit.
  • Fixed Nidus’ Parasitic Link being able to stun bosses.
  • Fixed disappearing Nidus Larva.
  • Fixed script error when clients try to cast Ravenous after their previous cast was nullified.
  • Fixed Nidus Larva not appearing for clients and slime FX on enemy not being removed.


Update 19.5.0

  • Warframe introduced to the game.

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.