[ Support Center • Rules & Policies and Guidelines • ARC ToS • Guild Recruitment Guidelines | FR DM Since 1993 ]
test content
Logo
What is the Arc Client?
Install Arc
Bug Reporting Guidelines [Please Read Before Submitting a Bug]!
zebular
Member, Neverwinter Moderator, NW M9 Playtest Posts: 15,270 Community Moderator
In an effort to bring justice to the bugs that plague Neverwinter, we're keeping this thread as a how-to on submitting bug reports and explaining the process of how bugs get fixed.
Many of you are wondering why a bug doesn't get fixed when there are multiple reports. I'm here to answer!
Most of the time, it's due to the fact that it's not 100% reproducible or there are no clear steps on how to get the bug to happen. When QA looks into a bug, there's very little they can do by a simple sentence like "X is not working." When X isn't working, it could be due to a million things! There's simply no time to do massive halo testing, hence why we ask for "repro steps."
Repro steps are a step by step, specific list of how to get the bug to occur. For example, let's look at the SW bug where Harrowstorm didn't knock targets prone after applying a curse:
1) Log in to a level 60+ Scourge Warlock
2) Slot Harrowstorm as one of your Encounter Powers
3) Head to any zone with monsters
4) Target a monster with Harrowstorm
5) While Harrowstorm is active on the monster, Curse it by pressing Tab on them
Observed Result:
Harrowstorm doesn't knock targets prone after applying the curse.
Expected Result:
Harrowstorm should knock targets prone after applying the curse.
If you have any screenshots or videos, make sure to attach them!
That's it! Something that simple could bring that pesky bug to justice. In order to fix something, we need to know exactly where to look, hence the repro steps.
I encourage all players to submit repro steps for any new and old bugs in order to get them all fixed. Thank you for reading!
P.S. Please do not discuss exploits on the public forums. If you have repro steps for an exploit, let one of the mods know via Private Message. Thank you!
Many of you are wondering why a bug doesn't get fixed when there are multiple reports. I'm here to answer!
Most of the time, it's due to the fact that it's not 100% reproducible or there are no clear steps on how to get the bug to happen. When QA looks into a bug, there's very little they can do by a simple sentence like "X is not working." When X isn't working, it could be due to a million things! There's simply no time to do massive halo testing, hence why we ask for "repro steps."
Repro steps are a step by step, specific list of how to get the bug to occur. For example, let's look at the SW bug where Harrowstorm didn't knock targets prone after applying a curse:
1) Log in to a level 60+ Scourge Warlock
2) Slot Harrowstorm as one of your Encounter Powers
3) Head to any zone with monsters
4) Target a monster with Harrowstorm
5) While Harrowstorm is active on the monster, Curse it by pressing Tab on them
Observed Result:
Harrowstorm doesn't knock targets prone after applying the curse.
Expected Result:
Harrowstorm should knock targets prone after applying the curse.
If you have any screenshots or videos, make sure to attach them!
That's it! Something that simple could bring that pesky bug to justice. In order to fix something, we need to know exactly where to look, hence the repro steps.
I encourage all players to submit repro steps for any new and old bugs in order to get them all fixed. Thank you for reading!
P.S. Please do not discuss exploits on the public forums. If you have repro steps for an exploit, let one of the mods know via Private Message. Thank you!
[ My Character Bios | Discord: Zebular#9524 | In Game: @zebular (PC) • @MtnDewFreak (XBOX) • @Terraseer (PS4) ]
[ Support Center • Rules & Policies and Guidelines • ARC ToS • Guild Recruitment Guidelines | FR DM Since 1993 ]
[ Support Center • Rules & Policies and Guidelines • ARC ToS • Guild Recruitment Guidelines | FR DM Since 1993 ]
1
This discussion has been closed.
Comments
For Console Players, the best way to report an in game bug (that's not an exploit) is to use this Bug Report forum to make a thread detailing the bug (again, as long as it is not an exploit).
To report exploits, contact any Neverwinter Community Moderator via Private Message (or even via Discord private messages) and detail the issue to us. We will then forward that to the Devs.
Please do not make a Support Ticket via the Support Section to report Console Bugs. Support Tickets should only be made for things that need a Game Master (Perfect World Entertainment) whereas Bug Reports should be things that the Developers (Cryptic Studios) need to be made aware of. Bug Reports go to Cryptic, Support Tickets go to PWE.
If you file a Bug Report as a Support Ticket, you'll be wasting your time and PWE's time as they will just tell you to make a bug report.
The only time you should be filing a Bug Report as a Support Ticket is when the Developers or Community Staff explicitly say to. For example, you made a post about a known bug that caused you to loose an item. A Dev or Community Staff Member replied telling you that support is aware and you should file a Support Ticket so they can authenticate the loss and reimburse you. Another example would be you posted a known bug that caused your character to get stuck somewhere and no in-game means will alleviate the issue. A Dev or Community Staff Member replied telling you contact Support so they can fix your character's location.
[ Support Center • Rules & Policies and Guidelines • ARC ToS • Guild Recruitment Guidelines | FR DM Since 1993 ]