Changing the restart button to redirect charselection

[Isoline*]

So, for the old players who played SRO back in the days, i remember that the client actually redirected you to the char-selection screen, upon restart, and not to the login-screen credentials.

it was like that in the beginning of SRO (talking about cap 80 times), but then ofcourse, joymax changed it due to the obvious financial reasons:
1. Client Restating - agent con is lost, gw con eastablished,
2. Being redirected to gateway's credentials screen - means he is offline.
3. re-waiting in the logging attempts queue list - which was crowded as hell
4. hence, people buy more silks-Premiums to enter by the the first login attempt.

afterwards, i remember that they changed it back in the roc mt. update came along, and then not so long after, chagged it back, so basically we inherit that till this day.

so i have been trying to re-create that old feature, because it useless getting the player out of the game because he is restarting, all servers these days are no crowded and its just simply annoying and useless.
so i tried several ideas:

firstly, i just thought of simply replacing sro_clients CPS:Restart to the CPS:CharSelection in a debugger, however, it is not an easy task, and a simple replacement, is doubtly to work & and can cuas serious client problems.

secondly, i thought to do it via a proxy:
simply block the 0x300A packet [SERVER_LEAVESERVER_LEAVE_SUCCESS]
coming from the server, so the client wont dc the ag module and go to gw module, append it with client request 0x7007 [CLIENT_CHARACTERSCREEN]
and let the sro_client do the proccessing for us.


unfortunately, both attempts failed, from many reasons, there could be other requierd modifications in the server nodes aswell, as im still testing everything i can.
i hope anybody skilled here can shed a light on the matter, or how to perform it.

[vorosmihaly]

Well what you could do with a proxy is handle the re-login in the background with the filter and send client the right packets to make it look like it didn't actually disconnect from the agentserver

[Isoline*]

Originally Posted by vorosmihaly

Well what you could do with a proxy is handle the re-login in the background with the filter and send client the right packets to make it look like it didn't actually disconnect from the agentserver

in thoery, that can be done, but it will still disconenct the gw module, and connect to ag module, furthermotre captcha will have to be disabled aswell, to allow the possibility to mimic this feature.

[qoaway]

when I was working on csro files while they wasnt public, I faced problem that redirects character select screen directly when teleport by some reason (its not happening everytime), I didnt figured out what problem is but when you are press start It was crashing the client.your idea can be done, not only in theory, in practice It can be.Try debugging csro files (not -r ones) maybe you can find a solution to use in vsro files

[​Exo]

Originally Posted by eitai123

in thoery, that can be done, but it will still disconenct the gw module, and connect to ag module, furthermotre captcha will have to be disabled aswell, to allow the possibility to mimic this feature.

Not exactly, you're technically not connected to either of them yourself. You're just coinnected to the proxy. Let the proxy re-initiate the connection and it should be fine. For the captcha, ye, should be disabled or just static.
One thing that could take care of the visuals is to let the client run a script while the process is being done. Shouldn't take long but the client does take some seconds to process the packets and visualize the stuff. But that's just to make it look "better".