i honestly think if your trying to speed through a strike bc you need to, you should do it by yourself. Matchmaking is for matching players to [i]play[/i] a given strike and leaving enemies behind for your teammates is straight up whack no matter which way you look at it.
you save no time bc you give enemies more of a chance to scatter so you have to chase them all down not to mention everyone should know bad guys die faster when more than one person shoots at them. maybe you cut off twenty seconds but in the longrun if the whole fireteam isnt skipping parts, it ends up taking longer.
every single tiger strike ive played has had one scrub run ahead and its annoying. im saying it now, in two weeks time the players that run ahead will [u]not[/u] be revived by the players actually killing the enemies. i expect runners to not revive the slow and steady; and i foresee much dancing upon the ghosts of the dead guardians.
why should i have to skip out on possible engrams because some egohead thinks hes "too good for killing these bad guys" [i]i shouldnt[/i] and i wont.
to put it in a nutshell: why play coop if your going to play apathetically toward your fellow teammates? its simply the obligation of the speeders to play strikes by themselves.
Your role as a moderator enables you immediately ban this user from messaging (bypassing the report queue) if you select a punishment.
7 Day Ban
7 Day Ban
30 Day Ban
Permanent Ban
This site uses cookies to provide you with the best possible user experience. By clicking 'Accept', you agree to the policies documented at Cookie Policy and Privacy Policy.
Accept
This site uses cookies to provide you with the best possible user experience. By continuing to use this site, you agree to the policies documented at Cookie Policy and Privacy Policy.
close
Our policies have recently changed. By clicking 'Accept', you agree to the updated policies documented at Cookie Policy and Privacy Policy.
Accept
Our policies have recently changed. By continuing to use this site, you agree to the updated policies documented at Cookie Policy and Privacy Policy.