Now the client thinks that the server responded to the third attempt and you will get the message “ The password “password” worked.”, even though qwerty is the password that worked. The first one is correct but the server has a lag spike, so after the client is already done sending all three login attempts, the server responds to the first attempt with Successfully logged in!. For instance, let's say it tries 3 passwords: password, 123456 and qwerty. The problem with this option is that it can cause ForceOP/AuthMeCracker to forget which password worked. Whether or not it should wait for “ Wrong password!” messages also has a small influence on the time it takes. At the minimum delay (50ms), Xato's list only takes a couple minutes. If it doesn't have AntiSpam, you can set it to a lower value which will drastically increase the speed. In other words, if the server has AntiSpam, like most servers, you shouldn't change this value. It's also the shortest delay that can bypass AntiSpam (the server plugin, not the hack). The default value is 1000ms which is equivalent to 1 password per second. The delay between attempts only influences the time that it takes. On some special servers, this may be worth it, but if you are just trying to get OP on a random server, you will definitely be better off using the default list. It contains 10000 passwords, but because it's so long, trying to crack a single password with it can already take several hours. I recommend Xato's '10k most common.txt' ( direct download link, since the link on the original post no longer works). A password list is a TXT file with one password per line.

To change the password list, select TXT file, click browse and select your list. The password list influences the chance that it works and the time that it takes.

In some cases though, it will be more efficient if you change the options, so we will get to that now.

Wurst client 1.14.2