The bug reporting system is not the place to report suggestions, missing/incomplete features, or polish issues.

These are the kinds of things you should report:

• "When I place an embellishment on another embellishment, the game crashes."
• "The game gets stuck on a black screen when I try to make a new save file."
• "The game crashes on launch when I try to run it from the D:\ drive."
• "The game freezes when I click the 'pleasure self' button."

These are the kinds of things you should NOT report:

• "I cannot give the test subject a blowjob."
  This is a missing/incomplete feature, not a bug.
• "Character models are jittery and look like they need more polygons / better textures."
  This is a polish/content issue, not a bug.
• "I can't import my old characters into the newest version."
  This is an intended/expected behavior, not a bug.
• "The laboratory is too dark."
  This is a missing/incomplete feature, not a bug.
• "The game crashes a lot."
  This might be a bug, but it is not specific enough to be useful (unless you include an error log!)

Before submitting a new bug report, search the existing bugs to see if your bug already exists.

If you find your bug, you can use the "Add Note" function to leave a comment / let me know that you're also experiencing the bug. The more people commenting on a bug, the more likely I am to investigate it quickly.

If possible, try to include an error log with your note!

If your bug hasn't already been submitted, now's the time to submit your bug!

Here's an example of a good bug report:

When submitting a bug report, it is very helpful to include an error log as an attachment.

On Windows, the error log is a text file located near the game's main program file:

On Mac, the error log can be found at: ~/Library/Logs/Unity/Player.log

On Linux, the error log can be found at: ~/.config/unity3d/Fek/Rack 2_ Furry Science/Player.log