SRL Archive - Discussions and Debates

LoginPlayer Errors


Kernel Klink

2006-07-07 09:25:03

Recently while autoing, I have noticed a slight error in LoginPlayer. When going to login a player, it clicks "Existing User", but then, instead of clicking "Username", it somehow misclicks on "Password." This continues and I eventually have the username and password of the player typed in the "Password" input. Now before beginning to fix anything, I want to know if anyone else is having similar problems. If you are, then please post.

WT-Fakawi

2006-07-07 09:39:07

yes yes. Just witnessed it today!

Prolly the Login Window floats :)

Kernel Klink

2006-07-07 10:32:18

Ok. You're witness is substantial enough. Thanks.

tarajunky

2006-07-07 14:59:29

http://82.92.130.193/forums/showthread.php?t=2191

Nobody believed me. :)

Dankness

2006-07-07 16:04:19

Iv seen it alot Kernal ill wake up and 10 of my players will be unactive and all with L/P errors

Kernel Klink

2006-07-07 16:40:30

Sorry Tarajunky, I should've been much more observant, therefore, I wouldn't have to make a re-post. You explained it much better might I add.

Dankness, when you say L/P errors, is that what your location is set to? Because with the problems I've been having, where both the username and password are both in the password input, the error doesn't appear as "invalid username or password", it appears as "Error Loading Your Profile. Please Contact Customer Support." As far as I know, the only time in which your location is set to "L/P Error" is after you try three times to log in after an invalid username error. Just trying to clarify this because I need to fully understand the problem to fix it.

As for now, I have made a quick fix, but I haven't added it to the SRL. All it does is if it finds the text "rror loading", it keeps on trying to log in. It usually logs in properly after the 1st or 2nd try after finding the error.

WT-Fakawi

2006-07-07 17:29:57

try unblanking line 100 in login.scar:
// SendKeysSilent(Players[CurrentPlayer].Name + chr(13) + Players[CurrentPlayer].Pass)

and blank 101-105.

The solution has already been there, only I find it highly detectable. (Prepare for a shock if you unblank 101 :D )