More than likely I was on an adventure because I was grinding to 50 at that time. But I would imagine that we weren't the only ones. Somehow whenever they do a fix for other people it ends up breaking on my end.Originally Posted by Sanii
Anyway you can't even talk to support about this, it's a black project like Area51. Mention it and you'll get ignored. Better be ignored than option B though.
Well last notification I received from BB_MrGrimm was that his manager was working with the dev's in an attempt to resolve this asap. Haven't heard any more at this point.
In a day where people have the option to spend money on this game (and do), it seems a bit ridiculous with such poor service as to not resolve this problem in any kind of timely fashion. In ANY other industry there would have been serious repercussions and compensation for such a blatant flaw in service and product. The fact that this problem has continued for weeks, is blatant negligence, or they have chosen to ignore the problem, and in essence a customer.
I will not spend another penny on this game (although my expenditure is FAR less then most probably), with poor service and support that causes customers (even if he hasn't spent a dime, they are still customers, and deserve service) to in essence have their problem shuffled under the rug. Adventures are a big portion of this game, and not being able to participate is just absurd.
database bugs like this can be extremely difficult and time consuming to fix. it might come down to analyzing a million lines of code, one at a time by hand to see where the issue is springing from. im sure their standard tools of resolving this have failed.
40 days now without being able to play an adventure? What a waste of money if you paid any.
Most businesses keep customers informed, especially when there is a trade descriptions situation developing.
Even if there weren't, keeping customers up-to-date stops them starting petitions and even forum threads.
This really should be given a high priority.
To heck with 'supposed' amount of lines of code are involved.
It needs a fix and communication.
Nothing to look forward to if that is the case but I know they have a starting point on this already through corresondence.
Three adventures? Come on. Anyway the rollback in theory took as backwards to a safe time. I can't believe its been so long and nothing has happened. Sure I did admin work and we got busy, but when you know its over your pay grade you kick it upstairs. Reminds me I had to take over a case one time, the remote office couldnt do backups which is deadly and the guy had been messing around with it for over a month. imagine over a month with no backups. when i talked to him he had no idea and was bumbling around not really testing anything but he didnt want to give it up. it was actualy kind of hard to find the problem but i sent bi weekly updates to the manager until i got it fixed. Turned out some of her firmware was out of date. Why it suddenly started causing a problem i nejver did figure out but after i got it upgraded she could do her backups. Anyway there is no shame in having to kick things up a level, but you gotta do it.
Having worked in multiple fields of customer service, taking this long to respond is unacceptable. I remember OceanHawk (I think that was his name) was unable to chat without having to connect his PC through a vpn to another pc and logging in from there or some other such complication and ultimately, i believe, he simply quit because all BB kept doing was giving him gems for his "trouble". You can't just keep throwing gems at a problem and hope it goes away. And while i'd like to think some sort of resolution comes out of this, being "isolated incidents", while troubling, they're probably on the backburner of some dev's desk.
i hope it gets fixed soon though. gotta suck to not be able to run advs
Well it's official the longest non-resolved issue I've ever had, 46 days.
Amen Sanii, no idea how or why, but last nights update has seemed to resolve the issue. *crosses fingers*
Posting Permissions
Reply With Quote