This seems very strange.
https://www.reddit.com/r/DestinyTheGame/comments/2wfigr/watch_out_for_a_new_gamebreaking_pvp_exploitmedia/

Little flying Heavy synths. :P

Most of my concerns come down to how Bungie has chosen to handle latency in general. I personally feel that matchmaking should be using latency as its first priority in selecting players. But maybe that isn't necessarily feasible, or isn't the priority they've chosen.

What do you mean by "selecting players" ? Matchmaking or like selecting host? Speaking of host... does Destiny ever perform host migrations? I remember in Halo when the host migration happened, the game would pause and go back to a team screen while respawning everyone into the "new match" ... does Destiny handle this seamlessly in the background? I guess I've never really noticed "down time". Maybe those times when you're dead and the countdown has expired, but you don't respawn no matter how many times you mash X are actually the middle of a host migration.

Destiny does do mid-match host migrations, but it is much more seamless then Halo ever was. This is how the infamous "Get Crota stuck taking a knee" glitch was performed. While the migration was happening, the game locally simulates some aspects of the game, and freezes others, until migration is complete. At least, that was my experience.

What do you mean by "selecting players" ? Matchmaking or like selecting host? Speaking of host... does Destiny ever perform host migrations? I remember in Halo when the host migration happened, the game would pause and go back to a team screen while respawning everyone into the "new match" ... does Destiny handle this seamlessly in the background? I guess I've never really noticed "down time". Maybe those times when you're dead and the countdown has expired, but you don't respawn no matter how many times you mash X are actually the middle of a host migration.

Not to change the subject...but this could explain that respawn glitch. Maybe it's not a glitch after all.

Most of my concerns come down to how Bungie has chosen to handle latency in general. I personally feel that matchmaking should be using latency as its first priority in selecting players. But maybe that isn't necessarily feasible, or isn't the priority they've chosen.

What do you mean by "selecting players" ? Matchmaking or like selecting host? Speaking of host... does Destiny ever perform host migrations? I remember in Halo when the host migration happened, the game would pause and go back to a team screen while respawning everyone into the "new match" ... does Destiny handle this seamlessly in the background? I guess I've never really noticed "down time". Maybe those times when you're dead and the countdown has expired, but you don't respawn no matter how many times you mash X are actually the middle of a host migration.

I don't know, but I guess I'd like to learn more about all of this stuff. What kind of criteria the game uses for matching players, choosing host, and whether the host migrates mid-match based on connection speeds or only if the host drops out. I imagine lag switches could wreak havoc if host doesn't migrate based on connection if you already have host advantage and then start injecting lag.

We're a bit stumped by "lag abuse"... What are people doing?

If it's intentional, it's probably a lag switch. But, there's always the chance that the Destiny netcode is just bad and people aren't doing this intentionally. Who knows

I prefer to think it isn't usually intentional.

Most of my concerns come down to how Bungie has chosen to handle latency in general. I personally feel that matchmaking should be using latency as its first priority in selecting players. But maybe that isn't necessarily feasible, or isn't the priority they've chosen.

I don't mind winning, but I'm pretty sure the losers in those matches (20k to 4k, seriously) are as upset with the matchmaking algorithms as I am in general.

My team generally only loses when we face either another coordinated team, or a group of laggers. I always worry that in those other ganes, the ones where we have complete map control and dominate the other team, that to them we're the laggy team of pseudo-cheats.

We're a bit stumped by "lag abuse"... What are people doing?

If it's intentional, it's probably a lag switch. But, there's always the chance that the Destiny netcode is just bad and people aren't doing this intentionally. Who knows

Also, I killed a guy at least once in a match (and others in my party claim to have as well) and he got a mark of the unbroken. But I saw him die! The feed showed I killed him! Somehow the final results didn't care.

My personal guess is that someone has cracked the game and released a cheat out into the wild.

--

After getting my ass handed to me for about 10 games, we went on a similar tear, this time in the win column. One game I had a 16.0 K/D ratio. On my level 28 Titan. So there was certainly something wonky going on in matchmaking as well. I don't mind winning, but I'm pretty sure the losers in those matches (20k to 4k, seriously) are as upset with the matchmaking algorithms as I am in general.

--

Also, there's the standard lagging guys who teleport around, shoot you around corners, don't take damage when you shoot them etc.

He never asked for this.