JavaScript is required to use Bungie.net

Помощь

Помогите нам помочь вам.
Изменено (k33puh): 5/19/2018 2:40:52 AM
4

Error Code: Guitar loading into final flawless match

Our fireteam received error code: guitar while loading into our final match of our 6-0 ticket. This counted as a loss for us and after spending over an hour and a half patiently playing, sweating our way to the top, Bungie issued our team error code: guitar while zoning into the match. This was utterly unfair and disheartening—our objective was to play against our last set of opponents but we were literally cheated out of our ticket for non-legitimate reasons. Why would I want to continue to put so much effort into something that could literally just be ripped from my reach? It would fine if this was a legitimate team; however it wasn't. We were cheated by Bungie. Researching error code guitar says that these network errors are automatically reported and tracked. The ticket occurred between 9-9:45 EST and consisted of Koopacabra#1888, Godly#11160, Evan#13482 and Waterkitten#11477. Please fix this by registering our ticket as a win and providing us with the flawless loot options. Thank you for looking into the matter and working on behalf of your customers. Sincerely, Koopacabra

Публикуется на языке:

 

Играйте достойно. Потратьте минутку на ознакомление с нашими правилами, прежде чем отправлять вашу запись. Отмена Изменить Создать боевую группу Опубликовать

Смотреть всю тему
  • @Project Atom - first of all, there's no need for you to be so aggressive without properly discussing this issue with me. You're out of line for making such statements. Second, I understand the point that Mister Exotic made last night regarding Bungie's history to not act on issues like these. This is my first time posting on the forums yet I understand the uphill battle this could be to bring the issue to light. To be clear, there were no apparent network issues nor were we disconnected from Destiny 2. We were not taken back to the start screen before character selection, ergo, nobody in our fireteam was disconnected. We were simply given the error and then returned to orbit, still together as a fireteam. Therefore I believe this issue could be investigated further on behalf of Bungie as to why they discounted our flawless card with a loss when they failed to initialize our next and final match. They could have simply returned us to orbit without marking us for a loss, if anything. If they know they're having stability issues with their servers (this has been a known fact for years, since Destiny 1, due to their complex server setup), then automatically defaulting to a loss for any immediate disconnect is poor policy and design. The issue we experienced was beyond our control and was a result of Bungie's failure to initialize the match. This is how you have constructive debates about topics. Please, in the future, avoid undeserved personal attacks of character without properly discussing said topics. Thank you Bungie for skimming the forums and looking into this further.

    Публикуется на языке:

     

    Играйте достойно. Потратьте минутку на ознакомление с нашими правилами, прежде чем отправлять вашу запись. Отмена Изменить Создать боевую группу Опубликовать

У вас нет прав для просмотра этих материалов.
;
preload icon
preload icon
preload icon