I played in beta, I lasted a couple months live. However the fact they added stuff without touching things that were broken turned me off rather quick at the second month. I return, about one year later.
Heals can still be deflected
Mobs can still move while charging skills
Latency and rubberbanding issues during peak hours.
Graphical errors showing both the attack and mob, ususally bosses, facing one direction while the actual damage happens in another.
Pets/Companions playing suicide by running right to the edge of a dropoff and pretending to be a lemming.
I see how they keep adding more and more new stuff, which adds whole new bugs on top of the old ones.
(Move over gramps, you do rubberbands. Hah! I'll turn his computer Off!) <-- happened twice
The fights are frustrating. Larger mobs are attacked before smaller. Even if the larger one is across the screen and behind you. Color me surprised when I spun around to shoot the dragon instead of the priest tossing nukes at me.
Adding new stuff is well and good but what happens when a new bug and an old bug you didn't bother to fix join teams and utterly wreck the machines of your playerbase.
There are bugs, for sure (like the door getting stuck in CN if two people try to open it forcing you to quit the dungeon), but I haven't seen these at all.
My Harem: Dawn HR, Erin CW, Piper TR, Zoe GWF
0
areefursonMember, Neverwinter Beta UsersPosts: 7Arc User
edited March 2014
Well now you know what to watch for you may notice them.
Beyond the usual note to keep your feedback constructive...
Bugs are fixed in the priority set down by the QA team. What that means is that bug reports are looked over by the QA team and sorted in order of priority. That does not mean they are fixed in the order they receive them.
For instance, a minor graphical bug may be of importance to a given player but of low priority in general. Likewise, a bug that the players may not think much of may be given a higher importance due to factors not known to the general populace (and no, contrary to popular belief, it is NOT how much the given issue will affect ZEN sales--financial and marketing information usually isn't even known to the QA department).
Also, first rule of debugging: If you can't find the cause, you can't devise the fix. Anyone who's done any sort of programming knows this, especially when you have to sift through thousands--if not millions--of lines of code to find the ONE misplaced variable or string that's causing the problem.
This, furthermore, gets pushed around by incoming content--after all, that has to be debugged as well. Bottom line is that simply because a bug has been around for a while doesn't mean it has been ignored--it simply means that there are higher priority issues. The QA team doesn't have infinite time to work on everything, thus, everything must be prioritized, and prioritizing is a constant process.
ROLL TIDE ROLL
Great Weapon Fighter: Because when is today not a good day to die?
PC and PS4 player. Proud Guildmaster for PS4 Team Fencebane. Rank 5 Officer for PC Team Fencebane. Visit us at http://fencebane.shivtr.com
0
areefursonMember, Neverwinter Beta UsersPosts: 7Arc User
edited March 2014
Thank you for the reply.
I do usually try to be constructive but after doing a flame dungeon with giants that follow after you while charging up thier self targetting AoE until your stamina is dry and you can't dodge kinda got me steamed. So manners kinda get tossed out the window at that point.
Beyond the usual note to keep your feedback constructive...
Bugs are fixed in the priority set down by the QA team. What that means is that bug reports are looked over by the QA team and sorted in order of priority. That does not mean they are fixed in the order they receive them.
For instance, a minor graphical bug may be of importance to a given player but of low priority in general. Likewise, a bug that the players may not think much of may be given a higher importance due to factors not known to the general populace (and no, contrary to popular belief, it is NOT how much the given issue will affect ZEN sales--financial and marketing information usually isn't even known to the QA department).
Also, first rule of debugging: If you can't find the cause, you can't devise the fix. Anyone who's done any sort of programming knows this, especially when you have to sift through thousands--if not millions--of lines of code to find the ONE misplaced variable or string that's causing the problem.
This, furthermore, gets pushed around by incoming content--after all, that has to be debugged as well. Bottom line is that simply because a bug has been around for a while doesn't mean it has been ignored--it simply means that there are higher priority issues. The QA team doesn't have infinite time to work on everything, thus, everything must be prioritized, and prioritizing is a constant process.
Would've thought being unable to progress in CN/VT and the MC shadow log for amd cards would be high priority. Guess not...
This bug/problem can definitely be a hassle for the poor CW trying to dust adds off the healer (or themselves) whilst the tank is busy keeping the boss occupied. (Possibly also for a HR, but I've not got one to a high enough level - yet - to find out.)
For example, the first boss fight in MC (Krol Whatshisface): Everybody's whaling on the Big Guy, when up pops some little snit of a powrie who decides to have at you (or the healer) with his sickles, but no matter what you throw at him - never mind that your targeting reticule is full on him - all your shots go towards the boss!!
"I have never considered it polite to comment upon the ravings of the insane, nor profitable to engage in arguments with lunatics." - King Avallach (Taliesin - Stephen Lawhead)
This bug/problem can definitely be a hassle for the poor CW trying to dust adds off the healer (or themselves) whilst the tank is busy keeping the boss occupied. (Possibly also for a HR, but I've not got one to a high enough level - yet - to find out.)
HR's Split Shot has a nasty habit of auto-aiming at a specific mob and tracking them- which is the opposite of what you want with a very slow-charging AoE. However, I don't think this is so much a bug as poor design. Don't worry though, the problem will be fixed in Mod 3 by rendering Split Shot useless with nerfs
There should be a dedicated event, a kind of celebration for the first birthday of all those one-year-old bugs. One Grand day of the bugs.
- All the companions would directly jump from the nearest cliff.
- All the doors and melting walls in dungeons would remain closed.
- All healing would be deflected
- In Protctor Enclave you could walk only backwards
There should be a dedicated event, a kind of celebration for the first birthday of all those one-year-old bugs. One Grand day of the bugs.
- All the companions would directly jump from the nearest cliff.
- All the doors and melting walls in dungeons would remain closed.
- All healing would be deflected
- In Protctor Enclave you could walk only backwards
Would there also be an event where invisible wall mazes appeared, requiring you to randomly backtrack occasionally, to progress across featureless ground planes?
i wonder if they will ever fix the exploit that is reported time and again for Castle Never. both the chest one (if u get in during DD the chest stays open after so ppl just go in and out CN until they find a open chest at the end with the dragon dead) and the one where some classes can get on the gate and aggro just the dragon from outside and slowly kill it . people all over the server are exploiting these and the ancient weapons prices have gone to hell for the ppl that can actually do a legit run. patch it fast please.
Comments
There are bugs, for sure (like the door getting stuck in CN if two people try to open it forcing you to quit the dungeon), but I haven't seen these at all.
Bugs are fixed in the priority set down by the QA team. What that means is that bug reports are looked over by the QA team and sorted in order of priority. That does not mean they are fixed in the order they receive them.
For instance, a minor graphical bug may be of importance to a given player but of low priority in general. Likewise, a bug that the players may not think much of may be given a higher importance due to factors not known to the general populace (and no, contrary to popular belief, it is NOT how much the given issue will affect ZEN sales--financial and marketing information usually isn't even known to the QA department).
Also, first rule of debugging: If you can't find the cause, you can't devise the fix. Anyone who's done any sort of programming knows this, especially when you have to sift through thousands--if not millions--of lines of code to find the ONE misplaced variable or string that's causing the problem.
This, furthermore, gets pushed around by incoming content--after all, that has to be debugged as well. Bottom line is that simply because a bug has been around for a while doesn't mean it has been ignored--it simply means that there are higher priority issues. The QA team doesn't have infinite time to work on everything, thus, everything must be prioritized, and prioritizing is a constant process.
Great Weapon Fighter: Because when is today not a good day to die?
PC and PS4 player. Proud Guildmaster for PS4 Team Fencebane. Rank 5 Officer for PC Team Fencebane. Visit us at http://fencebane.shivtr.com
I do usually try to be constructive but after doing a flame dungeon with giants that follow after you while charging up thier self targetting AoE until your stamina is dry and you can't dodge kinda got me steamed. So manners kinda get tossed out the window at that point.
my favorite (?) is the filters in AH for enchantment types don't work (offense/defense/weapon) etc. STILL.
Would've thought being unable to progress in CN/VT and the MC shadow log for amd cards would be high priority. Guess not...
This bug/problem can definitely be a hassle for the poor CW trying to dust adds off the healer (or themselves) whilst the tank is busy keeping the boss occupied. (Possibly also for a HR, but I've not got one to a high enough level - yet - to find out.)
For example, the first boss fight in MC (Krol Whatshisface): Everybody's whaling on the Big Guy, when up pops some little snit of a powrie who decides to have at you (or the healer) with his sickles, but no matter what you throw at him - never mind that your targeting reticule is full on him - all your shots go towards the boss!!
HR's Split Shot has a nasty habit of auto-aiming at a specific mob and tracking them- which is the opposite of what you want with a very slow-charging AoE. However, I don't think this is so much a bug as poor design. Don't worry though, the problem will be fixed in Mod 3 by rendering Split Shot useless with nerfs
- All the companions would directly jump from the nearest cliff.
- All the doors and melting walls in dungeons would remain closed.
- All healing would be deflected
- In Protctor Enclave you could walk only backwards
Would there also be an event where invisible wall mazes appeared, requiring you to randomly backtrack occasionally, to progress across featureless ground planes?