Jump to content

Bug reporting


savvage

Recommended Posts

Sounds like a basic game collision glitch. However, ...

 

Long War bug reports should be checked first in the "Long War" download page "Bugs section" and then in the appropriate Beta Feedback thread in it's "forum section" before posting to ensure a response. (The LW Team has stated they don't check the main forum at all anymore for problems. Really, the dev team is the most likely to be able to help with a LW issue but anyone else who can also will be there.) You may also find that the answer is already known and posted in those sections.

Be sure to read the "Readme" and "Detailed Troubleshooting" documents included with the LW download before reporting bugs. They need all the information requested there (including which OS platform: Windows, Linux, OS/X, ARM/IOS, etc.) to be able to help. If they can't reproduce the problem, they can't fix it. You increase your odds of getting help by re-reading included documentation and following instructions on reporting bugs, and then documenting what you have already tried ... in detail. Short "it's broke" reports simply generate requests for more detail; wasting time. Better too much detail than not enough. (Remember: This is all volunteer support, including the LW dev team. If you won't put in the effort to provide a good bug description, why should they spend time prying it out of you if it sounds vague enough to likely be something covered already?)

-Dubious-

Edited by dubiousintent
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...