Bug Reporting

If you’ve discovered a bug in EVE Frontier (yes, it happens!), you can help Fenris Creations fix it by submitting a bug report.
The preferred way is directly from the client by pressing F12 and selecting “Report Bug”.
Alternatively, you can submit one outside the game here: Submit a request

This guide explains when to submit a bug report and how to write a high-quality one.

 Before writing a bug report

• Customer Support: Bug reports are not the same as support tickets.
  Submitting a bug report to request assistance or reimbursement will not work, as these reports are never reviewed by GMs or the support team.
  If you need help from a GM, please submit a support ticket via the support site
• Exploits: Found an exploit that players are abusing (or could abuse)?
  Please submit both:
  • A bug report - to help the team fix the issue.
  •  A support ticket  - for quick action and follow-up on exploit consequences.
• Check Your Side: Before reporting a bug, verify whether the issue may be resolved locally.
  • Update your drivers - especially graphics drivers.
  • Clear your client cache, which often resolves unexpected behavior.
• By Design: If your concern relates to game balance, design, or general opinions, not an actual defect; please share your feedback on our Discord Feedbacks Channel and not through a bug report. 

Bug reports are normally not seen by game designers.

• Multiple Problems: If you encounter several issues, submit separate bug reports for each one.

How to write a good bug report

Title

A good Frontier Bug Report (FBR) title is short, clear, and descriptive.
It should explain:

• What the bug is

• Where it happens

• Under what conditions it occurs

Starting with a location or keyword helps QA sort reports more easily, such as “Exploration”, “Chat”, “Blockchain”, “Structure Name”, etc.

Example:
"Summary: Unable to interact with Portable Refinery"

Category

Choose the correct high-level category for your issue:

• Gameplay: Mechanics, logic, and intended feature behavior.
  Includes all English spelling errors.
  Examples: Ship or module attributes and manufacturing etc.
• PVE: Issues related to in-game environment content.
  Examples include Sites and Structures, and Exploration activities.
• UI: User interface behavior and functionality.
  Examples: Drag & drop issues, window scaling, sorting, transferring items to structures.
• Graphics: Visual issues excluding UI.
  Examples: Incorrect ship models, lighting issues, effects not displaying.
• Technical: Client performance and stability issues.
  Examples: Crashes, freezing, cache problems, hardware-related issues.
• Audio: Any sound-related issues.
  Examples: Environment music, missing effects, UI audio feedback.
• Launcher: Issues with updating or validating the client.
  Examples: Launcher failing to update, corrupted client files.
• Wallet: Blockchain-related issues.
  Examples: Problems with Assemblies, Smart Structures, or chain interactions.

Description

Provide a detailed explanation of the issue and the conditions under which it occurs.

A strong description should clearly outline the following:

• What happened: Describe the exact behavior you experienced.

• What you expected to happen: Explain the intended or normal outcome.

• Where it happened: Include the Region or System involved.

• Specific settings or conditions: Note any configurations, UI options, Modules, or actions that may influence the bug.

• Severity of the issue: Indicate how much it affects gameplay or functionality.

• Frequency: Mention whether the issue occurs consistently, occasionally, or only happened once.

If the issue involves Assemblies, chain functions, or wallet interactions, make sure to provide Assembly IDs or any other relevant identifiers.

For graphics-related issues, remember to include your graphics settings.

Reproduction steps

The most valuable bug reports include clear, repeatable reproduction steps.
Try to reproduce the issue and outline the simplest series of steps required to trigger it.

Write these steps clearly and in chronological order.
This allows the QA team to reproduce and fix the bug effectively.

What else is needed for a useful bug report sent through the website?

Providing extra files can significantly help QA verify and resolve your bug:

1. Screenshot of the bug – important for UI or graphical bugs.
2. DxDiag file (Windows only) – important for technical and graphical bugs.
3. LogLite log – very helpful to see if any errors were logged.
4. Crash dump - if it’s a crash and a crash dump was generated.