Skip to content

Public Nin Online Repository for Bug Tracking

License

Notifications You must be signed in to change notification settings

RorySoh/NinOnline

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Nin Online Logo

Nin Online Public Bug Tracking Repository

This is where we handle public bug report submissions for Nin Online.

Read these guidelines before reporting a bug

Many users file bugs which are useless because they don't contain enough information for us to do anything about them. Our policy is to close these bugs without investigating them. Please follow these guidelines to avoid having your bug closed and help make sure we can fix the bug you're reporting.

Most bugs are not actually obvious, even if they look obvious to you. Usually issues actually only happen in a very specific set of circumstances, which you happen to have. These guidelines are designed to make sure we can figure out what's going on. So please never skip any part of the guidelines, no matter how obvious you think the problem is, or how many issues you've filed before - skipping any details will likely make it much more difficult to help you.

Make sure you understand the bug

Many bug reports are actually just unintended consequences of systems that are working as intended. This is not a bug, and should be addressed as a suggestion.

Make sure you are running the latest version of the game

To avoid reporting bugs we've already fixed, please verify the issue happens in the latest version of client, and then verify that there is no existing bug report that matches the issue you plan to report already in the Issues tab. There is a chance that it may already be fixed in the pending update.

Use the bug report template

The bug submission page is pre-filled with a template. Do not delete it - we need all this information to be able to help you. Please provide as much of the requested information as you can, including the system details or crash report information with every report.

Only mention one problem per issue

Please only describe one problem in each issue you create. It's very confusing to have two separate descriptions at once and usually means you skipped some important information for one of them.

About

Public Nin Online Repository for Bug Tracking

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published