[HELP] Connecting to localhost with newest client

Hello!
I'm trying to connect to my localhost P-Server running NosWings source, I can connect with a older client (0.9.3.3107), but I think it's been corrupted somewhere down the line, and there's some flickering. I've managed to change the IP in NostaleClientX.exe from the client version (0.9.3.3160), I can see that it connects to the login server, but it instantly disconnects from it and doesn't show the server list. Any help would be highly appreciated!

Simply because since the last commit of the source you use the NoS0575 packet has been updated

Hi!
I've ran into another problem. After @[Only registered and activated users can see links. Click Here To Register...] pointed me into the direction of the login packet, I've managed to pin-point the problem to the NsTeST packet, and now I'm able to get a server list, but after selecting a channel to connect to I'm met with the message: Server was disconnected. NosTale is finished. In the World Server console I can see: "Client connected. ClientId = 1", followed by "Client arrived, SessionId: 0" and "Client disconnected! ClientId = 1". I'd appreciate any tips and help.

Quote:

Originally Posted by Skeetcher Hi! I've ran into another problem. After @[Only registered and activated users can see links. Click Here To Register...] pointed me into the direction of the login packet, I've managed to pin-point the problem to the NsTeST packet, and now I'm able to get a server list, but after selecting a channel to connect to I'm met with the message: Server was disconnected. NosTale is finished. In the World Server console I can see: "Client connected. ClientId = 1", followed by "Client arrived, SessionId: 0" and "Client disconnected! ClientId = 1". I'd appreciate any tips and help.

Same there the "Login" packet to world is changed it added Language Parameter.

Quote:

Originally Posted by FI0w Same there the "Login" packet to world is changed it added Language Parameter.

Ok, I do understand that but how would someone fix that issue?

Quote:

Originally Posted by GreatSymphonia Ok, I do understand that but how would someone fix that issue?

By checking how the packet is implemented on your source and how the packet is implemented on the official.

Even easier, u can juste check on NosCore because 0Lucifer0 already fixed this issue (ofc u'll need to adapt it for opennos)

Quote:

Originally Posted by GreatSymphonia Ok, I do understand that but how would someone fix that issue?

Just change some index parts, i think it was the index of the password and done. Since Opennos dont care about the Language.