READ ME FIRST!! - Bug Report Template

[Silvard]

With the aim of making bug fixing a more expedient and precise process it is recommended that you share as many details as possible in your report, so that the team can more easily identify exactly what the bug is and if possible how to reproducing it in testing (which is instrumental in fixing it). As such please try to fill out as much of the following template as possible when you make your report. Please feel encouraged to add as much as you can:

Description

Steps to reproduce

Expected result

Actual result

Screenshot(s)

Misc Notes

Which Server(s)?

Gaming Platform(s)?

[LittleWeasel]

For ease of copy / paste into your forum response, see code below

Code: Select all

[u]Description of Bug Experienced:[/u]
(please include information of what you did, that lead up to the bug, what you expected to happen there, and what actually happened, then move on to describe below:)


[u]Steps to reproduce the Bug:[/u]


[u]Expected Result:[/u]


[u]Actual Result:[/u]


[u]Screenshot(s)[/u]
(You can either add screenshots by uploading them to imgur, or by uploading them to Discord and put the respective links between [img] img link.jpg [/img])

[u]Additional Information/Notes[/u]

[Batrachophrenoboocosmomachia]

Like the reminder said - use the above template when making a post in this forum. Even if your bug makes it seem painfully self-evident and unnecessary to you, it may tell us more about what's happening behind the scenes than you realize.

The only bugs that do not need "steps to reproduce" are non-behavior bugs, like a resource node stuck in a wall or a broken area transition or similar. If it's a bug in an action or behavior you perform, providing a basic set of steps to reproduce it helps us fix things much faster and keeps the backlog from murdering us.

[Kenji]

Updated original template to include inquiry for live or PGCC server

[garrbear758]

Like the reminder said - use the above template when making a post in this forum. Even if your bug makes it seem painfully self-evident and unnecessary to you, it may tell us more about what's happening behind the scenes than you realize.

The only bugs that do not need "steps to reproduce" are non-behavior bugs, like a resource node stuck in a wall or a broken area transition or similar. If it's a bug in an action or behavior you perform, providing a basic set of steps to reproduce it helps us fix things much faster and keeps the backlog from murdering us.

Just want to remind everyone of this. If you do not use the template, don't be surprised if your bug report gets closed without resolution. We have 3,854 script files alone, many of which have several thousand lines of code, not to mention anything involving haks. If we don't have anything to go off of, chances are we won't be able to find the cause of the bug to be able to resolve it.