Skip to main content

How can we help you?

Search

How to submit quality feedback and bug reports

Table of contents:

  1. Submitting a bug report
  2. Submitting a quality bug report
  3. Submitting quality design/game feedback
  4. Submitting general feedback

Submitting a bug report

  1. When in-game, hit the ESC button to open up the settings menu.
  2. Click on "Report a Bug".
    • Note: Do not click on "Support" as this will not generate the proper form and logs for our QA team.
  3. The bug window will then populate to fill out with the issue.
  4. Be sure the "Attach Player Data" and "Add Screenshot" are checked. 
  5. If the issue is preventing further gameplay/progression check the "Unable to Progress" button to make sure the issue is properly marked.
  6. For further information on what to include within a bug report please read the section "Submitting a quality bug report".

     


Submitting a quality bug report

Bugs are important to have visibility on so the development team knows what is impacting your experience. It's always best to use the in-game bug reporter, but make sure to provide additional detail in the bug report to make it most valuable. 

Below is a list of content that should be included with any bug report when possible:

  • Title: A descriptive title that summarizes the issue.
  • Reproducible steps: While these can't be included all the time, when possible, including these makes it easier for QA to test for the bug.
  • Expected result: What should happen
  • Actual result: What is happening
  • Visual proof: Screenshots, videos
  • Severity: How bad is the issue. Is it preventing players from playing the game or is it a level bug that allows players to play and is only an inconvenience?
  • Impact: How many players is this affecting?
IMPORTANT: Providing severity and impact is especially important to help development prioritize their time on bugs. These must be included as accurately as possible.

Example of a good bug report

Title: Players are unable to access/use their stashes
Reproducible steps:

  1. Launch Last Epoch.
  2. Load a character.
  3. Attempt to access your stash.

Expected result: The player's stash opens up, is accessible and usable.
Actual result: Player's cannot access or use their stashes.
Visual proof: [Video of gameplay where the player cannot access or use their stash]
Severity: Urgent. This is preventing player's from using a key system in Last Epoch.
Impact: All players are impacted not able to access their stashes.

Example of a bad bug report

Title: Game crashes.
Reproducible steps: It happens randomly, I don't know what I do when it occurs.
Expected result: No crashing.
Actual result: Crashing.
Visual proof: None provided.
Severity: Given that the crashing is random, severity is hard to determine. Not seeing a lot of other reports of crashing.
Impact: Not that impactful as it's not being seen widespread amongst players on forums, Discord, Reddit, etc.

 


Submitting quality design/game feedback

Design feedback focuses on mechanics of the game, systems, balancing, classes, quality of life and more. This type of feedback must be clear, concise, and, above all, actionable.

Below is a list of content that should be included with design feedback when possible:

  • Title: A descriptive title that includes what is being provided feedback on.
  • Critique: Clear and concise information about what the player is providing feedback on.
  • Suggestions: Clear and concise actionable suggestion(s) for improving what the player is providing feedback on.

Questions to ask when gathering design feedback to help fill out the above include but are not limited to:

  • What feature/content/system is being given feedback on? (Title)
  • What is it about it that was liked/disliked? (Critique)
  • What about it could be changed to make it better? (Suggestions)

Examples of good game/design feedback

Example One

Title: Judgement Paladins are way too overpowered.
Critique: When playing my Judgement Paladin, Last Epoch feels so easy and gets to the point where it's just boring and not fun to play because there is no concern of ever dying.
Suggestions: I would say look at the scaling of the Judgement Paladin that I have on my account. Perhaps there can be changes done to the damage or defense of the character class to help improve the challenge of the game.
 

Example Two

Title: Rogue class needs to be more powerful
Critique: Right now the Rogue doesn't seem to be strong enough to be played solo through the game as I experience repeated deaths while attempting to defeat bosses.
Suggestions: There are a couple options here that would work, but I think the easiest one would be to adjust the way the class handles armor and/or resistance to reduce incoming damage from bosses.
 

Examples of a bad game/design feedback

Title: Game is boring
Critique: Last Epoch is boring and not fun.
Suggestions: Make the game more fun.
 


Submitting General Feedback

Any other feedback that doesn't fall under the above may also be valuable for us to know. 

Below is a list of content that should be included with general feedback:

  • Title: A title that includes what is being provided feedback on.
  • Description: An outline of what it is the player is providing feedback on.
  • Suggestion(s): Clear and concise actionable suggestion(s).

Example of good general feedback

Title: Localization needs to be improved for Chinese
Description: While playing Last Epoch in Chinese, I notice that there are a lot of translations that don't make sense or are confusing to a native Chinese speaker. [Includes examples of translations that are confusing]
Suggestions: Review all the Chinese localization and make sure that what is being said is accurately representing what should be said.