Error Messages

Sometimes, the player may encounter errors in Tales of Link. Unfortunately, most error messages are not very descriptive, often just saying "An unknown error has occurred," or giving the same error code for all errors (Error 10001). The errors may appear for several reasons and are usually easily resolved.

Errors Installing/Updating
Most errors from downloading are met with An Unknown Error Has Occurred, Unexpected Error, or Connection Failure. The error is non descriptive, so many steps may need to be taken to determine the cause.

Because of the size of the game, the system should have around 2 gigabytes of space free. When downloading the game for the first time or reinstalling, device space is often the main cause of downloading trouble. When installing updates, a large amount of disk space may also be required, so the first step in troubleshooting should always be to check the amount of space available on the device.

Assuming the disk space is not the issue, the download may also fail if the player's internet connection fails during the download. Retrying the download will often work, but if the download is taking more than 3 tries, the SD card may be to blame. Tales of Link ideally should install data on the SD card, but many have reported issues with the download with the option available. Attempt to remove the SD card and try the download again.

Immediate Game Crashing
If the game immediately crashes, the download may have been corrupted. This error may also come with an Inventory Get Error before crashing. Attempt to reinstall assets first if the game has previously been installed, especially without a transfer code or Facebook binding.

If a simple reinstalling of assets does not work, attempt to remove the SD card as indicated in the Download Errors section and try again. Should these steps fail, a last resort would be to reinstall the game itself.

Verification Error
A verification error occurs if the system clock is not properly synced. The player will not be able to pass the title screen until the clock is synced. This is to ensure all events start and end at the same time, as the game runs on the system clock. An option to change the system clock should be available in the device's time and date settings.

Slow Loading Pages
Often the game will load menus, inventories, parties, etc. slowly. This is especially problematic for large inventories of units, items, or gear, or on pages that are very long such as the Hero Index. Unfortunately, the lag will happen regardless of device specifications. Usually the problem continually worsens until the game is restarted, so remember to close the game often.

Game Crashing/Screen Blacking
The game may often crash on pages that were already slow to load, especially when the player is performing actions which require more menu usage. Common menus affected are using items on units, limit breaking units, upgrading gear, or fusing gear. Typically all previous actions are saved when the game has crashed. Similar to the slow loading pages issue, it is an unavoidable problem.

The Transmitted Data is Invalid
This error is rarer, often caused by the game syncing improperly with the servers. This is most often displayed after using herbs too quickly on units. Simply restarting or forcing the server to sync by performing another action should fix the error. No herbs would be lost.

Game Crashing/Sudden Closing
Oftentimes the game will suddenly close during battle, particularly during graphic-heavy scenes such as Overlink Artes or Mystic Artes. The battle may be resumed from the current turn when the game is reopened, though the turn may need to be replayed. Oftentimes, this is accompanied by a Record Not Found error, as detailed in the Errors After Battle section.

If an Inventory Get Error occurs during the battle once the game has crashed, resuming the battle may result in the error again. If the error persists, the battle may need to be discarded to fix the error.

Disappearing/Black Box Units or Displays
Units may disappear randomly or be replaced by black boxes if the game has been left to run for too long on a system. The black boxes may also affect any graphics, including enemies, guardians, attacks, and all text. This error is easily resolved by simply restarting the game.

Lost LC
LC may be lost in two different situations. If the game has crashed after using an active skill and the battle round resets, the active skill's LC may be lost. If an active skill is used between battle rounds, LC may also be lost without any effect. Both losses in LC are permanent.

An Unknown Error Has Occurred
This error is often displayed when too much time has been taken to complete a stage. The error will display instead of showing results, and the battle may look incomplete once the quest stages are loaded again. Fortunately, the error is a false alarm. Simply playing another stage or restarting the game will reload the system, and all rewards and clears will be displayed.

Record Not Found
A "Record not found" error will display typically after the game has crashed at the end of a battle. The error will result in not being able to see quest results, but like the previous unknown error, it is not an actual error. The results are still saved, and all rewards and clears will still be applied. If they are not immediately visible after the battle, then restarting or playing another stage will force their appearance.

Inventory Get Error
This error is rare, and the cause is unknown. Typically restarting the game fixes it, though sometimes redownloading all assets is necessary if the error persists.

Errors Transferring to the Same Device
Assuming password or obvious code errors are not to blame, an error may occur transferring an account while on the same device the account was previously on (such as during a reinstall). This error can be worked around by transferring the account to another device first, such as on an emulator, and then transferring it again to the proper device. Consider this option first before using a one-time only transfer code, as the code may not work again even if an error occurs preventing it from being used properly.

Transfer Code Errors
Transfer codes only work once and expire after 30 days. The most common issue with codes is simply reusing the code or trying to use it after expiration. With any errors with transfer codes and no Facebook binding, contact support to regain access to the account. Every transfer code error unfortunately means the code no longer will work, even if all steps have been correctly followed.

Errors With Purchases
Please contact support immediately for any purchase errors. The staff will find a way to resolve the problem.