Post Compromised Account Issues someone please help!

[Raist]

Looks like there may be some hope at least. Remember what Orlando told you to do:

Agent Orlando: You can bump your bug report in the forums and let them know it hasnt been resolved and specify that it is from GDR

Something specific like that is often some gimmick that may help escalate the ticket. Worth a try, especially since support is instructing you specifically to do so.

[Madoxone]

Raist, I want to thank you for all your advice, I really appreciate it! During all of my interactions with SE, including my original bug post two months ago, I have made sure to specify at every step that I was acting on instructions from a GDR. Below are the reasons (based on my I.T. experience) why submitting a bug reports won’t resolve my problem and why Support has continually suggested it.
1. Once a bug report is accepted it is also locked, so you can’t edit, comment or (as far as I know) bump it.
2. Bug reports come with this disclaimer "Please note that we are unable to provide individual responses to reports."
3. The reason for this disclaimer is because usually they are only looking for pervasive and/or program breaking issues. A user is only contacted to get more info after which the forum team then documents how to recreate it and passes the report along a different team that (possibly) created a fix. (The user experiencing the problem is rarely included in the documentation)
4. Finally this isn’t a bug, it’s the consequence of the restore team’s error. My guess is that these issues are the result of a database coherence problem brought about when they restored stale data (over a year old) to the item database while the database that keeps track of my quest progression was kept current.
5. If you were to view this as bug, the fix would be to write/test/validate a script that would look for database coherence issues and fix them. The dev’s won’t spend time writing something like this when a much simpler fix is to do a (correct) restore.
6. Finally the tech support guys are evaluated mainly on the number of tickets they can successfully close and how quickly they can do it. So they try to immediately find out the problem, offer a fix (so they have documentation of the resolution) and quickly get you off the phone so that they can close the ticket. They want as many resolved tickets possible, followed by closed tickets and try to avoid at all costs unresolved/open tickets. When they realize they aren’t able to fix my issue, they offer suggestions that look like resolutions and quickly get me off the phone, to common examples are contacting a GM or directing me to create a post in bug forum . This is why it’s sometimes better for the support guys to give out the wrong answer rather than risk hurting their numbers by trying to track down someone who might actually be able help.
Regardless, your suggestion to contact chat support was a very good one. I was able to save the chat conversation which I posted along with my problem and support frustrations to the General Discussion Forum. It quickly racked up a lot of supportive comments and was locked by a mod who stated: “Thanks you for bringing this concern to our attention. I have made sure to escalate this for further investigation to see if we are able to correct the compromised account restoration. Since further discussion about this topic is not needed, I will be locking the thread.

LGM Enkrateia”

While I am cautiously optimistic, this is still the best response I have received since this issues began three months ago! Thanks again!

[Raist]

sweet. hope it works out for you.

I remember back when I worked with an IBM/Microsoft firm (I know.. strange bedfellows--Linux, Java, and Winblows under the same roof....I lost a LOT of sleep) how frustrating it would be when things would go awry in a database. More often then not, me and the project manager would just manually edit the darn things through a SQL interface or get one of the AS400 guys to pull up file/field and we'd tell them what to change directly.

SE would probably birth a cow if they saw someone using such brute force on their databases. But hey... sometimes it's just faster to type that credit card info directly into the @#$@#$ fields than trying to script the d@mn thing. I understand why they wouldn't want the GM's to just go in there and set flags like that....but it sure would be nice if they would give them the power to do so.

Hang in there... and good luck!