Today we need to go over something important. It's so important I'm devoting a whole DN post about it because it needs to be covered. How to report a bug.
First off. Clear your Browser Cache! Flash uses a caching system. That means your computer saves old info so it loads things faster. If we rolled a fix to a bug and your cache still has the old info you WILL NOT get the fix! You should try and clear your cache at least once a month, but if you're reporting a bug clear your cache first, THEN try to get the bug to happen again. If it doesn't that means we most likely fixed it. If it does still happen then yes you should report it. To figure out how to clear the cache of the browser you're using a quick google search will show you how!
Now, if you've cleared your cache and the bug is still happening that's when you should report it.
That link is at the very bottom of the game window, just scroll down a little bit. It's in both the normal game window AND the DA only server so you just have to look. That's the first step if you find a bug. Click that link.
Once you do that, select DragonFable from the drop down list and then hit the "Go" button.
Now you need to pick your issue from the list. Try and pick one that's close but if you can't find one that is pick "Gameplay Issues".
Now, in the email box put a WORKING email. One that you actually check. If we can't replicate the bug or need more info that is how one of us will contact you. If you put an email that you never check then your bug may never get fixed.
In the Description box please don't try and describe the whole bug. If it's an issue with a specific item say the item and the issue. For example, if I'm have trouble with the "Super Fancy Sword of Wonder" not activating its special, I'd put "Super Fancy Sword of Wonder special not activating" in the box. You aren't done though!
Username: <---- Put your account username or character ID here. We need one of those to check the character itself. Class: <---- If it's a problem with a specific Class put the class name here. Even if it's NOT, still put what class you were in. Level: <----- This is your character's level. M or F: <------- This is the gender of the character you picked. Items equipped: <---- Include EVERYTHING that you have equipped! This includes your class (Yes I want it twice), ALL accessories including trinkets, any Artifacts you have equipped, temp food items you used at the time, what guests or pets you were using, and anything else at all no matter how small that is equipped on your character.
If you see a section called "Server" that is where you can put "Normal" or "DA Server".
This next part is where you get to go REALLY in depth.
-Before Bug occurred: <---- What were you doing before the bug? Did you just log in? Did you finish a quest? Did you buy an item? What did you do before it happened. If something is causing an issue it may be related to what you did before the bug happened so please put everything.
-During Bug: <---- What happened during the bug? How did the bug affect your character. Give as much detail and make sure you are as clear as possible. "DoT didn't go off" isn't clear enough. Go into detail. Give us as much info as you can so we don't have to guess! Guessing is BAD. Don't make us guess!
-After Bug: Did the bug go away? Did it happen again? Did you try and repeat it and it was still there?
Once you hit submit, that's it! We will get the report, and yes we do read them all, but it may not be fixed immediatly especially if it's not reported properly. I usually try and get as many bug fixes done on Monday's as possible so if you report something over the weekend don't expect it to be fixed that same day. (I like having time off to you know) Niki is very good at making sure Verly and I are aware of any big bugs that need fixes as soon as they get reported so if it's something bad it will get fixed asap.
Some of you may also be asking, "why is Ashendal telling us this?" The answer to that is we've been getting a lot of bug reports that aren't done the right way. Sending me a game breaking bug over something like Twitter or my e-mail is fine, but everything else needs to go into the bug tracker and reported properly. Also quite a few people have been putting one line in the description box, hitting submit, and expecting it to be fixed. We can't fix a bug when all we're told is, "the quest I was on is broken!". The game doesn't record the quest you were on or anything about what was going on when you click the report a bug link, YOU have to put that in the box.
We do our best to fix as many bugs with the game as we can, but we can't do that if you all don't report them and do so in a way that helps us do that! If you follow the steps mentioned above there shouldn't be any issues with future bug reports! Just make sure you're checking your email once a week!
San Robin has written a new quest for us this week! Log in now and head to the Book 3 Falconreach weapon shop to help Lim with the newest problem in his basement...
Dracelix has made some gorgeous new weapons as drops for the release!
Ashendal has gotten the Fire Soul weapon rewards live in the burnt house in Swordhaven for those of you that have finished the Alexander quest line. There is also new artwork for the Destiny upgrades that also went live this week! Dracelix has created shiny and bright new art for them!
I would like to let you know that the end of Espina Rosa will not come this week and that instead it will be due for another week (not next week). I know we said in the last DNs we were going to do it this week however between Tomix not feeling too well and my mild burnout from my Terran analog’s new job, we decided best to postpone it to the next available date. There will be a light release this week instead (make sure to wish Tomix well!).
In the mean time, I will make sure to brush up on the script as much as possible. After all, you will not be able to leave Espina Rosa without facing the final boss of the Fortress.
When that comes, I hope you are ready for a difficult battle, Hero.
San Robin has a short quest for us for Friday and the Espina Rosa finale will be coming in a couple weeks!
Hey guys! I've been working on AE's mobile games for the past few years but THIS FRIDAY I'm returning to AQW for a special guest release that I designed. Close your eyes and picture this...
OK, you can't read with your eyes closed. I see the problem.
Change of plan... keep reading but picture yourself with your eyes closed picturing this: The village of Deadmoor has been a ghost town for as long as anyone can remember. Some really bad stuff went down here and we're a few hundred years late to the party but it's never too late to try and right the wrongs of the past. I made friends with the ghost of a little girl who died here. Her voice was stolen when she was brutally murdered by the townspeople. If you can help me return her stolen screams, then I'll give you the chance to earn my own personal, Mad Weaponsmith armor and my super hammer! There will also be a bunch of other rewards if you're not a fan of green, but you look like a player with some taste... so you like green.
Getting off topic... Come to Deadmoor, help me help her. Learn the secrets of Deadmoor's terrible past and you'll get to learn a little bit more about me too (if you're interested. It's optional). The adventure in Deadmoor starts THIS FRIDAY in AQW! Don't let me down.
Greetings! Just wanted to give you all a heads up on a couple of things.
First off, I've just updated the Exp Curve for Exp Needed to Next Level for 60-80. This means that it won't take as long to level up anymore at the higher levels. It'll still take a while, but this should hopefully make it less of a pain to do so. No, this does not mean the Level Cap is going up any time soon. I just wanted to make it less of a hassle as many of you were complaining it took far too long, and those complaints were justified.
Many of you were also expecting a curse after the loss of the last war. There was an issue getting it in place. The short version is the curse coding itself works, along with the temp item to remove it per login, and the coding to make it scale based on your level. However the coding to actually SHOW when it's working doesn't because of how the game was originally designed. Due to that I decided to not turn it on at all. While I could have turned it on at any point, it was not fair to do if you didn't KNOW it was happening. That, combined with the reaction to the other event that occured during the war (which honestly drew a lot bigger of a response than any of us thought...because for some reason the bread lady with no previous character development AT ALL was important to a lot of you), meant that it wasn't something I felt should happen. If it could have been made to work we would have, but I didn't want to release something that only worked halfway. We'll come up with something else for later wars and I'll keep working on other possible ways to show that things are affecting your character.