Hotfix 37.0.4 (2024-10-10)

Hotfix 37.0.2 (2024-10-03)

Update 37.0 (2024-10-02)

Hotfix 36.1.6 (2024-09-05)

Hotfix 36.1.3 (2024-08-27)

Update 36.0 (2024-06-18)

Hotfix 35.5.6 (2024-04-10)

Line Of Sight (Los) Improvements

As announced last week, we have revisited LoS checks on other Warframes to bring them in line with the new and improved version of Dante’s LoS added in Hotfix 35.5.4.

To reiterate, there are now two variations of LoS checking:

  1. The first type of check sees if any part of the enemy has been drawn on the screen, so that any part of an enemy, big or small, is considered visible/eligible to pass the LoS check.
  2. The second type of check is for enemies that are not on screen. We now check for LoS to the enemy's head, torso, and feet instead of only to their body which will increase reliability there as well.

For Abilities that hit enemies in a full circle around you, both checks are used: Once to evaluate enemies that you can see and then a second sweep to check targets to the sides and behind you that aren't visible.

The above changes also tangentially fixes the issue of low FOV preventing LoS checks from occurring (this was most reported for Mirage’s Prism).

General Fixes

Hotfix 35.5.3 (2024-04-04)

Hotfix 35.5.2 (2024-03-28)

Update 35.5 (2024-03-27)

Mirage Eclipse Rework

After a great amount of input from the Community, Mirage’s Eclipse ability no longer determines the buff (Solar or Lunar Eclipse) to apply based on the environment’s light level, will always be at maximum strength, and is now a Tap/Hold ability!

In its previous state, Eclipse was quite unreliable. One step in any direction could suddenly switch the buff or lower its strength, which left players little control over its benefits. It also did not function correctly in every area of the game, notably in Open Landscapes and Albrecht’s Laboratories where only the Solar Eclipse buff would be active at full strength - even at night time.

The changes listed below affect both Mirage and Eclipse applied via the Helminth (with some notable exceptions listed below its Diminished Effectiveness).

How it works:

Scaling change:
Since the ability no longer depends on level lighting to determine the buff type, the buffs themselves also no longer scale based on light level. Instead, their previous maximum effect is now the base (affected by Ability Strength):

Helminth Diminished Effectiveness Change:
Eclipse has been one of the most popular Helminth abilities, so by fixing its unreliability related to light sources and making its buffs guaranteed, a rebalance was in order to compensate. This change does not affect the ability for Mirage, only when applied via the Helminth.

Mirage Prism Changes

In its current form, Prism's damage scaling is affected by environmental lighting at Mirage's position, which is impacted by the same inconsistency issues that Eclipse suffered from. The team has reviewed Prism and made similar changes to Eclipse:

Hotfix 35.0.8 (2024-01-11)

Update 35.0 (2023-12-13)

Mirage Eclipse Changes:

Tenno who are familiar with Mirage's ability Eclipse know how temperamental it can be. Areas that look light are actually dark and vice versa, which can make it rather difficult to know how much of a bonus the ability is actually giving you at any moment.

To address this issue, the HUD icon for Eclipse will now continuously update to show an accurate and responsive state of what effect Mirage is currently getting, rather than just showing the maximum values from standing in light or dark. We have also updated the HUD icons with names to distinguish which buff is being given:

This at least gives us (and you) a better tool to measure what Eclipse is really doing.

With this update we started assessing how inconsistent and frustrating this ability was, and noticed a variety of problems: it didn’t work properly on the Plains of Eidolon and, super relevant for this update, it didn’t work at all with the new lighting technology in Albrecht’s Laboratories!

We are still considering what we can do to make this ability better in the long term. Stay tuned for further changes on Eclipse.

TOP FIXES
GENERAL FIXES

Hotfix 34.0.5 (2023-10-26)

Update 34.0 (2023-10-18)

Base vs Final Stats in Modding - Health / Energy / Shield / Armor Stat Overhaul

If you’ve spent any time invested in the deeper nuances of Modding, you may be familiar with “Warframe Math” - math that upon first glance doesn’t really make sense, but once you learn the inner workings of the game, it all comes together. While we can appreciate the value that complex systems offer to a certain subsect of players, there are other aspects of the game that should have clear and understandable outcomes. Namely: Shield, Health, Energy, and Armor Modding.

Pop quiz: what is 300 + 440%? If you answered 740, you may just be an Excalibur player.

Vitality (+440% Heath), Redirection (+440% Shields), Flow (+150% Energy), and Steel Fiber (+110% Armor) come with large modifier values that don’t seem to match their outcome in-game. This is because these Mods apply their multiplier to the base stats of the Warframe - i.e., the stats you have at Rank 0. In the Excalibur example, a Rank 30 Excalibur’s Health stat of 300 earns an additional 440 Health from max rank Vitality (+440% Heath) since it applies to his base rank Health stat of 100, resulting in 740 total health.

