template->_php_include(): File ./../includes/nav.inc.php does not exist or is empty

How To Report A Bug

Are you having trouble with Puny Human's products?

Moderators: KindredPhantom, Forum Moderators

How To Report A Bug

Postby KindredPhantom » Thu Feb 17, 2011 7:59 am

Hi guys here is simple guide on how to report bugs in our bug tracker, Redmine. The following is a longer verison of how to report a bug in redmine, for the shorter version click here.

Reporting a Bug

In the first part of this guide we will be covering how to report a bug in redmine.

First you need to go to http://redmine.punyhumangames.com and click "Sign In" in the top right corner of your screen -

Image

If you don't have an account for redmine you will need to register one before we can proceed, just click "Register" in the top right corner of your screen and follow the instructions to create your redmine account. I'll just wait here until you have done that....

Image

Finished? Good, now let us continue.

After signing in you should find yourself at this page -

Image

On this page you should see two projects that you can choose from, "Blade Symphony", and "Dystopia". To choose a project just click on the name of that project, for the purpose of this guide we shall choose project Blade Symphony, so click on "Blade Symphony".

Image

You will now see the following page, you will be able to select from one of several tabs, the one that we are going to use in this guide is "new issue".
Before we do that you first need to enter a few words about the bug in the search bar located in the top right corner of the screen. It is important to search before reporting new bugs because someone may have already reported the bug you are about to report.

Image

If you find someone has already reported the bug then you will not need to report it, instead you can "update" the bug with any more information about that bug, to do this click "update", enter text and the click submit.

Image

However if after searching you find no one else has reported the bug then you need to click on the "new issue" tab, this is the start of reporting a new bug.

Image

You should see the following after you have clicked "new issue".

Image

When reporting a bug first check that "Tracker" is set to "Bug", there are three options in "Tracker", "Bug", "Suggestion" and "Task", for now we only want "Bug" so ignore the other two options.

Image

Now you need to fill in "Subject", put in a brief but descriptive sentence that sums up what the bug is, for example let us say there is a problem with the Knight's (Judgement) Tier 1 Heavy attack animation. In the bug report's "Subject" we would put "Knight's Tier 1 Heavy Attacks Animation Becomes Stuck After Repeated Spamming", this sentence sums up the type of bug and the character class that it affects.

Image

For the "Description" you need to describe what the bug is and why it is a bug, going back to our example we would put "The Knight's Tier 1 Heavy Attack animation can become stuck after a player repeatedly spams the attack, this leads to the attack animation becoming stuck and the player is unable to use any attacks in the round. This is a bug because the attack animations becomes stuck which means the player can no longer attack and gives them a major disadvantage as they can no longer attack."
After adding the description you need to add "Reproduction Steps", these steps are important as they tell testers and developers how to reproduce this bug which is an important part of the process to fixing the bug. For the example bug the "Reproduction Steps" would be:

1) Load Blade Symphony
2) Join a server and have another person join you to test this bug
3) Choose the Knight (Judgement) Character with any sword
4) Have the other person choose any character with any sword
5) Choose an arena and ready up
6) Use the Heavy Stance and repeatedly spam Heavy Tier 1 Attack
7) Notice that the Heavy Tier 1 Attack animation becomes stuck not allowing you to use any other attack

Image

Now after adding the "Subject" and the "Description" you need to choose the "Category" and "Berimbau Map" fields. You do not need to change the "Status", "Priority" and "Assigned to" fields, leave these fields alone as they will be done by Puny Human Staff later.
For "Category" you have five options to choose from, "Audio", "Graphics", "Mapping", "Programming" and "Stats". When reporting a bug you will need to select the "Category" that the bug falls into, for the example bug the "Category" that it would fit into would be "Programming" so we would select "Programming" and move onto "Berimbau Map".

Image

For "Berimbau Map" we would select the map that the bug occurs on, currently you have five options to choose from "GLOBAL", "duel_monastery", "duel_winter", "duel_district" and "box". In the case of the example bug the map would be "GLOBAL" as the bug can occur on any map, it does not occur on any maps it occurs on all of them.

Image

Now we need to fill in the "Result" and "Expected" fields, in the "Result" field you add what the "Result" of the bug is, in the case of the example bug the "Result" would be, "Knight's Heavy Tier 1 Attack Animation can become stuck after spamming". In the "Expected" field you add what you would normally expect, in the case of the example bug the "Expected" would be, "For the Knight's Heavy Tier 1 Attack animation to not become stuck after spamming".

