Sign inCreate account
Support

Bug reports

Frosthold runs on an open source emulator, so there are bugs and there will keep being bugs. This page explains what happens to a report from the moment you write it until the fix reaches the realm, and where to send it so that road starts.

There are no in-game tickets

The help button in the client leads nowhere: nobody reads what is written there and no administrator will answer you inside the game. A report only exists once it leaves the client through one of the channels below.
Life cycle

The road of a report

Five steps. None of them has a promised date, and saying so up front is more honest than inventing a deadline that later goes unmet.

  1. 1

    You report it

    You write what you expected, what happened instead and how to repeat it. That detail is the whole difference between a fix and an “I could not reproduce it”.

    There is a template further down so you do not leave anything out.

  2. 2

    It gets reproduced and linked

    We try to repeat the failure on the realm. If it repeats, we look it up in the core project: most of them are known AzerothCore bugs and already have an open issue, so your report is linked to it instead of duplicating it.

    If it does not reproduce, we tell you and ask for what is missing. Nothing is closed in silence.

  3. 3

    Someone sends the fix

    The core is maintained by people outside the realm and the patch may land in days, in months or never. This is the step we do not control, and that is why no fix is promised here.

    Some emulator bugs have been open for years. That is not neglect from the realm: it is the state of the project.

  4. 4

    It reaches the realm on the next update

    When the core is updated, the fix comes in with the world restart. Updates happen in batches, not one by one, so a fix can wait in the queue even after it has been written.

    Restarts are announced in advance in the log whenever they are not emergencies.

  5. 5

    It is named in a log entry

    Every update is written up in News, with the specific bugs that stopped failing. If you reported something and it got fixed, you will see it named there.

    That is the only public acknowledgement there is, and it is on purpose: whatever gets fixed is put in writing.

Channels

Where each thing goes

Three different destinations. Sending a bug to the wrong channel does not lose it, but it does delay it.

Realm and game bugs

Quests that do not advance, spells behaving oddly, creatures that never spawn, anything that happens inside the game. It goes by email.

There is no public issue tracker for the realm yet. When there is one, it will be announced in the log; until then email is the only channel and we are not going to pretend otherwise.

hola@avsolem.com

Launcher bugs

A download that stalls, a verification that fails, an installer that will not start. The launcher does have a public repository and that is where it is reported.

A GitHub account is needed. In exchange the history is public and you can follow your report without waiting on anyone.

Open the launcher issues

Account, access and password

This is not a bug report: it is account support. If you forgot your password, you change it yourself with a link sent to the address you registered with.

The link expires in 30 minutes and works only once. If you no longer have access to that mailbox, then do write to us: that part is handled by hand and is not immediate.

Recover access
How to write it

A report that can be fixed

A bug that cannot be repeated cannot be fixed. Everything below exists so that whoever reads it can sit down and reproduce it without asking you again.

Template

Copy these six lines into the email and fill them in. Nothing else is needed.

CharacterName, race, class and level
WhereZone, dungeon or rough coordinates
What you expectedWhat should have happened
What happenedWhat happened instead
How to repeat itThe steps, in order, from the start
WhenRough date and time

Details that change everything

Four things that turn a vague report into an actionable one.

  • A screenshot with the chat visible: the message that explains the failure is usually right there.
  • The exact error text, written as it appears, rather than a summary of what it said.
  • Whether it always happens or only happened once. A repeatable failure is fixed far sooner.
  • The quest number or the spell name, if you have it at hand.

Never send your password

Not in a screenshot, not “so you can check it”, not in any report. No administrator will ever ask you for it, by any means. The full rule is in Rules.
Expectations

What this channel does not promise

Written up front so nobody sits waiting for something that is not coming.

  • There are no in-game tickets

    Nobody reads the client help form. If you use it, your report goes nowhere.

  • There is no public board with the state of your report

    This site does not track the realm’s open issues. The answer arrives by email, and the fix, if it arrives, is named in the log.

  • There are no deadlines or guaranteed priorities

    This is a non-profit project maintained by one person. Every report is read; not every report is answered the same day.

  • Not everything in the emulator can be fixed here

    When the failure is in the core, the fix depends on a project that is not ours. What we do is link your report to it and tell you when it lands.

Community

Where to ask before reporting

Does not exist yet

There is no open community space yet. This is a realm that just started and setting up an empty chat helps nobody.

When there is one, it will be announced in the log and it will appear here. Until then, questions and reports go to the same address.

A well written report is worth more than ten complaints, and at this scale it shows immediately.