This topic was created to address the following Common Problems:

- Check Revision Failed
- Outdated Game Version
- Error 6 Overflow
- Error 13 Type Mismatch
- Disconnection Error
- Winsock Error

[Check Revision Failed]:

If you are receiving a "Check Revision Failed Error," download the following zip file: http://www.l2uthless.org/l2uthless%20Chat/MPQ.zip

If you are using l2uthless Chat, you must extract this zip into the Files folder inside your l2uthless Chat folder, if you are asked to overwrite files, select yes.

If you are using l2uthless Ops, you must extract this zip into the MPQ folder inside your l2uthless Ops folder. If this folder does not exist,  create it. If you are asked to overwrite files, select yes.

[Outdated Game Version]:

This error is commonly generated when you are using old hashes or the bnls server your are connecting to has not updated their files. Also be sure to check that you are using the correct Verbyte which can be located in the beginning of the Configuration files. Otherwise please download the most recent hashes or switch to a different bnls server.

[Error 6 Overflow]:

This error has been noted when l2uthless Ops attempts to process large amounts of data, the most common occurence is when processing large uptimes. To fix this error you can quit and restart l2uthless Ops or, Clear the Safelist/Shitlist/Tagban files. If this does not fix the error try disabling chat via the l2uthless Ops console.

[Error 13 Type Mismatch]:

This error can normally be fixed by Clearing the Safelist/Shitlist and, Tagban files.

[Disconnection Error]:

This error is generated most commonly as a result of an error encountered while handling the Warden protocol. You will usually be disconnected from battle.net or l2uthless Ops will suddenly quit without warning, this usually happens within 2-5 minutes of connecting the bot. It is recommended that you navigate to your Warden folder located within the l2uthless Ops directory and clear everything in the folder excluding the WardenW3.txt, WardenSC.txt and, zlib.dll files. If this does not resolve the problem you may require new Warden Offsets. It would be wise to consult the support forum for a link to the most recent offsets.

[Winsock Error]:

This error is generated most commonly as a result of being Ipbanned from battle.net or from exceeding eight concurrent connections to battle.net. If you are certain you have not ipbanned consider the following:

Have you installed any new security software such as an Anti Virus of Firewall that could be preventing the connection to battle.net? If you answered yes, to this question you must either add an exception to the Firewall and, or Anti Virus to allow you to connect to battle.net. You will have to allow incoming and outgoing connections via TCP/UDP on Port 6112. If you answered no, to this question move on.

Can you still connect to battle.net and all of its realms? If you answered yes, to this question then you have no reason to suspect being ipbanned from battle.net. If you answered no, then you are most probably ipbanned from your preferred battle.net realm and, will be forced to use a proxy to bypass the ban. Most Ipbans last for a 2 week period, although some are only 24, 48 or 78 hours long. You may attempt to connect once every 24 hours for the first three days, if you are still ipbanned you must wait 2 weeks before attempting to connect again. There have been cases where ipbans have lasted up to a month or longer.

*Note - If none of these fixes work consult the support forum. Remember to always remove your CD-Key(s) and, Password(s) if you ever post your configuration file.