JavaScript is required to use Bungie.net

Forums

Edited by chickengoujohn93: 7/4/2016 7:43:52 PM
4
I think red barring is being taken completely out of proportions and is being used as scapegoat for every death encountered in PvP instead of accepting it. Everyone in the match could be green bar and people will still blame lag. I've Raided with Red Bars and played PvP against Red Bars and everything works fine for the most part. I have witnessed first hand of being a Red Bar playing Destiny at my friends house and it appears to be a major hindrance for the offender as nothing registered for him and still got killed with ease. On my own internet I've been blamed for Lag before. I was absolutely destroying this one guy in Rumble and everyone was green bar. I got the customary hate message and lag was the topic. I obviously remembered this guy because he accounted for nearly 70% of my kills in the match so how could I not forget some of the encounters? The muppet missed the majority of his shots because I strafe and I seen them whizz past me including one of his Rocket Launcher shots without the G&H's perk which hit a wall behind me taking a tiny proportion of my shield as I was just outside the fatal blast radius. Any reason to not admit that they were completely outclassed in a particular instance. Also, there is too much word of mouth from the so called Destiny Youtubers and everyone hops on the bandwagon. They brand pretty much every Red Bar as those unkillable guys who snipe you through 16 walls from one point of the map to the other from your perspective. The uproar over skill based matchmaking was never about the lag and the red bars. It was used as sugarcoating in an attempt to protect precious K/Ds from the possibility of playing against people of a similar level/skill on a regular basis. For example, how would nKuch perform against another nKuch?
English

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • And to your point, it may be the scapegoat of the community, but it is nearly impossible to find full green throughout. There are red bars littered throughout trials. And especially once you hit 5 wins. So I find it to be a valid excuse and something that absolutely needs to be corrected to keep up the competitive balance.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • I completely disagree with this. I lose 90% of rds where someone has a red bar. I started keeping track out of curiosity and it is a major factor. For example, just yesterday, we played the same team twice in a row. They had significantly lower elo and k/d as a team. First game they had a red bar until they were up 3-0. Dude went green and we won 5-4. Next game against the same team another teammate went red after we were up 2-0. He stayed red and we lost 3-5. So, in just one example, small sample size I know, but my team went 1-8 against the red and 7-1 against the green. The idea that lag has no serious consequence on the outcome of matches is absurd. I am sure if it is exaggerated in the community out of frustration at times, but being just a fraction of a second behind someone can be the difference between life and death, win or loss, flawless or frustration.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Well put!

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Agreed, most red bars don't seem to cause much of an issue, rarely u get one that plays about, had one lastnight not showing up on the map and disappearing but on the whole it seems pretty rare

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon