# 1 Jan 13, 2015
# 8 Jan 13, 2015Only counts if it's a Death Maiden.
# 15 Jan 13, 201501/13/2015 02:53 PMPosted by KixxSo this gets a response but error 3006 doesn't. Thanks CM.01/13/2015 03:18 PMPosted by SPDCPAWould it be better if that CM stated "Hey, passed it on" in relation to error 3006?
Tyvalir has already done so here. I'd recommend keeping an eye on that thread for more information as it becomes available.
# 16 Jan 13, 201501/13/2015 02:53 PMPosted by KixxSo this gets a response but error 3006 doesn't. Thanks CM.
Just want to point out that the following BlizzTracked post was created about 30 minutes before yours: http://us.battle.net/d3/en/forum/topic/15699375531?page=3#51
Thanks for reporting this, everyone. We're currently investigating this issue.
For now, the best thing to do would be to follow the instructions on this page (which Devander kindly pointed out). If this doesn't solve your problem, please let us know on the Customer Support page or by posting in our Technical Support forum.
From that same thread: http://us.battle.net/d3/en/forum/topic/15699375531?page=8#151
Unfortunately, I don't have any sort of update to offer right now on the issue at hand.
Could I get a few of you to try deleting your Battle.net cache folder and see if it helps? Just a couple will do.
Deleting the Battle.net cache folder
And here: http://us.battle.net/d3/en/forum/topic/15699375531?page=11#206
Hi guys, turns out that at about the same time I made that suggestion, our network engineers think they isolated and resolved the problem. So while it's great that my idea may have worked, I don't really think it solved anything in this case.
If you'd like to follow this discussion, you can do in our Technical Support forum here. Thanks.
Edit: DOUBLE BLUE POST ALL THE WAY ACROSS THE FORUMS. WHAT DOES IT MEAN?