Difference between revisions of "How To: Submit a Bug Report"
m (add guide category) |
m |
||
Line 47: | Line 47: | ||
[[Image:title.png]] | [[Image:title.png]] | ||
− | There will be a template pre-filled into the comment field. | + | There will be a template pre-filled into the comment field. '''DO NOT DELETE THIS.''' |
<br> | <br> | ||
It will look like this: | It will look like this: | ||
Line 97: | Line 97: | ||
Please make sure to fill out every field in the bug report form, or make sure to write N/A if it does not pertain to your bug report. | Please make sure to fill out every field in the bug report form, or make sure to write N/A if it does not pertain to your bug report. | ||
− | + | '''Disclaimer''': This does not apply to the website bug report. The bug reports pertaining to the website will use this template: | |
**Bug Date & Time**: | **Bug Date & Time**: | ||
**Bug Name**: | **Bug Name**: | ||
Line 109: | Line 109: | ||
Please make sure that ALL information is correct before submitting. | Please make sure that ALL information is correct before submitting. | ||
<br> | <br> | ||
− | If for some reason, the information pertaining to the bug report changes, | + | If for some reason, the information pertaining to the bug report changes, '''DO NOT EDIT YOUR BUG REPORT ''OR THE TEMPLATE'''''. |
<br> | <br> | ||
Instead, please make a new comment with the updated information. Editing the template may mess up the entire format, so please do not touch it! | Instead, please make a new comment with the updated information. Editing the template may mess up the entire format, so please do not touch it! | ||
Line 116: | Line 116: | ||
Additionally, while referring to in-game commands, please use the $ symbol instead of the @ symbol. This prevents random users from being pinged. | Additionally, while referring to in-game commands, please use the $ symbol instead of the @ symbol. This prevents random users from being pinged. | ||
− | + | '''IF YOUR BUG REPORT DOES NOT HAVE THE TEMPLATE FORMAT, IT WILL BE CLOSED WITHOUT WARNING.''' | |
− | <br> | + | <br /> |
− | TO AVOID THIS, PLEASE MAKE SURE TO TAKE YOUR TIME AND GIVE US ALL THE INFORMATION! | + | '''TO AVOID THIS, PLEASE MAKE SURE TO TAKE YOUR TIME AND GIVE US ALL THE INFORMATION!''' |
− | <br> | + | <br /> |
− | IF YOUR BUG REPORT HAS BEEN CLOSED, PLEASE RESUBMIT IT WITH THE INFORMATION NEEDED. :) | + | '''IF YOUR BUG REPORT HAS BEEN CLOSED, PLEASE RESUBMIT IT WITH THE INFORMATION NEEDED. :)''' |
== Responding to a bug report == | == Responding to a bug report == |
Revision as of 13:41, 28 July 2021
Contents
How to Submit a Bug Report
You can locate the link to the platform for bug reporting on the main website, http://www.legiondark.com/.
On the top of the website, there are four tabs. Click the second tab, named "Community". A drop-down menu will appear.
For bug reports pertaining to the server, please choose "Bug Reports (Server)".
For bug reports pertaining to the website, please choose "Bug Reports (Website)".
Additionally, you can also find these platforms here.
Bug Reports (Server)
Bug Reports (Website)
Registration
To submit a bug report, first you'll need to register an account with Github.
Start by going to http://www.github.com/.
At the top right-hand corner, there will be two options. Choose "Sign Up".
Choose a username, password, and a corresponding e-mail. We recommend using a legitimate e-mail so that you can see e-mail alerts when staff respond to your bug reports.
Make sure to verify your e-mail.
Submitting a Bug Report
To submit a bug report, go to the corresponding link, whether your issue is with the server or the website.
At the top of the webpage, there will be seven tabs. Choose "Issues".
Once the page updates, on the righthand side, there will be a button that says "New Issue".
Choose a title that corresponds with the issue that you're having so that GMs can find your issue easily.
There will be a template pre-filled into the comment field. DO NOT DELETE THIS.
It will look like this:
- Date & Time**:
- FFXI Client Version (use `/ver`)**:
- Server's Expected Client Version matches, yes/no? (use `$ecv`)**:
- Character Name**:
- Nation**:
- Job(level)/Sub Job(level)**:
- NPC or Monster or item Name**:
- Zone name**:
- Coordinates (use `$where`)**:
- ffxiah.com link (for items issues only)**:
- Multi-boxing? (multiple clients on same connection)**:
- Steps To Reproduce / any other info**:
Please make sure to fill out every field in the bug report form, or make sure to write N/A if it does not pertain to your bug report.
Disclaimer: This does not apply to the website bug report. The bug reports pertaining to the website will use this template:
- Bug Date & Time**:
- Bug Name**:
- Bug Page/Url**:
- Bug Information**:
- Steps To Reproduce The Bug**:
- Additional Information**:
After you've finished a bug report, submit!
Please make sure that ALL information is correct before submitting.
If for some reason, the information pertaining to the bug report changes, DO NOT EDIT YOUR BUG REPORT OR THE TEMPLATE.
Instead, please make a new comment with the updated information. Editing the template may mess up the entire format, so please do not touch it!
Additionally, while referring to in-game commands, please use the $ symbol instead of the @ symbol. This prevents random users from being pinged.
IF YOUR BUG REPORT DOES NOT HAVE THE TEMPLATE FORMAT, IT WILL BE CLOSED WITHOUT WARNING.
TO AVOID THIS, PLEASE MAKE SURE TO TAKE YOUR TIME AND GIVE US ALL THE INFORMATION!
IF YOUR BUG REPORT HAS BEEN CLOSED, PLEASE RESUBMIT IT WITH THE INFORMATION NEEDED. :)
Responding to a bug report
Please be aware that it may take GMs time to respond to a bug report. We may not be able to immediately fix your issue.
We ask that players do not be hostile towards GMs if they are unhappy, as GMs are doing their best. There are a lot of bugs and we can't always pay attention to every single one at the same time. It takes time to fix things. :)
If players do become hostile, bug reports may be closed without warning.
If a player does not respond to a GM after 3 days, a bug report may be closed without warning. Make sure to check your bug report daily to ensure that you do not accidentally miss a response from a GM.