Image

Now before we finish, their is one last thing to do and that is to add a screenshot or another file to the bug report, to add a screenshot or file to the bug report you need to click "Choose File" and click on the file you wish to add to the bug report. When adding screenshots try to keep them under 1 MB in size, you can do this by making sure that the screenshots you attach are JPG's. You can add additional files by clicking "Add Another file" and then clicking "Choose File" again. In the case of the example bug report, a screenshot is not required but a video file could be added to show the bug happening in game.

Image

If your bug is a crash, then it's very helpful if you can upload the crash file by following this guide. For most people who will be running on Windows that file will be a MDMP. This is a file recorded by the source SDK that details what went wrong during the crash. Not all crashes will produce one, but please check for them. They will be located under C:\Program Files\Steam\steamapps\YOURSTEAMUSERNAME\source sdk base with enchanting names like "Steam__3264__2008_6_13T0_10_3C1520140.mdmp".

Finally click "Preview" at the bottom of the screen to "Preview" your bug report to check for any spelling or grammar errors before you submit your bug report. When you are happy with your bug report click the "Create and Continue" button to submit your bug report, and you are done, you have reported your bug. Thanks for reading and submitting your bugs.

Image
Image
Image
Image
User avatar
KindredPhantom
Puny Human staff
 
Posts: 3166
Joined: Mon Jan 23, 2006 8:27 am
Location: United Kingdom

Re: How to report a bug/suggestion in redmine

Postby KindredPhantom » Thu Feb 17, 2011 1:12 pm

Reporting a Bug the tl;dr version
-----
Hi guys here is simple guide on how to report bugs in our bug tracker, redmine.

Reporting a Bug

First you need to go to http://redmine.punyhumangames.com and click "Sign In" in the top right corner of your screen -

Image

If you don't have an account for redmine you will need to click "Register" in the top right corner of your screen and follow the instructions to create your redmine account.

Image

Before reporting a bug you need to enter a few words about the bug in the search bar located in the top right corner of the screen. It is important to search before reporting new bugs because someone may have already reported the same bug.

Image

If you find someone else has already reported the bug then you will not need to report it, instead you can "update" the bug with any more information about that bug, to do this click "update", enter text and then click submit.

When reporting a bug first check that "Tracker" is set to "Bug".

Image

Now you need to fill in "Subject", put in a brief but descriptive sentence that sums up what the bug is.

Image

For the "Description" you need to describe what the bug is and why it is a bug. After adding the description you need to add "Reproduction Steps".

Image

After this you need to choose the "Category" you have five options to choose from, "Audio" (voices, ambient sounds), "Graphics" (models, props), "Mapping" (mapping issues), "Programming" (crashes, attacks) and "Stats" (in-game statistics, the stats site).

Image

For the "Berimbau Map" field you choose either GLOBAL (all maps) or choose from one of the four offical maps.

Image

For the "Result" field you add what the "Result" of the bug is. In the "Expected" field you add what what should happen.

Image

You do not need to change the "Status", "Priority" and "Assigned to" fields, leave these fields alone as they will be done by Puny Human Staff later.

To add a screenshot or file to the bug report you need to click "Choose File" and click on the file you wish to add to the bug report. When adding screenshots try to keep them under 1 MB in size, you can do this by making sure that the screenshots you attach are JPG's. You can add additional files by clicking "Add Another file" and then clicking "Choose File" again. In the case of the example bug report, a screenshot is not required but a video file could be added to show the bug happening in game.

Image

If your bug is a crash, then it's very helpful if you can upload the crash file by following this guide. Not all crashes will produce one, but please check for them. They will be located under C:\Program Files\Steam\steamapps\YOURSTEAMUSERNAME\source sdk base with enchanting names like "Steam__3264__2008_6_13T0_10_3C1520140.mdmp".

Finally click "Preview" at the bottom of the screen to "Preview" your bug report to check for any spelling or grammar errors before you submit your bug report. When you are happy with your bug report click the "Create and Continue" button to submit your bug report, and you are done, you have reported your bug. Thanks for reading and submitting your bugs.

Image
Image
Image
Image
User avatar
KindredPhantom
Puny Human staff
 
Posts: 3166
Joined: Mon Jan 23, 2006 8:27 am
Location: United Kingdom


Return to Tech Support

Who is online

Users browsing this forum: No registered users and 4 guests

cron