In this update, we have removed this obfuscation by having Health, Shield, Energy, and Armor Mods apply to the stats of Warframes at their current rank. Continuing our Excalibur example, instead of Vitality always applying to Excalibur’s base rank 100 Health, it would apply to his Health stat based on his rank - namely, the stat you can actually see in your Arsenal. If your Excalibur were Rank 30, his Health stat would be 300, which means Vitality’s multiplier would be calculated off of 300.

With previous Health and Mod values, additional adjustments are needed to make this revision work while maintaining game balance. By only changing where the multiplier applies, a Rank 30 Excalibur would receive an extra 1,320 Health from max rank Vitality, resulting in a total health stat of 1,600. This outcome is a significant buff, which is not the intention of this system change.

To remedy this, we approached this problem in two ways:

1 - We reduced the overall multiplier for Health, Shield, Energy, and Armor Mods.
Since these now affect Max Rank Warframe stats, these Mods need to scale differently to maintain the status quo. Additionally, we wanted these new values to be as clear and understandable to all players as possible! Here are a few examples of these value changes:

Note: These are not all of the Mods affected by this change. We share the comprehensive list further down in this section of the update notes.

Doing some quick math, this means that a Rank 30 Excalibur (300 Health) with a reworked Vitality Mod (+100% Health, applied to the final Health stat) would receive 300 extra Health, for a total of 600. That, in contrast, is a nerf, which we also don’t want to do.

So, our next step:

2 - We adjusted Warframe Health, Shield, Energy, and Armor values to keep the end result of the revised Mods as close to the original values as possible.

With this change, Excalibur’s Rank 30 Health stat is 370. With +100% Health from a max Vitality Mod, his resulting Health stat would be 740, which matches what it was originally.

While this path to the same result may seem a little complicated, the outcome matches our intention: we want players to be able to look at their Health, Shield, and Armor Mods, and be able to understand how they affect the stats they see in their Arsenal.

In addition to everything above, we also increased the base stat values for Warframes so that these revised Mods offer similar value for lower-ranked Frames. To do so, we reduced the amount of Health/Shield/Energy that Warframes earn per rank in half, and transferred the sum of that value to their base stats.

For Armor, this is the one stat that does not increase with your Warframe’s level (with some exceptions). Armor values across the board have been slightly increased to compensate for the Mod changes.

Not to beat a dead Kaithe, but Mods will now be applying to the Max Rank stat instead of the Base Rank. You may look at these numbers and think “nerf” or “buff” depending, but the outcome is that total Modded values are the same, if not a little higher in some cases.

Warframe Stat Changes:

MIRAGE
Health: Base Rank - 200 (from 80) / Max Rank - 300 (from 240)
Shields: Base Rank - 120 (from 80) / Max Rank - 300 (from 240)
Armor: Base Rank - 105 (from 100)
Energy: Base Rank - 175 (from 150) / Max Rank - 225 (from 225)

MIRAGE PRIME
Health: Base Rank - 200 (from 80) / Max Rank - 300 (from 240)
Shields: Base Rank - 310 (from 110) / Max Rank - 410 (from 330)
Armor: Base Rank - 185 (from 175)
Energy: Base Rank - 175 (from 150) / Max Rank - 225 (from 225)

While there may be significant changes to Warframe Stats and Mod values as a part of this overhaul, the end result is that your Builds should mostly stay the same. The key difference is the added clarity of what your Health / Shield / Energy / Armor Mods do in your Upgrade screens!

Top Fixes:

Hotfix 33.5.3 (2023-06-23)

Hotfix 32.2.10 (2023-01-18)

Update 32.2 (2022-11-30)

Hotfix 32.0.9 (2022-10-05)

Hotfix 32.0.7 (2022-09-28)

Update 32.0 (2022-09-07)

Hotfix 31.7.2 (2022-08-17)

Update 31.1 (2022-02-09)

Update 31.0 (2021-12-15)

Update 30.7 (2021-09-08)

Update 30.5 (2021-07-06)

Update 30.3 (2021-05-25)

Hotfix 30.2.1 (2021-05-13)

Hotfix 30.0.8 (2021-04-27)

Hotfix 30.0.1 (2021-04-13)

Update 30.0 (2021-04-13)

Hotfix 29.6.8 (2021-01-25)

Hotfix 29.6.1 (2020-12-18)

Update 29.5 (2020-11-19)

Update 29.3 (2020-10-27)

Hotfix 29.2.4 (2020-10-15)

Hotfix 28.3.3 (2020-08-13)

Update 28.3 (2020-08-12)

Hotfix 28.0.6 (2020-06-24)

Update 28.0 (2020-06-11)

Update 27.4 (2020-05-01)

Update 27.3 (2020-03-24)

Update 27.2 (2020-03-05)

Hotfix 27.1.0.1 (2020-02-04)

Update 27.1 (2020-02-04)

Hotfix 27.0.12 (2020-01-23)

Update 26.1 (2019-11-22)

Hotfix 25.7.4 (2019-09-05)

Update 25.7 (2019-08-29)

Update 25.6 (2019-08-08)

Explosive Legerdemain - Sleight of Hand Augment - Mirage
Total Eclipse - Eclipse Augment - Mirage

Hotfix 25.4.1 (2019-07-24)

