We are noticing players reporting the MONKEY error after taking the 1.0.2.3 patch. If you are seeing the MONKEY error code, we would like your help investigating the potential cause of this issue. Please hit the "Comment" button below and provide us with the following information:
Gamertag:
Console:
When you receive the error:
Thank you for your patience and assistance.
NOTE: Please only post the above information. This helps us more rapidly investigate.
[b]UPDATE 3:20pm PDT 3/17:[/b] We are actively investigating the increase in MONKEY errors.
[b]UPDATE 3:30PM PDT 10/28[/b]: We are still actively investigating the MONKEY error players are encountering.
[b]UPDATE 6:45PM PDT 10/28[/b]: We are seeing the number of MONKEY errors subside. Thank you for your patience!
[b]UPDATE 11:40 AM PDT 10/29[/b]: We pushed an update last night that significantly reduced the number of MONKEY errors users were seeing. We will continue to investigate as the hit rate for this error continues to decline.
English
#Help
-
Edited by db0ssman: 10/28/2014 11:51:39 PMGamertag: db0ssman-_- Console: ps3 When I received the error: Soon as I signed on to Destiny starting at about 5pm EST I received a monkey error code every 5 minutes or so, causing me to be booted from doing the daily. At its worse I received one every 2 to 3 minutes while attempting the raid and eventually I had to stop playing the raid because I was just logging on, waiting to be revived and then getting kicked off again. By ~6:15 I was only getting booted every 10 to 15 minutes and thought it might be stable enough to try the weekly heroic strike. The last boot kicked me from the weekly strike right before my team won ~7:15 EST. Side Note: I actually got off work early enough today that I had a shot of doing the raid for once, and I couldn't because of these issues. Needless to say I'm not very happy with Destiny right now, I just wasted 2 hours trying to play a game that previously had no issues for me.