Glorious Alpha Two Testers!

Phase I of Alpha Two testing will occur on weekends. Each weekend is scheduled to start on Fridays at 10 AM PT and end on Sundays at 10 PM PT. Find out more here.

Check out Alpha Two Announcements here to see the latest Alpha Two news and update notes.

Our quickest Alpha Two updates are in Discord. Testers with Alpha Two access can chat in Alpha Two channels by connecting your Discord and Intrepid accounts here.

Bug Reporting Template

@Okies and I put together a template in order to help everyone report bugs cleanly. Examples are also provided within the template to give a general idea of how to properly write bugs instead of giving the devs 100s of posts stating "WaEpon suxorz!! PLAZ FIX".

Will update and change as neccessary.

Server: (Phoenix-EU)
Build number
: (00122.1)
Type: (Graphic,Sound,Etc.)
Region: (Darkwood forest)
Location: (X / Y / Z)
Phased/Instanced
: (Y/ N - Explain)

Summary
: Bunny explodes on bush --

Expected result: Bunnies do not explode upon contact with bushes. 

Actual result: 
Observed at 10:59 am PST on 12/15/2017 a small bunny entered collision with a bush at location X/Y/Z and then promptly exploded.

Bugdata
: "Error - Target path missing"
(Creature/Model ID. if available)
(May not be available. If is most likely will be /bugdata in chat, showing an error message or something similar) --

Reproducibilty
: X/5 (ALWAYS test the bug 5 times and report how many times it reproduced) --

Bug reproduction steps
:
1. Go to Location (X/Y/Z)
2. Attack a nearby bunny
3. Lead bunny to Bush at (X / Y / Z)
4. Observe bug

Additional Comments
: Bunny color and/or level does not change outcome
(These comments are for further information not already covered)

Attachments / Screenshots
: Screenshot.322nkwuuu12

Comments

  • I've never tested for bugs before so thanks for this. Could you add other things that are commonly buggy in developing MMO's so I could keep a look out for them?
  • Great work guys, I think I speak for the community as a whole when I say, THANK YOU!!!!!!!
  • Thanks in bunches!  Expecting this to be used heavily.
  • @Deathfyre You should add a date and time of the occurrence. For devs it's always useful to have a timestamp to inspect certain logs :wink:
  • Herdo said:
    @Deathfyre You should add a date and time of the occurrence. For devs it's always useful to have a timestamp to inspect certain logs :wink:
    It seems redundant currently; assuming so far that posting bugs will happen here on the forums which are timestamped anyways. If there is another way for us to report bugs that doesn't have timestamps already implemented, I will be sure to add all proper sections thatbthe devs will need.
    Soon I will also be writing up more examples of what types of bugs there are, how to identify them, and how to describe their reproducibilty properly. 
  • Not really redundant, if you are accumulating reports due to being tied up with an ongoing event in game which may prevent you from stopping to go to forum to make a report.  Some ppl might take screens and make notes and come back later to type up a proper report.
  • Jennoula said:
    Not really redundant, if you are accumulating reports due to being tied up with an ongoing event in game which may prevent you from stopping to go to forum to make a report.  Some ppl might take screens and make notes and come back later to type up a proper report.
    Exactly. Even if you encouter a bug, you might not stop in the middle of a raid, siege or whatever to report it to the forums :smile:

    @Deathfyre Additionally, what we normally do when fixing bugs, is to require our "customers" to explain the expected behavior. E.g. when I click that button, it should actually do A and B, but it only does A. This helps to identify bug reports from actual feature requests :wink:
  • ArchivedUserArchivedUser Guest
    edited December 2017
    Herdo said:
    Jennoula said:
    Not really redundant, if you are accumulating reports due to being tied up with an ongoing event in game which may prevent you from stopping to go to forum to make a report.  Some ppl might take screens and make notes and come back later to type up a proper report.
    Exactly. Even if you encouter a bug, you might not stop in the middle of a raid, siege or whatever to report it to the forums :smile:

    @Deathfyre Additionally, what we normally do when fixing bugs, is to require our "customers" to explain the expected behavior. E.g. when I click that button, it should actually do A and B, but it only does A. This helps to identify bug reports from actual feature requests :wink:
    Thank you for reminding me about expected behaviour. I know i was forgetting a major section and has been bothering me xD. I'm going to add that as soon as I can along with actual behaviour section where timestamps can easily be added into. Example: Observed at 10:59 am on 12/15/2017 a small bunny entered collision with a bush at location X/Y/Z and then promptly exploded.

  • Solid bug reporting template.  Well done.  Having the template with an easy to use example is definitely helpful for people who have and might not have had the chance to go squash bugs.
  • For those under NDA

    Sarumonin-Today at 7:43 AM

    Please avoid talking about the game or launcher from this moment forward, do not talk about the launcher, patcher, etc. Thanks friends. If you have any issues, contact a Moderator directly.
Sign In or Register to comment.