FIX: Bulltrue still results in death

I sincerely hope 343i is doing something to fix the issue of getting a bulltrue and still dying. It’s bad enough in normal game modes but it really shows when one plays Living Dead where there’s nothing but shotguns and swords. It’s a really annoying problem in Reach that, to the best of my knowledge, never existed before, and it should be very high on the list of fixes to MM. What does everyone else think?

the problem is latency, they can’t fix latency.

on the sword users screen, he hit you before he died, on your screen it is the other way around, if 343i were to patch it so the hosts decides then there would be a lot of un-registered hits with the sword and a lot of comaplaining about how there sword is very inconsistent.

> the problem is latency, they can’t fix latency.
>
> on the sword users screen, he hit you before he died, on your screen it is the other way around, if 343i were to patch it so the hosts decides then there would be a lot of un-registered hits with the sword and a lot of comaplaining about how there sword is very inconsistent.

Then make sword user host, always! Pick it up and you become host! It would be a fool proof plan, with no sort of bad consequences whatsoever, right?

> the problem is latency, they can’t fix latency.
>
> on the sword users screen, he hit you before he died, on your screen it is the other way around, if 343i were to patch it so the hosts decides then there would be a lot of un-registered hits with the sword and a lot of comaplaining about how there sword is very inconsistent.

Now perhaps my memory is just fuzzy on the matter, or it could be caused by the upgraded graphics and game mechanics, but, I don’t recall having these problems in Halo 3.

You speak the truth. This is an extremely annoying problem. The point of the bulltrue is to award you a medal for essentially saving yourself from the instant death of a sword lunge. I also don’t remember this problem in Halo 2 or 3 so if anyone can elaborate why it happens in Reach, and why it can’t be fixed in Halo 4, I’d be interested to know.

> the problem is latency, they can’t fix latency.
>
> on the sword users screen, he hit you before he died, on your screen it is the other way around, if 343i were to patch it so the hosts decides then there would be a lot of un-registered hits with the sword and a lot of comaplaining about how there sword is very inconsistent.

So what did Bungie do in Halo 3 that made this issue non-existent? In Halo 3, it was perfect. Reach came along and bulltrues equaled in mutual deaths and latency existed in both games.

> You speak the truth. This is an extremely annoying problem. The point of the bulltrue is to award you a medal for essentially saving yourself from the instant death of a sword lunge. I also don’t remember this problem in Halo 2 or 3 so if anyone can elaborate why it happens in Reach, and why it can’t be fixed in Halo 4, I’d be interested to know.

Agreed
Never happened in older halo games just Reach .

> > the problem is latency, they can’t fix latency.
> >
> > on the sword users screen, he hit you before he died, on your screen it is the other way around, if 343i were to patch it so the hosts decides then there would be a lot of un-registered hits with the sword and a lot of comaplaining about how there sword is very inconsistent.
>
> Then make sword user host, always! Pick it up and you become host! It would be a fool proof plan, with no sort of bad consequences whatsoever, right?

Someone get this man to 343!!! He knows what’s up!!

> > the problem is latency, they can’t fix latency.
> >
> > on the sword users screen, he hit you before he died, on your screen it is the other way around, if 343i were to patch it so the hosts decides then there would be a lot of un-registered hits with the sword and a lot of comaplaining about how there sword is very inconsistent.
>
> So what did Bungie do in Halo 3 that made this issue non-existent? In Halo 3, it was perfect. Reach came along and bulltrues equaled in mutual deaths and latency existed in both games.

In halo 3, whoever happened to be physically closest to the host, won. Do you really think thats better? Reach has a fairer netcode than that, but there are some hard limits to how fast information can move through this universe which means this is a problem which is impossible to fix.

The double melee death is annoying for sure. But in Halo 3 weapon kills trumped any type of melee kill every time. Aslong as it was within the span of time a melee may be “contested”. Now that it has spread to double deaths of all varieties and weapons in Reach, I find the current state of the game in this reguard is unacceptable.

Getting a bulltrue and still dying is no glitch. In fact, the mechanic that causes this to happen was very intentional. As A Haunted Army previously explained “on the sword users screen, he hit you before he died, on your screen it is the other way around”. In Halo 3, the game compensated for this by taking the action which reached the host first. In Halo: Reach, the game compensated for this by taking both actions.

There is a little bit more too it than that but that is the general idea. I will agree that what we had in Halo: Reach is not perfect but it is certainly an improvement from Halo 3.

> > > the problem is latency, they can’t fix latency.
> > >
> > > on the sword users screen, he hit you before he died, on your screen it is the other way around, if 343i were to patch it so the hosts decides then there would be a lot of un-registered hits with the sword and a lot of comaplaining about how there sword is very inconsistent.
> >
> > So what did Bungie do in Halo 3 that made this issue non-existent? In Halo 3, it was perfect. Reach came along and bulltrues equaled in mutual deaths and latency existed in both games.
>
> In halo 3, whoever happened to be physically closest to the host, won. Do you really think thats better? Reach has a fairer netcode than that, but there are some hard limits to how fast information can move through this universe which means this is a problem which is impossible to fix.

I doubt that, in Halo 3 about 90% of my bulltrues were legit, and times where I messed up it was my own fault. There’s no way I was near the host that many times

> > the problem is latency, they can’t fix latency.
> >
> > on the sword users screen, he hit you before he died, on your screen it is the other way around, if 343i were to patch it so the hosts decides then there would be a lot of un-registered hits with the sword and a lot of comaplaining about how there sword is very inconsistent.
>
> Then make sword user host, always! Pick it up and you become host! It would be a fool proof plan, with no sort of bad consequences whatsoever, right?

Sure if you want multiple black screen host migrations in your game because people can’t hold onto their swords.

> You speak the truth. This is an extremely annoying problem. The point of the bulltrue is to award you a medal for essentially saving yourself from the instant death of a sword lunge. I also don’t remember this problem in Halo 2 or 3 so if anyone can elaborate why it happens in Reach, and why it can’t be fixed in Halo 4, I’d be interested to know.

I will say that it wasnt a problem in 3 but it has happened to me twice. And i remember it was twice because my friend did it to me twice in a row while playing on the same console though im sure that was more of a glitch.

> the problem is latency, they can’t fix latency.
>
> on the sword users screen, he hit you before he died, on your screen it is the other way around, if 343i were to patch it so the hosts decides then there would be a lot of un-registered hits with the sword and a lot of comaplaining about how there sword is very inconsistent.

Latency is NOT the problem. This can and should be fixed for Halo 4.

There’s a glitch in the game where, if you start a swing with the ES and your body hits something, it counts as a stab. It doesn’t even matter if you’re dead.

Give it a test. Swing the ES and then interrupt the swing with an Evade into somebody. If your body touches their body they will be “Pummeled” and die.

An inconsistent way to avoid this problem in Halo: Reach is to try to quickly side-step after shooting a swordsman to death. If you’re lucky they will just fall next to you, rather than on you.

Yeah it sucks, hopefully it’s not in H4.