I understood that fully and yes, that very well could be the problem.

Maybe they should try setting it to "wumbo".

I've been noticing this a lot, I've actually made it a habit since the nerf to attack from the front and not expect any wonders from attacking from behind. This actually makes sense how you've explained. I thought they just -blam!-ed up the cone angle and reversed it by accident on the nerf. This is a really constructive theory and wouldn't mind seeing some input from Bungie's end.

It's a good theory and all but it wasn't broken in year 1. So fixing it is only a matter of undoing every nerf that happened in year 2. That would make a lot of people happy too.

I think this proves that bungie employees don't poop...

[spoiler]Made You Look[/spoiler]

Like most things in life, issues should only be discussed after a solid half hour of reflection on the can Good life choices, my boy

I think it is mostly a question of effects. Blink jump acts as a fainted manoeuver dazzling your opponent (on his/her screen). If your coming from the back, there would be no true reason to use blink melee, except for gaining a little range, to your advantage. As for myself, I prefer trying to tick 'em off so they turn around and battle... Although the attack (to prevent frustration) should garanty landing damages as soon as you have targeted and pressed "RB", the hitbox then serves as reference for the level of success of the melee hit. Meaning that if I sent melee to a gardian facing me, I am sure to deal him at least little damage in situations where he runs out of hitbox AND (my favourite) overkill if I calculated correctly space notions... I would expect the player to know what distance is required to perform, in optimal range, the so-called blink. Concerning backstabbing, I would tell you not to forget another human is actually controlling your target. It is totally fair for them to get the chance to avoid the attack, either by running/sprinting or turning around to hit you in a rush. Lets compare to elements: When your enemy has void shield and you strike it with arc element, you don't mind dealing fewer damages. So, because of the angle of the melee attack, the player should consider having failed his pursuit by rushing into backstabbing, without allowing the opponent to engage in an adequate fight. Therefore, blink strike needs some sort of target lock. An interesting alternative could imply an extended hitbox which contains more presice scale of potential damages. Yours truly, I hope my ideas, one day, will come in handy.

I'm on the pooper writing this. It's a good theory and I as well have zero knowledge of programming. Like everyone else on this forum I assume every fix should take 5 seconds and their job is way too easy to be messing up this much. ;)

a wise man said once: Unlagged uses a technique called “backward reconciliation” for hitscan weapons' hit tests. For the duration of a hit test, it moves players to where you saw them when you fired. (It knows because it sent you the player origins in the first place, it saves that information up in a history queue, and your fire command contains a timestamp.) After the hit test, it moves them back. Moving player entities around like that is perfectly fine, as long as the entities' states are restored exactly, [u]and as long as no code runs which requires players in their correct state [/u]while the [u][b]server[/b][/u] is in a backward-reconciled state. Unlagged is very[u] careful [/u]about such things, so it doesn't present any problems.

Front hand/Back hand ?

Maybe people are just wearing their gear backwards