05-10-2009, 02:22 PM
I have a question about the login process itself. I've come back to play and have forgotten my password, so I downloaded all of my files and went to log in. The first time it simply gave me the invalid credentials screen, and when I tried another password, it would freeze on the "Verifying Account..." screen. After about five minutes or so it will finally move on to giving me the next page (on a wrong password it will load the invalid credentials screen again, etc.). I can close down the client, give it five minutes or so, then re-start Razor and it responds normally.
My question is:
Is there a lockout timer after a failed login attempt?
If there isn't such a timer, is there something I can change so that I can actually try my different passwords without it taking hours to do so?
A bit of info on my install:
-Using Razor, information regarding Razor is all correct.
-My login file is the default login, as I was under the impression that Razor overwrites the login.cfg file anyway.
-I downloaded all of my UO files from in-x.org.
-Before loading Razor, I patched UO to it's latest version.
-After patching, I copied the .mul files into my directory.
I've tried different variations of each of these steps to try to resolve the 'freezing,' but nothing has worked.
My question is:
Is there a lockout timer after a failed login attempt?
If there isn't such a timer, is there something I can change so that I can actually try my different passwords without it taking hours to do so?
A bit of info on my install:
-Using Razor, information regarding Razor is all correct.
-My login file is the default login, as I was under the impression that Razor overwrites the login.cfg file anyway.
-I downloaded all of my UO files from in-x.org.
-Before loading Razor, I patched UO to it's latest version.
-After patching, I copied the .mul files into my directory.
I've tried different variations of each of these steps to try to resolve the 'freezing,' but nothing has worked.


Maybe it sounds like a dumb question, but thats how I was solving this problem... You just re-launch client, and everything will be fine... I'm not sure about razor tho, but on injection it was working fine... try to launch client without razor if it won't help... If your clients don't launching without third-party programs then download "Injection Clients" from our website, there is client called "5.0.1h m". And it will launch without razor/injection.
just wanted to make sure you knew it wouldn't have an effect.![[Image: ginzodium.jpg]](http://user.disk-one.se/odium/ginzodium.jpg)