JavaScript is required to use Bungie.net

#feedback

Edited by Utsuro Bune: 6/8/2015 3:27:12 PM
27

Trials of Osiris: "Losing" for time-out

Really, Bungie? In your desperation to make a PvP game mode where people won't cheat to win a simple prize, you've made one huge mistake, and that's losing *NO MATTER WHAT* if you leave the game. I have flawless Internet, but the fact that a fraction of a second loss of connection boots me out of a game and makes me take a loss when I have literally two wins left until I reach Lighthouse, is stupidly unfair. it's just unfair and thoughtless for you to overlook players that actually DO have connection problems just to keep cheaters from trying to get away from the loss. Seriously? No one is being attacked with leaving the game Bungie. So why make it this way? It's a win win situation. A person leaves without a loss and the other team wins. This is a problem, and it is cheating to get out of a loss, but not big enough for you to unfairly punish bad connection players for this. Please patch this now. [i]EDIT:[/i] Also, note that mercy DOES NOT prevent a counted loss on a passage coin if you time out. This is another flaw with this system which further values my point.

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 twey_ironside: 6/9/2015 7:54:15 AM
    We had got booted after 4-0 while about 2 win the 5th game. We all had the Mercy active. Me and another of our fireteam got a loss while the 3rd person got it coutned as a victory. I think it should just be counted as neutral. So no win or loss. I think its is hard to differentiate between a wanted or an unwanted disconnect. Its disheartening though if you have to start over becase the serves cant hold up. My internet is fine as well.

    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