New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lobby server issues on secific character slots. #497

Open
TeoTwawki opened this Issue Sep 23, 2014 · 3 comments

Comments

Projects
None yet
3 participants
@TeoTwawki
Copy link
Member

TeoTwawki commented Sep 23, 2014

I didn't notice til I needed to create a bunch of alts to test my attempts at nexus cape with but I verified this is not a multi boxing issue and tested with a clean dsp pull & build (no modifications) before opening the issue on github.

Remember the old bug that crashed servers if you tried to log in certain characters? That was fixed a long time ago, but I think the recent client updates changed something again.

I'm seeing certain character slots unable to log in with pol-0001 after 5+ characters are created on the account.

If I move the effected characters to a different account they can log in, but at the risk of a different character on the previous account suffering the pol-0001 error.

The weird thing is, its not always the same slot across accounts. I loaded up 2 accounts to test it. account ID 1000 had slot 4 get perma stuck after creating the 5th character. Account 1001 had slot 3 get stuck instead. All other characters on both accounts are able to log in. Very interestingly, logging in directly from character creation will work. By this I mean if you delete "stuck" character and then make a new one that occupies that slot the initial zone in from char creation works (IF you don't get the invalid key crap that is) but then re-logging you see pol-0001 again.

These are NOT problems that can be fixed by resetting the character, they don't even touch the map server at all. There are no server log errors or crashes, ports and IPs are correctly set.

I'm pretty sure recent one of the client updates did it.

@teschnei

This comment has been minimized.

Copy link
Member

teschnei commented Sep 23, 2014

could be that something changed for lobby packets, anything in lobby server log?

@TeoTwawki

This comment has been minimized.

Copy link
Member

TeoTwawki commented Sep 23, 2014

That was my guess. Nothing in log at all abnormal for lobby or map, acts like client isn't there when affected chars try to log in.

@atom0s

This comment has been minimized.

Copy link
Contributor

atom0s commented Jan 22, 2015

Before I recoded the boot loader, every slot past 6? or something did not work. Which I found the bug causing that and fixed it. However, in the attempt to fix that, the bug you are explaining here came about. It is not a new bug that happened recently. It is a known issue with the boot loader / lobby server that 2 out of the 16? slots have problems logging in when you create a character in every slot. I have not been able to pinpoint the problem, granted I stopped looking into it a while ago.

Now that I wrote polpackets to dump the packet flow from PlayOnline, someone could dump the retail POL communications again and check into it. It's mainly needing to see if anything changes when you log into an account in a higher end slot. And what the packets look like if anything has changed. I doubt they have since POL has not been updated in years now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment