Sarulas

Please add 'correcting your mistakes' to your plans for next week, thanks. And by mistakes I mean the twice botched LoS changes on Dante. You've already chosen to double down once, and now we have clips like this: Warframe character model blocks LoS: https://clips.twitch.tv/HomelyAggressiveWormPJSalt-XA21cwDUsYU4yVcd FoV changes break LoS: https://clips.twitch.tv/FineHilariousPorcupineTwitchRPG-n6J-Qnm9mlmk2rVt This such a horrible, yet predictable, look for you guys. I expected better after the change in leadership. This change was ill-conceived in the first place, and these broken attempts at fixes to the already unnessesary problem are just embarrassing. At this point, please just cut your losses and try a different approach. I've said it in previous comments, but every enemy in ability range that was tagged by 3 should be hit by 4. There's many ways to ensure this core functionality is kept, and exactly 0 of them are with LoS checks. I wish the team the best of luck in regaining the trust that's been lost with this entirely avoidable debacle.

YES. 10000% THIS. LoS was NEVER going to be a good solution.

Well, this is disappointing, but not surprising. I'll spell it out: Doubling Down--Fixing a broken mechanic that shouldn't have been present in the first place. Listening to community feedback--actually reverting the LoS changes entirely. I'm sad you made the less trustworthy choice. You introduced an unnessesary problem, and then made a better version of what is still the problem. I hope nobody on the team is surprised when people are still upset. Edit: I am not saying that Dante is perfect and needs no changes. Balance is nessesary for the health of the game and nerfs are a part of that. It does matter exactly what those changes are, though. The LoS changes had both a bad concept AND bad execution. Improving the execution isn't a full solution. And we've seen better concepts on these forums the past few days. At the end of the day, the issue is that his 4 should affect all enemies that were tagged by his 3 and are in range, even if you were in motion as they were tagged or you rounded a corner. LoS will always break that functionality in some way.

+1 because I can't 'like' any more posts on this thread

10000% this. LoS isn't just flawed because it's buggy and inconsistent. It's flawed because it fundamentally does not belong on this ability. Making the LoS check more consistent will NOT solve the actual problem here. I'm all for balancing the frame, but said balance needs to keep the feeling of playing it intact. Tweak numbers, sure, but this LoS change will neuter the tag/cash-in mechanic that is THE WHOLE POINT. There's no way this interaction wasn't originally intended, and I'm stunned that it was so easily discarded. Xao, thank you for helping me articulate why I have such a big problem with this. DE, please don't make the mistake of doubling down here when so many have so clearly called for the change to be reverted. These LoS changes would absolutely be helpful when applied to the right frames, but Dante IS NOT one of them. Ember might be, though. I'm sure that buffing her with the solutions you proposed in this post would go a long way.

There is no salvaging this mess, at least not with a hotfix like this. After the comments about this being a 'light adjustment' that was going to be 'carefully considered,' destroying the functionality of Dante's kit like this a mere 2 days later is a slap in the face. Such a high profile failure severely damages the community's trust, and will kill interest in other new frames as their power could swing wildly as the result of these unnessesary and reactionary nerfs. This LoS change must be FULLY and UNAMBIGUOUSLY reverted. Attempting to double down by fixing issues that shouldn't exist in the first place will only further erode trust. You won't get more chances at this. If tomorrow's hotfix doesn't completely solve the many issues introduced today, there will be no way to save face. And based on the outline you provided in this post, that seems incredibly unlikely. Further attempts to update the flaws with LoS checks will only draw more attention to the fact that it didn't need to be changed in the first place. Removing the restriction down the line after failing to address the problems will only cause more embarrassment. And leaving it in such a broken state is obviously unacceptable. Please. Revert this mistake. Do it now, and save yourselves the hassle and PR.