Halo 3: Worst Betrayal Ever

Nothing sucks more than being betrayed by a teammate in any game, but sometimes betrayals are either by accident or of the mysterious kind. The above video is an interesting investigation into one such mysterious betrayals. This particular case looks like a glitch in the game caused the death.

Join the Conversation   

* required field

By submitting a comment here you grant GameFront a perpetual license to reproduce your words and name/web site in attribution. Inappropriate or irrelevant comments will be removed at an admin's discretion.

108 Comments on Halo 3: Worst Betrayal Ever

joe

On March 1, 2008 at 8:48 pm

Lag. He shot before you jumped but due to a lag spike you were able to jump backwards before his bullet hit you, the game picked up on what happened and knew you should have died so it rerouted the bullet to your current position after the lag spike; which happened to be your head. :(

John

On March 1, 2008 at 9:08 pm

Wow.. that was awesome. But like joe said, it was the lag spike.

S.T.A.L.K.E.R.

On March 1, 2008 at 9:10 pm

What Joe said makes sense.

th15

On March 1, 2008 at 9:39 pm

Yea definitely. That’s just how dead reckoning works. He did in fact pull the trigger when his crosshairs where over your head (either on his client or to the server).

Luth3r

On March 1, 2008 at 10:10 pm

Or the sniper bullet hit the grenade, and that caused the ricochet

nolanvoid

On March 1, 2008 at 10:24 pm

back and to the left…. back and to the left… back and to the left.

Ben

On March 1, 2008 at 11:31 pm

I was thinkign the same thing as joe, that it had to be lag, and to make it fair theres probably some failsafe that reroutes the bullet to the person it was aiming it in lag. Theres one like that in a mod for Jedi Knight 2: Jedi Outcast. and the same thing happens

Tallfriend18

On March 1, 2008 at 11:44 pm

I honestly dont think it was lag. It wouldn’t make sense for the angle of the trail. Hell its not even aligned with the barrel, its an inch or two before you reach the tip. Incredibly strange.

Sean McGeezer

On March 1, 2008 at 11:46 pm

THERE WAS ANOTHER SHOOTER

Ifartedonyourpillow

On March 2, 2008 at 12:00 am

YEA I LUV THIS MUSIC LEIK MOAR PLZ

Hydra

On March 2, 2008 at 12:35 am

heh, reminds me of the magic bullet theory

Interesting...

On March 2, 2008 at 1:02 am

I believe it hit the nade the red guy threw. Pause the clip at around 1:45 and watch it through to 1:48 – I think you’ll find the answer there. That’s a hilarious betrayal though!

Azselendor

On March 2, 2008 at 1:45 am

Lag.

I’ve seen something similar with BR’s in laggy games. They guy firing will be aiming one way, the bullets flying somewhere else.

Still, great video.

anonymous

On March 2, 2008 at 2:15 am

It Could be lag from a aim bot

Jim

On March 2, 2008 at 3:47 am

The music from this video is that same HIPPY that they use for ing car commercials.

And the video was boring and made no sense, Halo 3. It’s for s.

That Guy Hiding in The Fruit Loops Bawks

On March 2, 2008 at 4:59 am

Your armor sucks…. :mrgreen:

Chris

On March 2, 2008 at 5:22 am

It was the grenade, its Obvious, Its right infront of him then he shoots it and it bounces off to his head, just lucky…or unlucky :P

@ JIM

On March 2, 2008 at 5:31 am

gg nub.

Nitefox

On March 2, 2008 at 5:44 am

lawless victory.. :mrgreen:

Peter

On March 2, 2008 at 10:05 am

Jim needs to calm the down

Beast

On March 2, 2008 at 11:58 am

I totaly agree with chris. It bounced of the grenade. My friend and I did It on forge on Foundry. We put a box down that was head high, put a grenade on it, turned into a human, turned back into the moniter, deleted the box leaving the grenade floating in air, shot the grenade with a sniper, it bounced pack and put a black, chared hole in my forehead. We did this quite a few times. LOL. :smile:

S.T.A.L.K.E.R.

On March 2, 2008 at 12:06 pm

If you look closely though the grenade isn’t in the right spot, nor does it correspond correctly with the trail of the bullet.

Skunk

On March 2, 2008 at 12:15 pm

Grenade. You can do interesting things with the grenades. You can shoot them, stick them, put them under gravity lifts, etc.

William

On March 2, 2008 at 12:34 pm

I really don’t think it was lag or the grenade. It looks like it somehow shot through a wall..possibly a glitch gap in the game….

Sharky

On March 2, 2008 at 12:58 pm

Those damn magic bullets.
Couldn’t have been the wall, the grenade seems too low, but it could’ve been the culprit.
Most likely lag + nade.

Iku Tri

On March 2, 2008 at 4:14 pm

It was the nade thrown by the red guy.

I paused it and it looks like the grenade exploded because of it.

Iku Tri

On March 2, 2008 at 4:17 pm

Also, the lag could of helped place the grenade/invisible wall…….

Jay Ikutri

On March 2, 2008 at 5:44 pm

i think i saw someone in the grassy nole, maybe it was them

Iku Tri

On March 2, 2008 at 6:15 pm

Saying “@Iku Tri” works best.

But that was funny.

Rix

On March 2, 2008 at 6:25 pm

maybi it bounced off the grenade

sirkit

On March 2, 2008 at 6:33 pm

If you want a real halo3 glitch, that has nothing to do with lag spikes,
Xbox Live GamerTag: DLK ALL DAY
File Share File #4 aka “OV Glitch”
its me..trading a power regen, for an oversheild, in matchmaking, and carrying the overshield like a gravlift/power drain, and when i die it plops out of my dead body and floats in the air until someone grabs it.

greg

On March 2, 2008 at 6:36 pm

it was the instant puff of smoke and possibly a glitch making the smoke into a wall or enough of a barrier to ricochet the bullet look closely the grenade is not even remotely near the bullet so the nade is out. smoke+glitch=headshot!

LHO

On March 2, 2008 at 6:39 pm

grassy nole!

Jesse

On March 2, 2008 at 6:47 pm

The red guy threw a grenade and the sniper bullet bounced off of that grenade causing the betrayal…half way through the video u can see the grenade bounce off the ground and explode behind the 2 blue guys.

Joetr

On March 2, 2008 at 7:01 pm

It wasn’t lag. You can clearly see the deflection off the frag grenade, and the action on the grenade as a result of the impact by the bullet.

Kushan

On March 2, 2008 at 7:05 pm

What I think happened was that the grenade explosion (thrown by the person who got “betrayed”) caused the bullet to ricochet back and hit him in the head. :?:

The lag spike doesn’t explain the smoke trail…

Tony Fendall

On March 2, 2008 at 7:07 pm

I recon the guy must have an aim bot which glitched at that moment and targeted your head rather than the enemy

david

On March 2, 2008 at 7:13 pm

grassy nole! : I second that motion

Will

On March 2, 2008 at 7:13 pm

It’s “Knoll” you ing retards.

Wes

On March 2, 2008 at 7:25 pm

:mad: four minutes of my time, forever fleeting, never to return…. :cry: a moment of silence please for

Nate

On March 2, 2008 at 7:34 pm

It definitely bounced off the grenade. Lag could not have caused it to change angle. It can change the targeted area of the shot but never the angle. What I mean by targeted area is if you say aim at a guys head, then a lag spike occurs, the shot is three feet to the left of where you intended. Obviously the grenade if you look at it horizontally. Whoever made this, my Gamertag is Nato234. If you could send the video to me or put it on your file share, I wanna check it out some more.

Xbox 360

On March 2, 2008 at 7:42 pm

Wow, that’s crazy… you should send this ti Bungie!

Goat Molestor

On March 2, 2008 at 7:46 pm

If any of you have ever thrown a grenade and shot it you would know an active grenade explodes once shot.

Zorse

On March 2, 2008 at 7:48 pm

Kushan is right, I’ve had this happen with a rocket before. I shot it at a guy who had just thrown a grenade and when the rocket was traveling over the grenade the grenade blew up. It turned the rocket 90 degrees to the left and sent it into a wall rather then into the guy I shot it at. This sniper shot just got exploded backwards by the enemy grenade blowing up a the exact right time so it counts as a betrayal rather then a kill for the red guy.

Brian

On March 2, 2008 at 7:57 pm

Watch that grenade. The sniper richochetd off the grenade and hit you in the head. I noticed it right away.

kav

On March 2, 2008 at 8:09 pm

I am going with, the sniper round hit the grenade.

ADSFDS

On March 2, 2008 at 8:18 pm

wow people are making such a big deal out of this. stfu

andy

On March 2, 2008 at 8:25 pm

Maybe it bounced off the second grenage thrown and hit him in the head

Mortician

On March 2, 2008 at 8:28 pm

I think its just a really weird glitch where it thought there was a wall somewhere that there wasn’t.

Evilcannon

On March 2, 2008 at 8:37 pm

Did you not see the red guy throw a nade? Did it bounce off the red guys nade?

MexMen

On March 2, 2008 at 8:41 pm

The sniper’s bullet hit the grenade, and that caused the ricochet. See it, it’s logical.

Peter

On March 2, 2008 at 8:48 pm

No – for all those who believe it ricocheted off the grenade, this is incorrect – it was indeed Lag.

The way modern multiplayer games work is rather complex and rather strange, there are lots of shortcuts to enable seemingly ‘lag-free’ play. Here, as Joe says, the shooter shot the guy through the head fair and square, there was a bit of lag and it took a moment to propagate to the other client – essentially he was dead but due to a touch of lag didn’t know it yet. The strange smoke trail can be explained, because it’s up the local client to draw *almost everything*. Essentially the local client was told – hey you just got shot in the head HERE, from HERE, a second or so after it actually happened, so it had to draw that weird trail even though it looked impossible due to the lag. The rarity of this type of close movement around a shooter, and the level of lag at just the right time, as well as clever tricks that can mask such occurrences means you don’t often see effects as bad as this, but it DOES happen.

For more information, take a look at this Valve doc, as the Source engine works similarly: http://developer.valvesoftware.com/wiki/Lag_Compensation

N.B. I speak with some authority on the matter, being a published researcher (IEEE) in the gaming field (game security).

Devlin

On March 2, 2008 at 9:28 pm

Bounced off the grenade.

fagan

On March 2, 2008 at 9:29 pm

Looks like it bounced back off the grenade to me..

Xatos

On March 2, 2008 at 9:53 pm

Who gives a

Jimmyd4ng3r

On March 2, 2008 at 9:56 pm

There was another sniper on the grassy knoll.

Zack

On March 2, 2008 at 9:56 pm

i know this is weird but what if…the explosion from the grenade changed the bullets flight path and for some reason it was rerouted into the persons head :neutral:

abiku3003

On March 2, 2008 at 10:25 pm

portal!

Lame

On March 2, 2008 at 10:31 pm

I find it more interesting how you managed to spend ~4:00 minutes on what should roughly be a 30 second clip.

ewfg

On March 2, 2008 at 10:34 pm

dude it bounced off the gernade!!!!

Zachary Koeneke

On March 2, 2008 at 10:40 pm

you need to see the clip from your teammate’s client. if you saw what he saw, you’d have your answer.

apena89

On March 2, 2008 at 10:41 pm

it was Colonel Mustard with the wrench in the kitchen.

Ross

On March 2, 2008 at 10:50 pm

Lee Harvey Oswald.

Yonah

On March 2, 2008 at 10:56 pm

Wow, let’s look at the same shot from 42 differnt angles with slow motion and music. You Halo Fanbois never cease to amaze. :shock:

Noah

On March 2, 2008 at 11:28 pm

HAS ANYONE CONSIDERED THE GRASSY KNOLL?!

specialsauce

On March 3, 2008 at 12:05 am

I say it bounced off the granade but if it didn’t then I guess I would say that I don’t really care.

grenade_theory

On March 3, 2008 at 12:41 am

I am seconding the grenade theory. It more than likely bounced off the one you threw.

Jordan

On March 3, 2008 at 12:57 am

I think it’s either the lag, or from the grenade explosion throwing the assault rifle and the shot ricocheted off the AR.

Rick

On March 3, 2008 at 1:05 am

I agree with that guy its a deflection off the grenade.. thats badass

Halo Demigod

On March 3, 2008 at 1:44 am

Its obvious what happens:
Sniper shoots Red guy as he throws a grrenade, Sniper shot deflects off of the grenade, kills ally.
Easy, look harder. It lines up.

JFK

On March 3, 2008 at 2:35 am

It was a second shooter on top of the grassy knolls.

joedaddy587

On March 3, 2008 at 2:40 am

i’m gonna go with the deflection off the grenade theory

roboking

On March 3, 2008 at 4:39 am

LOL. The Grassy knoll. The magic bullet strikes again.

Swifty 76

On March 3, 2008 at 4:46 am

It richochet off the other persons nade. The person on the blue team threw a nade and then right after the person on the red team threw a nade which went infront of the snipers barrel. idiots.

supermario

On March 3, 2008 at 5:27 am

grassy noll shooter…… it happened way back in to the day by some guy that went by the name of JFK or somehting like that never really heard much :roll:

Itaintrite

On March 3, 2008 at 5:30 am

I’m cool with Halo 3. I’m even cool with people who play WoW 24/7. But ffs this is a bug/glitch/spike whatever it is. Nobody gives a .

Now if you were actually betrayed in real life, got shot in the head and is somehow blogging from the beyond, maybe then I’d be interested… or maybe not.. Moving on…

The Mike

On March 3, 2008 at 7:20 am

I can’t believe how many people are trying to analyze this. Its a video game. The “physics” aren’t going to be 100% accurate. Just respawn. What did you expect? You only paid $400+ for your XBox 360 and $60+ for your copy of Halo 3.

“It ricocheted off the grenade!”

“No! It was due to client/server lag!”

Sounds like some of you need to get laid.

q

On March 3, 2008 at 10:35 am

You ever play CS? interp ftw

greg

On March 3, 2008 at 10:45 am

it deff bounced off the assault riffle if you look close

ahimothZer0

On March 3, 2008 at 12:22 pm

Did you check teh grassy knolls?//???/?/?

costalong

On March 3, 2008 at 1:58 pm

I think someone said something about grassy knolls?

John

On March 3, 2008 at 2:32 pm

lag and the video was about 3:30secs too long for something as dumb as that.

James

On March 3, 2008 at 6:33 pm

exact same thing happened to me:
http://www.geevee.com/index.php?p=viewvideolist&u=DTHLRD

blake fife

On March 3, 2008 at 7:37 pm

“You know Einsteins theory, space is curved? These are smart bullets.” – SGT. Bilko But seriously, I hate the Havok physics engine, thats my best guess or something to do with lag.

Zack

On March 3, 2008 at 7:40 pm

people, it couldnt have bounced off the grenade because there would atleast be a trail leading to the grenade. but as you can see, there is only a trail going to the persons head. dont believe me? look at the self kill last stand, there was a trail leading to the bounce point and back

Acadius

On March 3, 2008 at 7:44 pm

I feel your pain but at least it wasn’t done on purpose. I can’t count how many times I have been betrayed by some kid who is just out to piss people off by going against the team. What’s worse is when it is done in ranked matches.

DigitalKlepto

On March 3, 2008 at 9:30 pm

#1 Reason it did not bounce of the grenade: If you shoot a primed grenade it will explode. Try it.

This is caused by lag and latency between you, (the client) and the host, which was most likely the sniper.

I couldn’t find the video, but I have seen a video on Snowbound where a plasma grenade was thrown, missed its target and landed on the ground, then all of the sudden floated across the room and stuck to the faceplate of its original intended target. Some of these glitches are done intentionally, and its all done with bandwidth manipulation, and it is something that Bungie is cracking down on if you read their weekly updates over at http://www.bungie.net, you can see for yourself.

Rob

On March 3, 2008 at 9:34 pm

definitely the grenade ricochet theory.

berky93

On March 3, 2008 at 9:58 pm

it was the grenade – if you pause at 1:54 you can see the grenade is directly in front of the snipers barrel when he fires. The first person (who was killed) threw a grenade, and then the enemy threw one. the sniper hit the enemy’s grenade and it bounced off. it didnt explode because the game programmers never expected a grenade to be shot before it explodes.

Micheal

On March 3, 2008 at 11:51 pm

It was the Grassy Knoll

Calokiddie

On March 3, 2008 at 11:55 pm

Damn, he gots skill.

DTHLRD

On March 4, 2008 at 6:12 pm

it was not a grenade. it was definitely lag. my betrayal was the same and there is no grenade or ricochet – it is Halo connecting the bullet to the headshot, but lag makes it go backwards.
http://www.geevee.com/index.php?p=viewvideolist&u=DTHLRD

shelory

On March 5, 2008 at 4:12 am

it looks like the sniper shot at a grenade that was thrown and his shot ricushade of it and hit you.

Yp

On March 6, 2008 at 11:09 am

could it not have ricochet from the granade the other guy threw… even thought it should have exploded….. that was fun though :?: :!: :twisted:

Veco

On March 6, 2008 at 11:41 am

it defiantly looks like it bounced off the second grenade, the frame rate doesn’t show it right in front of the gun, then again, it doesn’t show it the very second it fired so its more than likely it did. plus it didn’t bounce off the top wall hence it had already done it off something else.

Anybody home

On March 10, 2008 at 2:51 pm

Wow, this video could have been a 1min and gotten the point across, to may effects ->= large video ->= larger file. GG, get the point across in less time and you’ll be just as effective. That or post a linger video somewhere else. Other than that only a couple of things it could have been like everyone else is saying, lagg or nade, or lagg+nade yup anyways you can make some pretty cool pics with some screenshots form this.

paul

On March 11, 2008 at 6:25 pm

any1 know the name of this song or the artist?

gwk

On March 14, 2008 at 11:58 am

who cares

Marc

On March 17, 2008 at 11:24 am

it’s definelty lag.. The strail of the bullet is irrelevant..

mik

On March 20, 2008 at 2:02 pm

would the lag transfer to the video playback though?

Free Xbox 360 Elite

On March 22, 2008 at 2:28 am

I would definitely think its lag. I think it would transfer through the video playback, why wouldn’t it?

max

On March 27, 2008 at 12:26 pm

no way…………that bullet is clear directly to the enemy :!: :!: :!: :!: :!: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?: :?:

max

On March 27, 2008 at 12:27 pm

:evil: :evil: :evil: or something :!: :!: :!: i don’t know :?:

OrochimaruVoldemort

On March 27, 2008 at 2:48 pm

it is obvious, the physics engine outraced the graphics engine. i have seen it happen a few times, but rarely ever a headshot. it would make sense.

Ramification

On April 15, 2008 at 7:39 am

Obvious lag.
All packets go out with timestamps and are assorted by the server.
The server then reroutes them to clients and the clients enforce them from the backlog even if they were out of sync.
It’s the same effect as playing against someone in some game, killing them, then all of a sudden you inccur “ghost damage” and die.
Essentially, they fired before they died but due to latency the packet took time to do the proper routing and get to your client and be processed.

rafeal

On April 24, 2008 at 10:03 pm

it ricocheted on the grenade

Zarphus

On June 17, 2008 at 2:12 pm

this is an instance of clientside vs host-side. due to network latency, your teammate actually shot BEFORE you jumped back, a small lagspike occured, and you were hit. to “rationalize” this event, the client made the bullet on your game show as if travelling from the gun barrel to your head, which he hit just before you jumped out of the way.
chain of events: you get in the way of ally, a small lagspike occurs, he pulls the trigger and accidently headshots you, a moment later, data gets through, and you recieve your headshot of death.
ive seen 2 other occasions of this, the most baffling of which was a video where even on my client a snipers bullet hit the corner of a wall, stopping the bullet, but i still recieved a headshot and died.

http://www.gcmsgmgmaaro.com

On February 16, 2011 at 8:27 am

Hey jeuvs3ta1xa7hmr1rbjb, very interesting post, it really got me thinking. 94p1p3r8fb qci4ire9ni Thank you. p83tdeocis
32iycywy5r