Reporting Bugs

Mobile Devices

To report a bug while playing Path of Titans, tap the bug button at your top left. All game crashes are automatically sent and reported.

Android users experiencing performance issues and crashes are encouraged to fill in our Device Survey which will let our developers know there is a problem with the game on your device. Click here to access the survey!

All Platforms

If you've found a bug, issue, or exploit in Path of Titans, the best way to report it is through our Bugtracker Website.  Bugs reported here are directly connected to the tools used by our development team, making them much easier for us to process. Reporting bugs, issues, and especially exploits can earn you a Bugtracker Skin! For more information on these rewards and how to earn them, please visit the Bugtracker Skin Support Article.

1. Visit our Bugtracker Website

2. Log in to your Alderon Games account.

   • Authorize the Bugtracker if it is your first time logging in.

3. Use the search field to find if your bug has been reported before. 

   • Try keywords related to your issue such as: stuck, floating, texture, etc.

   • Upvote identical and similar reports to show you are also affected!

   • Add any missing or additional information you may have to the existing report.

     • Adding information to a pre-existing bug report may still qualify you for a Bugtracker Skin! Submitting duplicate reports may not.

4. If your issue hasn’t been reported yet, click the blue 'Report A Bug' button next to your username.

5. Read all the attached information provided on the screen and the available fields.

6. Fill in the bug report form:

   1. BUG TITLE: Briefly explain what the bug is and what you were doing when it happened.
      Example: Getting attacked by Allosaurus in Green Hills as a Juvenile Camptosaurus freezes you in place.

   2. CATEGORY: Select the area the bug is affecting. 

      • If you are reporting an exploit, make sure to select the category Exploit so staff can identify it among other bug reports.

   3. BUG DESCRIPTION: Briefly describe what the bug is and what you were doing when the bug occurred.
      Example: I was playing a juvenile Camptosaurus running through Green Hills when an Allosaurus ran up and bit my tail, causing me to freeze in place. The bug only happens in Green Hills and if you are a juvenile Camptosaurus.

   4. OBSERVED OUTCOME: Describe exactly what happened when the bug occurred.
      Example: My Camptosaurus couldn’t move or use abilities/emotes until it was killed.

   5. EXPECTED OUTCOME: Describe what should have happened instead
      Example: I should have taken damage but remained mobile and able to run or fight back.

   6. REPRODUCTION RATE: How often did the bug occur? Use a percentage if possible.
      Example: “75%” (Bug occurred in 3 out of 4 attempts).

   7. REPRODUCTION ATTEMPTS: Enter how many times you have tried to encounter or trigger the bug.

   8. REPRODUCTION STEPS: Describe what we need to do to encounter the bug in-game. Press the blue '+ ADD STEP' button to add more steps.
      Example: 

      1. Enter official matchmaking on Gondwa.

      2. Select or create a juvenile Camptosaurus.

      3. Go to Green Hills.

      4. Have an Allosaurus of any growth stage attack your tail.

   9. GAME BRANCH: Select the game branch where you found the bug. The Production branch is the default game branch. Always select the Production branch if the bug is found on both Production and the Public Test Branch.

   10. GAME VERSION: Provide the game version number. This is very important! This is shown:

       • In the main menu, next to the game title.

       • In the Alderon Games Launcher above the news.

              

   11. PLATFORM: Select the platform you found the bug on.

   12. HARDWARE DETAILS: Enter any hardware information related to your bug. This depends on your platform.

       • Android/iOS/Handheld: Device brand and model.

       • PC:  Key hardware specs (CPU, GPU, RAM).

       • Controllers: Brand and model (especially 3rd-party or mobile/PC controllers). 

       • Modified devices: List any custom modifications that may affect replication.
       • Anything extra you believe our staff should be aware of.

   13. VIDEO EVIDENCE: (Optional but Strongly Recommended)
       Upload a video showing the issue in action. This is the best way to help staff understand and reproduce the bug.

   14. PICTURE EVIDENCE:  (Optional)
       Upload screenshots. These are also helpful, though may show less than video.

7. Click on the blue 'SUBMIT BUG' button at the bottom right. Done!

You can now locate the bug you reported in the My Reports tab! You can add additional information to your bug at any time as well as replying to comments from other users or staff.