Search the Community

Showing results for tags 'tracker'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • NEWS AND RULES
    • News and Announcements
    • Rules and Guidelines
  • INPUT AND ASSISTANCE
    • Community support
    • Guides and Tutorials
    • Report a Player
    • Ban appeal
  • COMMUNITY
    • General Discussion
    • Suggestions and Opinions
    • Introduce yourself
    • PvP
    • PvE
    • Media
    • Off-Topic
    • Bugtracker
    • Class Discussion
  • REALM DISCUSSIONS
    • Trade
    • Guild Recruitment
    • Arena Recruitment
  • HAVOC-WOW VIDEOS
    • Official Videos
    • PvP Battles
    • Video Suggestions
  • Staff Applications
    • GM Apps
  • Havoc WoW Club's Topics

Product Groups

There are no results to display.

Blogs

There are no results to display.

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Race


Class

Found 1 result

  1. Syl

    Bugtracker Guidelines

    Bugtracker Guidelines We highly appreciate your efforts to report any problems you may discover on our site or in-game. In order to process and resolve all reported bugs, we ask you to follow the guidelines below. - Make sure to search between submitted issues before posting a new one to our bugtracker. It's possible someone else has already reported the issue in question. - Improper use of the system will result your reporting privileges being revoked. - Use proper titles. E.g. the name of the quest, NPC or Item you have problems with. - What is wrong? E.g. What happens and what is supposed to happen. - Add anything else you think might be useful for us to know. - Avoid revealing or using any kind of your personal data on submitting issues. Please follow these guidelines and you'll make our work-space much cleaner and easier. In return, we'll reward you with 2 DP for each confirmed issue; FORMAT FOR REPORT: Description: Current behaviour: /*Tell us what happens */ Expected behaviour: /*Tell us what should happen instead*/ Steps to reproduce the problem: 1. 2. 3. ... NOTE: Issues will get moved to the "Pending" section of the bugtracker after they have been confirmed.