Terroriced

Found this on youtube, Deimos pets have this bug with their tails. https://youtu.be/fAKHLoQ83U4?t=8061

This is a major improvement. Prior to this, new players were never using aura mods. Glad you found this one. There is a reason that tutorials on this quest stage on Youtube have over a million views since its 2017 release with thousands of players venting about their frustration from searching for hours with no success. And that was before you made that quest mandatory. I guess the prog stop where exiting the search area in any of the mission stages bricks mission progress without new players realizing it will be fixed at some point in 2025, yes? The extraction scenes being ridiculous placeholder drone going up, you will notice in 2026? New players speaking to Konzu then entering the Plains to search for Saya 'on the outskirts of Cetus' wasting hours of time while also unknowingly aborting the quest? Cant you just lock the door until they find Saya IN Cetus? New players talking to Saya then making the same mistake, because they have to talk to her twice and click 'accept' and they dont know that and instead run into the Plains again? Saya's Vigil is the worst quest in the game and you made it mandatory for game progression without checking for pitfalls at least once. How is your game design philosophy still 'me and my coworker could do it so anyone can' and not 'how could a player get stuck here'? New players didnt watch 176 devstreams, many dont even search for info outside the game. Many dont even pay attention half the time. Do you want paying customers or not? Do nearby companions still prevent me from picking up keyglyphs? Finally. Player have been giving feedback about this issue for a long time. Glad it has been finally looked at. Disruption on Jupiter still uses Little Duck dialoge instead of the intended Ordis/Alad V conversations though (https://warframe.fandom.com/wiki/Alad_V/Quotes#Corpus_Gas_City_Disruption) fixed but not in patch notes This happened after Konzu showing the weird drawing of him, Saya and Onkko to the player . With all the fixes it almost seems like you made someone look at the early game content and that is good. Most players drop off early because of all the pitfalls and poor game design. All it takes is one employee at DE to be responsible and repeatedly look at videos, VODs and other new player response to fix those big issues. You want the game to grow, right?

Warding Halo, Nezhas 3rd ability does not give 90% damage reduction when receiving high damage. This bug is being ignored while more and more new content restricts revives. Cant even revive myself after dying to a bug.

How many years did we wait for this? I still remember when this broke. Could have just compared the last working build with the first bugged one to find the issue, but this was not on DEs radar.

There is a bug with Nezha where he doesn't get damage reduction from Warding Halo, if incoming damage is higher than what the UI counter of that ability shows. This bug lets enemies oneshot Nezha in high level gameplay very often. Please investigate.

Thx. Yeah, too bad I was focused on the Nighwave non-recoverable weeklies FOMO instead of this. My bad I guess.

Wait, I missed an event reward? I dont even know what that glyph is called or how it looks like.

It's been over 5 years since the Nezha bug, where Warding Halo does not grant damage reduction, has been first reported. DE remains unaware.

One day they will fix Nezha not receiving 90% damage reduction, right?

Grenades in Archon hunts do this consistently if my shields are down. Blitz Eximus too. Narmer enemies can do that too. EE.log: 2144.945 Game [Info]: Terroriced was killed by 1,335 / 12,499 damage from a level 147 PNWNarmerFemaleGrineerAvatar399 using a PNWNarmerMaskPowerSuit But I would call that Narmer ability scaling another separate bug too. I finished the investigation and can conclude that the old bug formula is still correct today. (raw_damage - Warding_Halos_points) reduced by other sources of damage reduction for any hit that breaks Warding Halo instead of the intended 90% damage reduction. This bug often instantly kills Nezha. Im just glad that all aspects of this bug are known and didnt change, which I hope can make it easier for players to communicate it and for the devs to fix it one day. Here are my notes from todays testing, but they are not formatted to help explaining every step.

Yes it is inconsistent and random. The bug happens every single time when Warding Halo breaks, but you will only really notice it if Warding Halo was low at that time and enemies are high level, which in combination can reach crazy damage numbers. Its based on luck. I tested pure toxin damage with the aura from infested toxic Eximus and it behaves exactly like any other damage type. Only in combination with other damage types in the same hit do we see a deviation from the established 'regular bug variant'.

