After clicking on the Bug Box button, you'll be taken to the Bugbox tab within the Bug Box. At the top of this page, you will find Your Bug Reports. This is where the reports that you have created will be logged.

Underneath Your Bug Reports, you will find Newest Bug Reports. Newest Bug Reports showcases the 5 most recent reports made to the Bug Box.

The Bug List is the official list of all reports that have been made to the Bug Box. There are two ways to get to this list, the first being the Bug List tab featured at the top of the Bug Box page. Alternatively, you can select View All at the bottom of the Newest Bug Reports section.

Both options will bring you to the current list of pending bugs. These reports are automatically displayed by most recent activity!

If you're looking for an existing report, you'll want to use the Filter tool. You can find a brief overview of what these filter options mean below.

• Title contains...: Input words that you believe may be related to the bug that you're looking for. If a very specific word brings no results, try a vague term instead!


• Categories: Select a category from this dropdown to help narrow down your search, such as if the bug you're looking for is art-related vs grammar-related!


• Priorities: If you'd like to search by report urgency, select from this dropdown. However, this is not recommended if you're trying to find an existing report for a bug that you're experiencing.


• Statuses: Search by report status (e.g if a fix is in progress).

Should you instead wish to view reports with the longest period of inactivity first, click Bug Info. Click it again to restore the previous display order!

In the instance that you have found an existing report via the Bug List, click on its title to be taken to the full report. Should there be more than one report, select the oldest one!

If the original report or existing comments cover all of the same information that you'd provide, select "I am experiencing this bug!"

If you have new information to add, select "I am experiencing this bug!", and scroll down to the comment field. Here you can provide any additional information that you have, as well as screenshots!

Once you're done, select Comment, and you'll find that your comment has been published to the existing report. You cannot edit your comments once you have posted them. If you have a correction to make or information to add, you'll need to comment again.

If you have not found an existing report, you're in the clear to create one. To do this, select Report a Bug.

You can see that there are a lot of empty fields to put information into. It's alright if your report isn't 100% accurate, just try your best!

• Give a title to your bug report: This should be a short but direct summary of the bug that you are experiencing. Vague titles are not helpful to other users or our coders, so please try your best to be descriptive!


• Please describe the bug that is happening: Keep this a direct "step-by-step" explanation, like you're writing up an instruction manual.


• What is the expected behaviour for what you have experienced?: Write what you believe should be happening.


• Are there any error messages? What are they?: If you encounter an error message, put a direct paste of the error here. Account creation or linking errors should NOT be reported here; you'll want to use the Modbox instead!


• Are you able to reproduce this bug when you try the action again?: Select yes if you can get the bug to occur more than once. Select no if you cannot, whether that be through attempting the same action, or if you simply do not have the ability/assets to do so.


• Upload screenshots: If you have screenshots of the bug itself, upload them here. Do not upload screenshots of each step that you took for it to happen; all that's needed is a visual of the bug.


• Please include any links that might be relevant to this bug: Include links to any relevant pages, such as a direct link to a lion, or a URL that contains search filter results.


• Please pick the category that best fits your bug report: Pick what you believe is the most relevant category for your report.


• Please choose a priority for this bug report: Select what you believe to be the most accurate representation of urgency for your report.


• Your device: Manually type in your device type.


• Your browser: Manually type in the browser that you're using.

When you have finished writing up your report, select Report Bug!

If your bug meets the Modbox report requirements that are outlined in the Before Making a Report section, then you can report it to the Modbox using Serious Bug as your ticket's topic. As a result of selecting Serious Bug as your ticket's topic, you will be provided with the following dropdown menu:

• I need an item replaced due to a bug: For if you did not receive an asset accordingly (currency, items, lions, etc) while using a gameplay feature as intended, such as the Trading Center.


• I need a lion reset due to a bug: For if you're unable to use a lion as intended; such as being unable to send a lioness on a hunt, or conduct a trade after a lion's cooldown has ended.


• I need to report an exploit: Exploits are bugs that allow you to gain an unfair advantage; such as being able to buy an asset from an Event Shop without losing Event Currency, or bypassing a cooldown. If your bug qualifies as an exploit, select this option, and avoid recreating it.


• I have a question regarding a bug or exploit: For if you're unsure whether or not what you're experiencing is a bug/exploit.


• Other: For if your bug does not fall into any of the other "why" categories. An example of this would be being unable to access your Den Page, or another core feature.

If your bug turns out to not be a bug, or gets fixed, you can thankfully manually change your report's status yourself. To do this, look to the top of your report, and select one of the following buttons:

• Mark as "Not a Bug": If you discovered or were otherwise informed that what you are experiencing is not a bug, select this option, and your report will automatically close.


• Mark as "Fixed": Should the bug appear to be fixed, select this option, and your report will automatically close.

Near the bottom of your bug report, you will find a dropdown menu with a handful of different notification options. These options will help filter when you get notifications related to your bug report, if at all!

• "Notify me for ALL responses or if the status of the bug changes"
• "Notify me if an admin comments or the status of the bug changes"
• "Notify me ONLY if an admin comments"
• "Notify me ONLY if the status of the bug changes"
• "Do not notify me"

Simply select one of those options from the dropdown menu, and then press Update.

If your bug report has a "pending" status, it will be eligible to auto-close 1-month after its creation date. You will receive a notification 2-weeks before this happens, in which you will be asked if you are still experiencing this bug.

• Yes: Your bug report will be removed from the auto-close queue, and will remain open until an Admin handles it.


• No: Your bug report will be marked as "fixed", and will automatically close.


• If your bug is an event bug, it will be given 12+ months to its auto-close date, in which you will receive a notification 2-weeks before your report reaches 13-months.

If you do NOT respond to this notification, your report will automatically close on its relative close date.