FRONTIERS

FRONTIERS

Not enough ratings
How to Submit a Bug Report
By railboy
This is how you submit a bug for the FRONTIERS beta. Read carefully!
   
Award
Favorite
Favorited
Unfavorite
Part 1: Accessing the Bug Report discussion in-game
If you're not familiar with accessing the Steam community in game, don't fret! It's super easy. While you're playing FRONTIERS, just hit SHIFT+TAB at the same time and you'll see this:

CLICK TO VIEW SCREENSHOT[i.imgur.com]

To post a bug, click DISCUSSIONS and proceed as though you're working in a web browser. To see this guide, just click the How to Submit a Bug Report item.

Mouse Cursor Bug Workaround
When you hit ESC to return to the game, there's a chance that the mouse cursor will get stuck. If it does, Alt-TAB out / back in to the game and control will be restored. I'm working on this bug.
Part 2: Writing the report
Thank you for the time and effort you are investing to find and report bugs and ultimately make Frontiers a better game. Seriously you rule.

If you think you've found a bug, this is what to do, in order from most to least important.

1) Post in the right thread / discussion
Bug reporting level: Good
  • Please check if it has been reported before. In that case it is more useful to add your information to the existing topic about it.
  • Only one bug per topic. If you report 5 different ones in the same post then some will inevitably get lost.
  • If there is only one bug, this topic can eventually be marked as FIXED and this will hopefully prevent lots of double reports.
  • And if you have additional or more accurate information about it, by all means add it to the topic!

2) Describe the Bug In Full Detail
Bug reporting level: Super
Be specific.
  • What were you doing? Did you have an active quest? What weapons were you using? Were you in a house, near a waypoint marker?
  • This is CSI Frontiers. You collect all the data you can but you can not know which trivial detail will convict the suspect.
Bonus round: provide the exact steps to reproduce it. If you can reproduce it in a new game, that's super awesome. If you can only reproduce it in your savegame but not in a new game, that's still a huge help.

3) Attach a log file
Bug reporting level: Elvis
Frontiers Log files are found in:
WINDOWS: [Program directory]\FRONTIERS_Data\output_log.txt
OSX: ~/Library/Logs/Unity/Player.log
Linux: ~/.config/unity3d/AADProductions/FRONTIERS/Player.log
If they are short, just copy/paste them into the report. Otherwise use pastebin: http://pastebin.com/
If they are too long for pastebin, email them to frontiers.game@gmail.com

4) Provide system info
Bug reporting level: Grand Master
Not all issues are hardware related but if you are not sure, please include this additional information. If you're tech savvy you know the routine, of course, but for everyone else:
On Windows systems you should have a "My Computer" icon on the desktop. Right-click it and select properties. Now you can see:
  • Operating system. (like Windows 7 Professional)
  • Type of system. (32 or 64 bit)
  • Amount of Installed memory. (like 4,00 GB)
  • On this window you should also have an entry for "Device Manager" on the top left. If you click that, you can look up your...
  • ...Graphics Card. Very important.

5) Follow up
Bug reporting level: God among insects
If you encounter the same bug again, follow up with another post in the same thread.
Bonus round: if you verify that the bug has been fixed in a later build, follow up and confirm in the original thread.

6) Be patient
Bug reporting level: Steve McQueen
I am but one developer. Bugs take time. Bugs that seem like they should be simple to fix often aren't. If you can wait patiently without posting things like What's the holdup? and This shouldn't be that hard! then you have achieved a level of bug-testing known to only the few and great.

The difficult part about fixing bugs is not the knowing that they exist - it's finding out why and how they occur. That's the reason why we are asking for such a lot of information.

That's it! And now... good hunting! :)
5 Comments
railboy  [author] 22 Apr, 2017 @ 7:45pm 
That depends, does -everybody- include yourself?
Old Man Shadowdark 22 Apr, 2017 @ 4:20pm 
Also, I killed -everybody-. Guild master, Settlers, Quartermaster, chickens, everyone. I hope this doesn't affect my ability to complete the game. ; )
railboy  [author] 18 Aug, 2015 @ 10:01am 
Because game dev is an endless game of whack-a-mole :steamfacepalm:
PKodon1618 17 Aug, 2015 @ 6:08pm 
And, if you figure out how to fix the bug you're fixing, then you have to figure out why and how some new bugs show up when you do that :)
log1 23 Dec, 2014 @ 7:36pm 
Thanks for this guide, this should standard practice for every game!!!:Mstar: