Bug Report Best Practices

 

Please note: We mainly use our bug report form as an ingest for bugs, as most don't require a response. If you need to receive assistance, please reply to the ticket and it will automatically be escalated to a support agent for further help.

 

5.png

CLICK HERE TO SUBMIT A BUG REPORT

5.png

To help ensure that your bug report is comprehensive and complete, it is highly recommended that you follow these guidelines:

Ticket Subject

Write a concise summary that clearly states the problem. Try to avoid statements like “Help!”, “It doesn't work”, “It’s broken”, or “There’s a bug”, and instead use a short phrase to accurately summarize your issue. You may find it helpful to think about what you would search to find help for the issue.

(i.e. Players can phase through Dragon statue in Calming Incense quest) 

Type of Bug

Pick the one that fits best from the list of bug types:

  • Social (Friends, Communities, Chat, Parties)
  • Skills (Bug Catching, Cooking, Fishing, etc.)
  • Gameplay (Accomplishments, Housing, Tools, Inventory, etc.)
  • Lore (Quests, Friendship, Romance, Gifting, etc.)
  • Clipping, Visual Issues, Collision Issues
  • Other

Depending on which selection you pick, a new set of options will appear. Please select whichever is closest to the issue you are reporting.


Description - Information about the bug/issue

To better help you in addressing your concern, Player Support needs to gather information about the issue that you are experiencing. Here are some guide questions on the type of information PS mostly requires. 

  • What platform were you using? (Switch, PC, etc.)
  • Can you provide steps to replicate the issue? / Can you describe the issue?
  • What were you doing when you experienced this issue?
  • How many times has the issue happened?
  • Did relogging help with the issue?  


Depending on the nature of the bug/issue, you might get asked a few more questions during your exchange, but the questions outlined above are the typical exchanges that usually happen when writing a ticket to Support.

Expected Result and Actual Result

After listing the steps, clearly state what happens, and what you believe should happen.

Include the exact text of any messages (e.g., error messages) that appeared at the time of your issue.

Attachments - Screenshots and Logs

Other than a detailed description of the issue, attaching screenshots to the ticket can also help to showcase the issue more clearly. 


Screenshots: 

Players can phase through Dragon statue in Calming Incense quest

Bug sample.png

 

(Depending on the issue you are experiencing specifically lags, crashes and freezing, you might need to submit Palia Logs and DXDIAG for Dev team to investigate the situation)

Palia Logs:

  • Press [Windows Key]
  • Type "File Explorer" and hit [Enter]
  • Paste %LocalAppData%\Palia\Saved\Logs into the file explorer and hit [Enter]
  • Highlight all of the logs
  • Right-click and select "Compress to ZIP file"
  • Attach the zipped log file to the ticket

DXDIAG:

  • Press [Windows Key] + R (this will open up a "Run" window)
  • Type "dxdiag" and hit [Enter]
  • Click "Save all information" and save the file
  • Attach the file to the ticket


Review

Take your time. Read over your bug report to make sure you didn’t leave out anything and that everything is clearly explained.

 

REMINDER:

As stated above, Bug Report tickets will be sent an automated response. However, Player Support may reach out to you incase they need to gather more information about the bug/issue that you had reported.

Also, if you happen to require further or immediate assistance, you can send a reply after receiving the automated response and Player Support will get back to you as soon as we can.  

Was this article helpful?
243 out of 291 found this helpful