Hotfix 25.3.3 (2019-07-16)

Update 25.2 (2019-06-19)

Update 25.1 (2019-06-05)

Update 25.0 (2019-05-22)

Hotfix 24.7.2 (2019-04-17)

Update 24.6 (2019-04-04)

Update 23.5 (2018-08-24)

Hotfix 23.3.2 (2018-08-13)

Hotfix 23.0.2 (2018-06-15)

Update 23.0 (2018-06-15)

Update 22.20 (2018-05-17)

Hotfix 22.18.5 (2018-04-24)

Hotfix 22.16.4 (2018-03-20)

Update 22.14 (2018-03-01)

Hotfix 22.12.3 (2018-02-12)

Update 22.12 (2018-02-09)

Update 22.8 (2017-12-21)

Update 22.7 (2017-12-12)

Update 22.4 (2017-11-23) Mirage Sleight of Hand Changes: In addition to booby trapping nearby objects, Mirage’s Sleight of Hand now spawns a jewel that attracts near by enemies! If Sleight of Hand is used with Hall of Mirrors, each of her clones will also place a smaller jewel with a smaller enemy attraction. The jewel Damage, Blind Duration, and Range increases with the level of Sleight of Hand.

Hotfix 22.2.5 (2017-11-11)

Update 22.0 (2017-10-12)

Update 21.5 (2016-08-16)

Hotfix 21.4.2 (2017-08-11)

Hotfix 21.0.9 (2017-07-17)

Update 21.0 (2017-06-29)

Hotfix 20.7.3 (2017-06-16)

Hotfix 20.5.2 (2017-05-18)

Update 20.1 (2017-04-05)

Hotfix 20.0.9 (2017-04-03)

Hotfix 20.0.7 (2017-03-30)

Hotfix 20.0.4 (2017-03-27)

Update 19.13 (2017-03-09)

Update 19.12 (2017-03-02)

Hotfix 19.11.5 (2017-02-28)

Hotfix 19.11.2 (2017-02-17)

Update 19.7 (2017-01-18)

Hotfix 19.6.3 (2017-01-17)

Update 19.4.2 (2016-12-20)

Hotfix 19.3.1 (2016-12-08)

Hotfix 19.2.1 (2016-12-03)

Update 19.2 (2016-12-01)

Update 19.1 (2016-11-25)

Hotfix 19.0.3 (2016-11-14)

Hotfix: The Index Preview 4 (2016-10-25)

Update: The Index Preview (2016-10-20)

Hotfix: The Vacuum Within 3 (2016-10-13)

Hotfix: Specters of the Rail 0.1 (2016-07-08)

Update 18.13 (2016-05-27)

Hotfix 18.10.6 (2016-05-06)

Hotfix 18.10.4 (2016-05-02)

Update 18.10 (2016-04-29)

Update 18.7 (2016-03-30)

Hotfix 18.6.2 (2016-03-22)

Update 18.5 (2016-03-04)

Update 18.1 (2015-12-16)

Hotfix 18.0.8 (2015-12-11)

Hotfix 17.6.1 (2015-10-07)

Update 17.5 (2015-10-01)

Update 17.4.5 (2015-09-23)

Update 17.4 (2015-09-09)

Update 17.3 (2015-09-02)

Update 17.2.4 (2015-08-26)

Update 17.0 (2015-07-31)

Hotfix 16.10.2 (2015-07-02)

Update 16.10 (2015-06-25)

Update 16.8 (2015-06-10)

Hotfix 16.4.3 (2015-04-24)

Update 16.4 (2015-04-23)

Update 16.3 (2015-04-09)

Update 16.2 (2015-04-01)

Update 15.16 (2015-02-25)

Update 15.13 (2015-02-05)

Hotfix 15.11.1 (2015-01-22)

Update 15.11 (2015-01-21)

Hotfix 15.10.1 (2015-01-16)

Update 15.10 (2015-01-15)

Update 15.9 (2015-01-08)

Hotfix 15.7.2 (2014-12-19)

Update 15.6 (2014-12-11)

Hotfix 15.5.9 (2014-12-08)

Hotfix 15.5.7 (2014-12-03)

Update 15.1 (2014-11-05)

Hotfix 15.0.6 (2014-10-27)

Hotfix 15.0.5 (2014-10-27)

Update 15.0 (2014-10-24)

Update 14.10 (2014-10-08)

Update 14.9 (2014-10-01)

Update 14.8 (2014-09-24)

Hotfix 14.7.3 (2014-09-19)

Update 14.7 (2014-09-17)

Update 14.6 (2014-09-11)

Hotfix 14.5.1 (2014-08-30)

Hotfix 14.5.0.2 (2014-08-28)

Update 14.5 (2014-08-28)

Update 14.2 (2014-08-13)

Update 14.1 (2014-07-30)

Hotfix 14.0.9 (2014-07-26)

Hotfix 14.0.6 (2014-07-22)

Hotfix 14.0.5 (2014-07-21)

Hotfix 14.0.4 (2014-07-21)

Hotfix 14.0.1 (2014-07-18)

Update 14.0 (2014-07-18)