Bogi

---

Run into a bug or an error? Chances are, someone may have already reported it. Make sure you use Forum Search before making a thread, searching in Bug Reports and Help Center to see if anyone else has made a thread about it.

This guide covers some basic troubleshooting, reporting etiquette, and a list of commonly run-into errors.

Troubleshooting Tips
Before you make a thread about your bug, you should try the following troubleshooting steps:

• Clear your cache. A lot of issues people run into that appear to look like a bug can be solved with clearing your cache. Not sure how to clear your cache? Check this article for information.
• Clear your cookies.
• Manually log out and back into the site.
• Try using Incognito mode.
• Disable any extensions you have running, especially any antivirus browser plug-ins.
• Try using a different browser. It is recommended that you use a different 'base' than the one you're using. For example, if you're using Google Chrome, try using Mozilla Firefox.

When Making a Bug Report
It is incredibly important that you include as many details in your bug report as possible. Including details about your devices, the steps you took before running into the error, etc. helps the engineers immensely when trying to make fixes. Simply pasting an error is not enough.

When you're making a bug report, please include the following:

• What were you doing before the error or issue occurred?*
• What device are you using? E.g., a laptop, an iPad, a Samsung S6 phone.
• What operating system (OS) are you running? E.g., MacOS, Windows 10.
• What browser are you using? E.g., Google Chrome, Mozilla Firefox, Brave, etc.
• Is your browser up-to-date?
• What antivirus do you have installed, if any? E.g., Malwarebytes, Bitdefender, McAFee, etc.

Here's an easy to use template you can copy and paste for your report:
*Please be sure to list what you were doing before running into your problem. If you don't, the only information that the engineers have to work with is an error message and device information if you choose to include them. Visual bugs such as gene and apparel errors do not needs steps. A good rule of thumb is that if you run into a page with an error message on it, you should include steps.

Examples of Good Bug Reports and Bad Bug Reports
(All of these reports were written up by myself and any references to existing threads are not intended.)
This is an example of a bad bug report. There is minimal information included in the thread title which is poor forum etiquette and the body does not contain much either. Those who are familiar with with commonly reported issues may be able to figure out what occurred here, however it is not best practice to rely on others who may or may not know what you've run into.

This one is a little bit better than the above. The post only contains an error message, however it is detailed enough to give the engineers a start at figuring out the root cause by providing the error itself and a relevant URL. This bug report can be improved by including steps prior to running into the error and device/troubleshooting information.

This is a good example of a bug thread! In this report, there is information on what the user was doing leading up to discovering the error. They include the link as well as device information and any troubleshooting that they attempted. This would help the engineers best figure out what is the problem.

For those wondering, threads that have been moved get a new URL based on the board they're in, which would be the answer behind this one!

Masterthreads
Some errors have their own dedicated thread to keep all similar errors together in order to prevent flooding.

• Apparel artwork errors: [T] [Art] Apparel Problems
• Dragon Gene & Eye Color errors: [T] [Art] Incorrect Gene Colors (Currently locked for review.)
• Skin & Accent problems: [T]Skin and Accent Problems
• Typos, grammatical errors, & textual errors: [T] Typos MEGATHREAD!

Common Bugs & Errors
Site components not loading
E.g., the red stripe where food points are listed.

Clear your cache.

Can't equip familiars
Only one copy of a familiar can be equipped to a dragon at a time, no matter how many copies you have.

"An error has occurred" when trying to list on Auction House
Make sure you toggle the correct radio button when making a listing. If you have treasure selected but put the price in gems, you will get this error.

Fairgrounds isn't awarding money
Fairgrounds awards a maximum of 75,000t a day.

Currently, FR is divided into two domains: www. and www1. This is because the site is currently undergoing a site-wide refactor to bring code up to modern standards. Finished portions of the site are ported to the www1. subdomain while unfinished ones remain on www. These domains need several minutes to communicate sometimes, meaning your treasure amount may appear inaccurate on some pages but not on others.

Can't breed dragons
Make sure the dragons you're trying to breed have at least 40 energy and are not on a breeding cooldown.

Additionally, Ancient breeds (which are marked with a on their profile) can only breed with their own species, meaning cross-breeding is not allowed. For example, Gaolers can only breed with other Gaolers.

Color search isn't working
When determining the range of colors to search for, the site looks at the shortest range between your two selected colors. For example, if you search Maize<->Pearl XXX dragons expecting to get the whole wheel, you'll find you only see Maize and Pearl dragons, because on the color wheel, the two colors are right next to each other.

This "shortest-range between two colors" is also how breeding works for colors.

Site assets are blocked / Coliseum enemies won't load
These have the same fix.

Whitelist FR (both the www. and www1. domains) on your antivirus. Sometimes your antivirus will block site assets with an ID of repeating digits (for example, Glowing Embers has an ID of 888 and may be seen as suspicious).

Can't feed dragons despite having food
Make sure your food is converted into food points. You can do this by going to your Hoard.

Errors with 'deadlock'
See this article to learn more about deadlock errors. Put simply, they're not anything you should be worrying about. Just refresh and continue.

Error 400
See this article for troubleshooting tips.

Error after logging in / using Baldwin (includes 'filters.php')
Refresh the page. If your item is brewing, it means you double clicked a button twice.

Baldwin countdown timer is incorrect
Refresh the page. Visual errors occur with items with a high time, including Bogsneak items and Prismatic tokens.

Hoard search is gone
Hoard search is off by default and occasionally may reset. To get it back, click the spyglass in the top left corner next to the 'Food' tab.

Can't equip battlestone to a dragon
Some battlestones have a minimum level requirement in order to be used. You can check a level requirement in the stone's tooltip.

Signature cuts off at the bottom
Using columns shaves off a few pixels from the bottom of your signature. To avoid the automatic cropping, resize your images to be around 97px in height or smaller.

Marketplace resets to page 1 after purchase
Not a bug.

Game Database genes lead to Specialty
Being looked into.