How to report core and DB bugs straight to the developers

Hi guys,

In the interest of helping the developers locating and fixing bugs, both core and DB. I'm going to show you where and how to post it so we can give feedback faster which hopefully means DB/Core bugs will get fixed faster..

Core development covers,

• Spells, which includes procs from items, armor, trinket, armor set. So if the item doesn't proc or giving wrong damage calculation, then it needs to be reported to core
  
• Talents, which means if your talent doesn't work or work the wrong way, report it to the core devs.
  
• Game mechanics, such as damage/parry/dodge/defense/resilience calculation, etc
  
• Instance scripting, for example, opening of door in instance, boss skills, spawns, summon (if summon and spawn is part of event
  
• Battleground scripting, for example, summoning Tree lord in AV, doors, etc.
  
• Events, for example, Halloween, Battleground weekend, Children's week, etc
  
• Achievement
  
• Pet's ability/talent
  
• Special quests such as escort quest, using mounts to complete quests, etc
  

Format and rules for reporting core bugs to devs

• To report, you go to http://www.trinitycore.org/forum/project.php?do=issuelist&projectid=3&issuetypeid=bug (Remember that we're using Trinity2)
  
• Search the forum first before posting, this is to make you sure don't post a bug which already been reported. Or maybe the bug has already been fixed in repository but I haven't update our core yet.
  
• If a bug is already been reported, simply add a reply to confirm the bug and let them know which revision that we're running on.
  
• For core bugs, always be nice in explaining what the bug is, don't demand. These people do this project for free and using their own spare time, so be very nice to them.
  
• Describe what is wrong, try to be as descriptive as possible. Don't just say "Doesn't work". Explain to them what doesn't work and how it suppose to be.
  
• When describing how things suppose to work, always use othe external information source to backup your report. For example, use WoWArmory, WoWWiki, Youtube (if you try to show how bosses should be scripted), and last WoWHead (WoWHead is known among devs to be not very reliable since it captures info from private server too).
  
• Always mention what revision of core that we're using, if you don't know, have a look at the update log at https://blackcat.forumotion.com/server-information-f1/server-update-log-t38.htm check the latest post and that will be the revision number. I normally update my core every Saturday
  
• Always mention that the core is compiled on release build (not debug build) using MS Visual Studio 2008 Pro.
  
• Remember that they're ONLY interested in how are thing in blizzlike (retail), so don't quote other PS when describing how things suppose to be.
  
• If you are planning to help, tell me what your nick is in the dev's core/db forum so I know. My nick there is BlackCat2
  

DB development covers,

• Wrong items stats, for example, it suppose to be +12 STA but when on our server is only +10 STA or wrong level
  
• Mob drops / loot, for example Mobs on Howling Fjord don't drop anything, to fix this, report to DB people.
  
• Wrong drop/loot rate
  
• Mobs/NPC/Boss is not spawned or missing
  
• Mobs/NPC/Boss has wrong stats, for example, too much HP or too little HP.
  
• Spawning items/objects - it's called gameobjects for quests
  
• Vendor items
  
• Trainers, for example Trainer A doesn't teach Spell A
  
• Quests credits, for example Killing A doesn't give you the credit.
  
• Quest text/rewards, if they're wrong, it's DB related.

Format and rules for reporting DB bugs to devs

• To report, you go to http://trinitydatabase.org/index.php?/forum/6-bug-reports/
  
• Search the forum first before posting, this is to make you sure don't post a bug which already been reported. Or maybe the bug has already been fixed in repository but I haven't update our core yet.
  
• If a bug is already been reported, simply add a reply to confirm the bug and let them know which revision that we're running on.
  
• There a DB bug guideliness as well on the dev forum, please read it first before doing anything. It's on http://trinitydatabase.org/index.php?/topic/12055-bug-reporting-guidelines/
  
• DB developers have different section for different bugs, for example, loot bugs is in different section from NPC bugs, so please make sure you post in the right section.
  
• When reporting bugs, always be nice in explaining what the bug is, don't demand. These people do this project for free and using their own spare time, so be very nice to them.
  
• Describe what is wrong, try to be as descriptive as possible. Don't just say "Doesn't work". Explain to them what doesn't work and how it suppose to be.
  
• When describing how things suppose to work, always use othe external information source to backup your report. For example, use WoWArmory, WoWWiki, and last WoWHead (WoWHead is known among devs to be not very reliable since it captures info from private server too - so don't rely on it).
  
• Always mention what revision of core that we're using, if you don't know, have a look at the update log at https://blackcat.forumotion.com/server-information-f1/server-update-log-t38.htm check the latest post and that will be the revision number. I normally update my core every Saturday
  
• Always mention what DB version that we're using, at the moment we're using UDB 382 (converted). I'll try to update it so it'll stay current. If you don't know, ask me.
  
• Remember that they're ONLY interested in how are thing in blizzlike (retail), so don't quote other PS when describing how things suppose to be.
  
• If you are planning to help, tell me what your nick is in the dev's core/db forum so I know. My nick there is BlackCat2