Since friday I been having Watercress and Newt errors on my xbox one version of the game and has been occurring for a minority of the player base.
I have patiently waited or hoped in a vain attempt that bungie would fix these errors in their new 2.8.0.1 hotfix but they have completely ignored the issue.
You have forced my hand and now I have video evidence that proves that the error does exist and it's only effecting the log in for my xbox one version of the game.
[b]Please find the link to the youtube video[/b]
I am a avid destiny player and my main source of playing the game is my xbox and this error occured hours before trials started. This error hasn't effected any of my friends that I regularly play with.
I have been speaking to other players in the forums and they have a similar issue and also stated they are also experienced Destiny players.
Its safe to assume that since Bungie has ignored or glossed over the issue must mean that Destiny's security has been compromised and we have been locked out so someone can get a advantage on the first week of trials.
The only response I had from bungie is them copy and pasting the Watercress error code page which I found incredibly insulting and completely ignored the issue.
I have spoke to Microsoft aswell and they couldn't help either.
You have ran out of time to make excuses Bungie so for the last time.
[b]FIX YOUR GAME![/b]
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.