A new way to see known issues

We’ve launched a public Bug Status board to give general visibility into issues that are known and being tracked. This is a new approach for us, and we’ll be closely watching how helpful it is for the community. If it’s not serving its intended purpose or creates more confusion than clarity, we may rethink the approach or choose to discontinue this format.

This board exists to answer one simple question: Is this issue known?

It’s meant to be a reference point for players, not a live development tracker. The information on the board is shared at a high level so you can understand what’s on our radar.

This board does not yet include every known issue. Some reports are still being reviewed, grouped, or documented, and they may be added over time. The board will continue to be updated and expanded as information becomes clearer.

A few important things to keep in mind about how this board works:

The board is informational only. It does not reflect real-time development progress, internal task lists, or priorities.

Updates happen when there is something new to share. Some entries may remain unchanged for long periods of time. This does not mean they are ignored, only that there is nothing new to communicate yet.

Not every reported issue will appear individually. Some issues may be grouped or summarized to keep the board readable and useful.

The board is curated by the Community team. It is not directly connected to internal development, QA, or support systems, and developers do not update it directly.

This is a work in progress. The board will continue to evolve as more entries are added and refined.

What the statuses mean

Each issue on the board includes a status to help set expectations.

Known and Monitoring: We’re aware of reports related to this issue and are keeping an eye on its behavior and impact. This means the issue has been acknowledged, reports are consistent enough to track, and no conclusions have been made yet.

Identified: The underlying cause or pattern of this issue is understood, but the timing of any potential change is unknown. This does not mean a fix is planned for a specific update.

Recently Resolved: A change related to this issue was applied in a recent update. Monitoring may still be ongoing, and this status reflects past changes only.

Needs More Information: We’re aware of reports, but additional details may help clarify when and how the issue occurs. This does not place responsibility on players, nor does it block internal review.

Some entries may include notes such as gameplay impact, visual only, platform-specific, or affects some players. These labels are informational and meant to help you understand whether an issue may apply to you.

About VOA Zone

We also want to speak about the Valley of the Ancients (VOA) Zone.

We know this has been one of the most frustrating issues for a long time, and we understand how disruptive crashes and instability in this area have been, especially for end game players.

The issue with VOA isn’t caused by a single bug. It comes from how the zone’s visuals and effects behave in memory as you move through the area, which can lead to instability over time across different devices. Because of this, fixes need to be applied carefully and incrementally. The team has been avoiding rushing large changes in order to reduce the risk of introducing new crashes or issues elsewhere, focusing instead on steady adjustments and testing rather than one-off fixes.

This work is active and ongoing and remains a high-priority topic. This issue has not been shelved or ignored, improving stability in this zone remains important.

If you’d like to stay closer to updates or take part in these conversations, you’re always welcome in the official Celtic Heroes Discord. Our community manager, Tiramisu, is active there and keeps an eye on feedback shared in the appropriate channels.

Thank you for sticking with us and for helping improve visibility around known issues.