JavaScript is required to use Bungie.net

#feedback

Edited by CarnivalLaw: 9/28/2016 5:48:55 PM
121

I'm doing my job. Now Bungie, you do yours.

I am reporting every single red bar I see in the Crucible. Yes, those on my team, too. Now do your job, Bungie: start banning people who are repeatedly reported for bad connections. I say "repeatedly" because frankly, [i]everybody[/i] red-bars from time to time in this game. But, there are a lot of players who red-bar way too frequently to be allowed to continue to play. Trials is coming. Iron Banner is coming. Clean it up, Bungie. Edit: [b]We are no longer playing in a game world where you can assume that just because you have internet, you can play any online game you like. [/b] Edit: I am not suggesting anything like a permanent ban. Something on the order of a couple of days, allowing the player to sort-out their connection issues. If, however, upon their return, they continue to receive regular bad connection reports, the bans should get longer and longer.
English
#feedback

Posting in language:

 

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

View Entire Topic
  • Edited by MADG33k: 9/29/2016 10:51:55 PM
    Carnival, we often agree on Destiny things but this time we have arrived at a divide. Banning players with red bars really is not a good long term solution to this issue because it is, for the far majority of them, not their fault. The problem is with the way the Internet is designed, which makes it super susceptible to bottleneck issues which can come and go without user intervention and all of which dynamically effect all players ping times (lag). Think of it this way, you can have the fastest car in your drive way, say one that does 200mph (low latency), and you live next to a 10 lane wide freeway (direct ISP connection to the Internet backbone) and you have a private road to the freeway on ramp (wide band ISP connection, unlike most cable connections). One afternoon you need to get to your work (10 miles down the freeway) in 15 minutes. Should be no problem, unless that freeway is I405 in Southern California, where EVERYDAY from 2pm to 7pm that Backbone is jammed full of traffic, so no matter how fast your car is and the fact that you had a private entrance to the freeway or that the freeway is wider than most others in the world, you are not going to go faster than 15 to 20mph. Now you might say that it is the persons fault for living in Southern California next to that freeway, but the truth of the matter is that when it comes to the Internet we are all living next to the 405 freeway. Part of the reason for this is that the Internet is not designed for speed, but data reliability in a network that is designed for ad hoc add on's, which is how it works. This allows the network to work reliably even with huge bottlenecks that come and go. It may not always be fast, but it works reliably. For the application of an online FPS shooter where time and bandwidth is of the essence, the current implementation of the Internet is terrible. This is one of the reasons why people are calling for private servers but in reality we will also need private backbones that run a different protocol than TCP (or UDP) across all the continents to resolve most of these issues (probably 80%, as the bottleneck problems when connecting back through the Internet will still exist). This is why I disagree with banning "red bars", because they really are not consistent and there is often nothing more they can do. Especially since Bungie does not put a priority on latency matching, rather they match games based on skill, regardless of how much there is a spread in latency times to the host server (which to make matters worse is a "peer" server).

    Posting in language:

     

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

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