-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
You may encounter errors or (hopefully not) bugs and glitches with the bot. Even though every effort has been done to patch and remove bugs, obviously some will remain. Below is a list of types of errors/bugs and how to deal with them.
Tip! Use CTRL+F to search for the error you are experiencing.
These are bugs that happen when the bot is actually running.
Please start the launcher and run the bot from there (err_launcher001)
The launcher was detected as not being started. Make sure it is open when the bot is running.
Please launch the program from the launcher 'Start' button. (err_launcher002)
You must log in and connect before launching the bot.
IdealTF or IdealTF config is not installed. (err_launch001)
The program does not appear to be correctly installed as some core files and folders are missing.
Config does not exist. Please log into the bot if you haven't already (err_config001)
Config files were not made, this can be caused by closing the Launcher down and reopening it while in use. This error is highly variable and can be caused by a range of file errors. Try running \config\ITFsettingsAgent.exe and \config\ITFsettingsCompiler.exe to try and fix the issue.
Screen Size Config is corrupt (err_config002)
You entered an invalid screen size. Make sure it is in the XXXXxYYYY format and remove any spaces or trailing symbols (i.e. A certain bug may cause a '...' to be added to the end of your inputs).
Screen Size Config doesn't match current screen size (err_config003)
This is an unused and deprecated function, will be removed in later version or release.
Version config error (err_config004)
Your bot's version is not set or is incorrect/corrupt. This is usually the cause of a bad installation.
Build ID config error (err_config005)
Your bot's build ID is incorrect/corrupt or not set and is caused by the same error as err_config004.
Couldn't download screen data (err_config006)
This is an unused and deprecated function, will be removed in later version or release.
Could not find screen config for screen size (err_config007)
Screen Config files (e.g. \config\XXXXxYYYY_1cfg.bat) are missing for the currently set resolution.
[file] is missing (err_file001-009)
The displayed file is missing and can not be found and started.
Trade Hold present. Fatal error (err_hold001)
The bot detected that you have an ongoing trade that is being held, please wait for that to complete or cancel it before using the bot.
Config for [itemid] is invalid or does not exist (ic_invalidcfg)
The bot is attempting to check an item that does not have a config. Item configs are located at \config\itemconfig. Config files are stored with the name [itemid].bat.
Config image for [itemid] is invalid or does not exist (ic_invalidimage)
The bot cannot find the image for the item it is checking. Images are in 24-bit BMP format (.bmp) and stored in \config\itemconfig\img_[Your Screen resolution]\ with the name [itemid].bmp.
Slot9 is NOT valid. Exiting call
This is a normal error message that happens at the end of an item check for a specific item.
Holdcheck timed out after [number] tries. (timed out)
This is a normal error message that happens if a trade hold is not found. Ignore this message.
Trade offer timed out after [number] tries. (timed out)
This is a normal error message that happens if a trade offer was not found.
These are bugs that occur on program login.
Server is down for maintenance
There is scheduled maintenance under way. If you see this error then we're probably fixing the server right at that moment! Wait a few minutes and try again. Scheduled maintenance is on Fridays and Sundays.
Could not connect to login server
This can often be caused by antivirus or firewall issues or a problem with your install. Make sure \config\botfiles\other\temp exists and \config\serverip.txt exists with a valid IP (try entering it in your browser to see if it works). If the IP doesn't work it most likely means there is an unannounced server issue.
Incorrect username or password
Check your username or password carefully and try again. Usernames and passwords are case sensitive. Make sure you have the latest version of the bot as older ones may not have correct login protocols. If you have forgotten your password, request it to be reset by contacting us.
There was an error verifying your account
Something went wrong while logging in. Retry your login and wait about 10 seconds (after the login window disappears) before pressing 'Connect'. This is an error on your side and not on any server (apart from that one time.. and that other time).