Im currently recalculating if current numbers for the normal bug variant are still consistent with observations from previous years. So far it looks like they are and I need to edit my previous comment again. And now on to the shieldgate talking point: The shieldgate argument is a bit tricky. Normally, adding another damage type to an attack that already includes toxin should not kill Nezha if the toxin component is not able to do it alone and shields are up, because they dont interact, but in the case with Archon Nira there is a hit with her Verdilac that has both toxin and IPS at the same time, where the IPS damage actually helps the toxin damage that bypasses Warding Halo to 'grow' despite it not being changed at all. Im gonna quote my example from the bug report: I think it is very hard for me to compile this interaction into a short and easy to understand phrase and talking about the shieldgate hasnt been too successful as a quick explanation yet. But this is how I perceive it in my head. I expect the shieldgate to save me, but the IPS damage just teams up with toxin and obliterates Nezhas HP. In high level gameplay even the standard bug variant will instantly kill Nezha, when the shieldgate isnt up, which makes health tanking inefficient way earlier than expected.

Thanks for bringing this up. I hope this bug will be fixed rather soon than in another 5 years. It was first reported on in 2018 btw! I have been waiting so long :( I also want to clarify on the math that you quoted me on. For the normal bug variant, unfortunately the Duviri update has changed things for the worse. The math used to be easy but now it doesnt make sense anymore. The only observable metric is that even more damage now bypasses Warding Halo, but there seems to be no easy to identify calculation anymore. Warding Halos points used to be added to your heath (or shields if they were up) instead of applying a damage reduction, but now something else happens that doesnt produce predictable values. Nezha now basically receives almost full damage and I dont know why. Edit: I did numbers testing in simulacrum again against different lvl enemies and the old bug formula is still correct today. (raw_damage - Warding_Halos_points) reduced by other sources of damage reduction For the rare bug variant I investigated the interaction with Archon Nira again in March and fixed some major errors in my calculations. There is an actual easy to understand explanation now, why toxin damage is so deadly to Nezha when inflicted together with other damage types in the same hit. You can read about it in this comment. Please dont use that old quote of mine about Archon Nira anymore as it is incorrect / outdated information. Thanks for caring about the issue. Edit: Im investigating the standard bug variant again, maybe the old formula is still correct. Edit2: It is still correct.

Any chance this could be solved in the Abyss of Dagath Update?

With this change you will lock a pretty big percentage of new players out of progressing past earth. I watched most new player videos that were posted on Youtube for a couple of years (I'm weird, I know) and a lot of those players can't find the glass shards, venture out of the area marked on the minimap, ignore or react slowly to the 'abandoning objective' warning, thereby bricking the mission (can't be completed anymore but doesn't end or communicate this fail state). Those players will then search for a glass shard on the entire plains for sometimes hours, get frustrated and exit the mission via Esc --> abort mission. This needs to be fixed urgently. No more 'abandoning objective' fail state please and also please add markers to those glass shards that appear after enough time has lapsed. You would be surprised to learn that outside of the quest way more new players exit the Plains of Eidolon by aborting the mission instead of returning to Cetus via the gate, because they don't remember where the gate was, never learned that they are supposed to go back and they don't understand that they LOSE ALL ITEMS they collected if they don't. So many multiple hours first time Plains of Eidolon videos end with the players aborting the mission with twitch chat screaming in pain. Big part of the problem is the way the game describes what consequences aborting the mission has to the player. 'You will keep progress but forfeit the completion rewards and bonuses.' This is massively misleading. Every single new player who encountered and read this text assumed it was safe to abort the mission. Every single one of them. 'Oh I will keep my stuff and just not get the bonus. Ok, let's do this.' Instead this should read: 'You will FAIL THE MISSION and LOSE ALL ITEMS and only retain base affinity' You need to understand how to properly communicate information to players. I'm baffled that this wasn't figured out yet. Here are some theoretical examples how not to communicate: If you gave new players a warframe mod upon completing the Awakening quest that reads 'convert 60% affinity into extra damage but forfeit the affinity rewards and bonuses' but don't explain them those affinity don't go to character / account progression anymore, they would put it on and slow their progression by 60%. If you gave new players an inbox with an option that reads 'temporarily unlock all warframes, companions and weapons for 7 days but forfeit the mission rewards and bonuses.' but don't explain to them they will be left with zero items, affinity and resources after that time period, most of them will be very surprised and they will not like it.