Carthington wrote:
I mean no disrespect Fyre.....but.....
In all honesty, this is not fixing the issues and passing the buck just doesn't do it for us.
You misunderstand. I'm not implying that I'm above testing, I'm telling you that I do not have time to test every bug report given to me by players. If someone gives me a bug and I cannot reproduce it the very first try, I've just lost time that could be used creating new items or fixing a better-documented bug. It's a service outside of my job description that I check the forum for issues and attempt to respond to them directly. If you wish to continue receiving this type of support, you'll have to put up with my requests for more information ;P If not, you can always make use of our ingame bug feature, which will filter the bugs through QA (who sends me detailed reproduction steps).
Acctic wrote:
4 direct examples, present on page 1 of this thread and written many weeks ago. Its a little frustrating to be hearing from you now, what huh..theres a problem?
The examples on page 1 were cited multiple hotfixes ago, before this issue was supposedly resolved. Every example given after my response to this thread used vague references or incorrect effect names, hence my request for further information on what was
still not working. Nowhere in my posts did I imply surprise that there was a problem. Just that I'd already submitted a fix and was not sure why it hadn't gone live.
For those that have not followed this issue since the beginning, this is not a problem with the effects themselves, and all of them work properly on local server (which is why I have to rely entirely on your info about what is not working). I fixed them about a month back, but due to an error during the transfer to live, only about half of the data made it. This caused a slew of additional problems, which I've been trying to iron out when I have time (which I don't). There's nothing here for me to "fix", all I can do is resubmit the info and have it pushed again, but I have to know specifically what to push since (again) it's all working on my end.
LINK