Bug Reports

Vestra Coda is in early access, which means bugs are inevitable. Your reports are one of the most valuable things you can give us — every bug you take the time to document helps us build a better game. Here's how to do it effectively.

How to Report a Bug

Follow these steps to submit a clear, actionable bug report:

1. Check known issues first. Visit the roadmap page to see if the bug has already been reported. No need to duplicate effort.
2. Gather your information. Before writing the report, collect the details listed in the section below.
3. Submit the report. Send it via email or the in-game command (details below).
4. Be available for follow-up. We may reach out if we need more details to reproduce the issue.

What to Include

The more detail you provide, the faster we can track down the issue. A good bug report includes:

• Game version: Found in the bottom-left corner of the main menu or in Settings > About.
• Steps to reproduce: What exactly did you do before the bug occurred? Be as specific as possible. "I opened my inventory, clicked on a potion, then dragged it to slot 3" is much more helpful than "potions are broken."
• Expected behavior: What should have happened?
• Actual behavior: What actually happened instead?
• Screenshots or video: A picture is worth a thousand words; a video is worth even more. Screen recordings are incredibly helpful for visual bugs, animation issues, or anything timing-related.
• System specs: Your OS version, GPU, RAM, and driver versions. This is especially important for crashes and performance issues.
• Frequency: Does this happen every time, or only sometimes? Can you reliably reproduce it?

Where to Report

• Email: Send your report to bugs@vestracoda.com. Include "Bug Report" in the subject line along with a brief description (e.g., "Bug Report: Inventory items disappearing after trade").
• In-game: Use the /bug command to open the in-game bug reporter. This automatically captures your game version, character info, and recent log data, making it the fastest way to file a report.

Bug Severity Levels

We categorize bugs by severity to prioritize fixes. Here's how we think about it:

• Critical: The game crashes, data is lost, or a security vulnerability exists. These get immediate attention and emergency patches.
• Major: Core functionality is broken — a skill doesn't work, an entire area is inaccessible, or a common action produces wrong results. These are prioritized for the next patch.
• Minor: Something doesn't work quite right, but there's a workaround. Incorrect tooltips, minor calculation errors, or non-blocking UI issues. These go into the regular development queue.
• Cosmetic: Visual-only issues — typos, misaligned UI elements, texture glitches, or animation hiccups. They don't affect gameplay but we still want to fix them.

You don't need to assign a severity level yourself — just describe what happened and we'll triage it. But if you think something is critical, say so. It helps us prioritize.

Known Issues

Before filing a report, check the roadmap page for our current list of known issues. If your bug is already listed there, you don't need to report it again — but if you have additional reproduction steps or details, those are always welcome.

Thank You

Seriously — thank you. Early access development depends on players who care enough to report problems instead of just walking away. Every bug report you send makes Vestra Coda better for everyone. We read every single one, and even if we can't reply to each individually, know that your report matters and will be acted on.