Adjustment is needed in several areas for the late spawn / quit matches. No blanket response on either side of the point is correct. ** If there's Aimbot(s). IRL example: 2 from same clan end up going combined 92-0., and very unnaturally. After the first 3 minutes of experience I spend my time in-game reporting then leave. Not my problem. Actually got a Bungie "thank you" for it recently. Nobody can knock for the quit. There's no contest to be found = no purpose in the match. Of course, you could still land a 5min suspension for leaving.......but 5 min isn't the issue. It's the fact that the penalty exists unchecked & might lead to other action down the line. I believe the real answer to the problem most of the time is: Penalize the initial match quitters, not the ones that are joined late and leave because of circumstance they didn't create.....BUT NOT carte blanche. It should come with limitation..... .....there should also be cutoffs for points deficit and/or match time remaining. What's fair? 50 point deficit? 3 minutes left on the match clock? There's such a thing as fairness to the team who just got screwed by the quitter.....but within doable parameters. And what about back filling / pro-rating your Super / special ammo? Not doing so tilts toward a loss and tilts toward an additional quit.....because there's no equity in it. Just a "you can't quit without penalty" stamp - which is hogwash. I'm just looking for reasonable. The throw away matches are ridiculous. There's no contest to be found in them either. Night before last I left just one match....it spawned me in on the short side of 7 - 59. That's a throw away. I didn't check the game clock. If it's a 30+ deficit close to the 150 cap as you join and get spawn killed via Super during the near end of match Supers barrage exchange.....with no super of your own to counter with. That's a throw away.. You're not going to be in-game long enough to swing momentum. __________________ When you're on a roll you will be paired as defacto "sherpa" for a team with lesser mathematically probable chance of winning. Understanding and accepting this, I stay in all fresh matches I'm paired into regardless of how it unfolds. I get tons of these. As a sidebar I can say that a decent amount of the newer and returning players are starting to perform much better, which is awesome. For in progress joins.....If the point deficit is ballpark 30 or so with around half the clock +/- left, you have opportunity and It's a fun challenge. Turning those into a win or making them close is very satisfying. .....Same goes for the 4v6 or 4v4 to start matches. Interesting challenge. Never know what you're gonna get, and I'm not opposed. NOW is the time to post about in-game issues. Bungie's suggestiion box is wide open.

"stop killing your game" Stop backing out of yours.......

Competitive isn't even competitive. You get suspended for bungie's poor decisions lol.

At this point, ppl are leaving too much. It's reasonable. If you're gonna leave, don't load in. If you're gonna leave anyway, you won't be allowed to load in.

Yeah join a match in progress, see your team losing or winning, but later on, your team does absolutely dogshit for some odd unknown reasons. And lose big time. After match, the game would tell you it would break up team for better matchmaking. I mean, I do hate that when it happens like 3 times in a row, if I'm facing a 5 stack with a lucky noob player. Why cant it be me with the 5 stack? XD matchmaking is kinda working against me and not with me. So mostly I try to stay away from PVP but mainly to get that Crucible weekly bounty thing out of the way since doing Crucible is faster than Vanguard for me. Unless I saved the previous 4 bounties from last week.

[quote]Bungie are you serious? You're killing PvP with this nonsense suspension on Control. Matching is utterly rubbish. You can't force people joining games in a row in progress and expect people staying. Control isn't competitive, stop Killing your game.[/quote] They killed it the minute they started handing out special ammo like it was -blam!- again