Aion client will not switch to gameserver

Newbie Spellweaver
Joined
Jun 14, 2022
Messages
5
Reaction score
1
I have this problem since some days now. it will not switch from ls to gs and all packets is okay!
packet capture also shows client receiving packets and database ip is correct, gameserver.java is correct.

any idea how this can work? I use wine on linux for playing aion locally and d3dx9 in winetricks. I think something is different in the wine that prevents this working. telnet to 7777 locally sends gs key... mm so frustrating! ls can connect to gs for ping so maybe this packets is wrong?

here is the images album:

please any help will be great :D sorry my english
 
Last edited:
Aion 4.6 Emu is not compatible with Client Aion 4.5 NA...

Use Client 4.6 EU for this Emu

it runs in windows ok. i think this is some packet problems running aion with wine on linux.



sems you dont have put no ip dll to bin32 or bin64 folder of client

not .dll error i already check this but ty
 
Upvote 0
it runs in windows ok. i think this is some packet problems running aion with wine on linux.





not .dll error i already check this but ty

If it's the upper end of 4.5, for eg. 4.5.0.33 there is 0x43 static gameserver opcode and 0xCC 0xDD required to encode the opcodes from the Gameserver.

Looks like you're not getting any response from the Gameserver at all which means you're correct, the Client is receiving an OK! from the Loginserver but not opening a socket to the Gameserver.

If your client was connecting but failing packets, then it's a packet problem. Because you are not connecting at all, this means its a platform specific problem such as the way you're running the client, in this case through wine on Linux.

I tried running my custom emulator on Linux and it runs flawlessly for windows clients but fails just like this for Linux clients, maybe some other developers can help explain why this happens, I'm betting money it's wine's networking setup not working correctly.

I'd start with doing an ipconfig from within a wine prefix and see what the setup is like, try ping 7777 with telnet if available.



Aion 4.6 Emu is not compatible with Client Aion 4.5 NA...

Use Client 4.6 EU for this Emu

Can confirm mate, it's a Linux specific networking problem with wine not an emulator problem.
 
Upvote 0
it runs in windows ok. i think this is some packet problems running aion with wine on linux.

I believe you are using AionGer 4.6, correct? they who worked on this version.
I tested client 4.5 and i had problems with Emu, this was resolved with the 4.6 EU client,
that's why i asked this question, but i believe that StingerOne must be right.



Can confirm mate, it's a Linux specific networking problem with wine not an emulator problem.
Yes i believe you are right.
 
Upvote 0
I believe you are using AionGer 4.6, correct? they who worked on this version.
I tested client 4.5 and i had problems with Emu, this was resolved with the 4.6 EU client,
that's why i asked this question, but i believe that StingerOne must be right.




Yes i believe you are right.

If it's the upper end of 4.5, for eg. 4.5.0.31 or 4.5.0.33, the SM_VERSION_CHECK packet is a mix of 4.5 and 4.6 bytes. The opcodes are also different, change both of those and it will work for your 4.5 NA client.
 
Upvote 0
If it's the upper end of 4.5, for eg. 4.5.0.31 or 4.5.0.33, the SM_VERSION_CHECK packet is a mix of 4.5 and 4.6 bytes. The opcodes are also different, change both of those and it will work for your 4.5 NA client.

Yes i understand, when AionGer stopped fixing this version i also made some fixes,
but i decided to work on 4.0-4.3 and in free time i still go on.
 
Last edited:
Upvote 0
I believe you are using AionGer 4.6, correct? they who worked on this version.
I tested client 4.5 and i had problems with Emu, this was resolved with the 4.6 EU client,
that's why i asked this question, but i believe that StingerOne must be right.




Yes i believe you are right.

yes aion ger 4.6 and it works with 4.5 client



If it's the upper end of 4.5, for eg. 4.5.0.33 there is 0x43 static gameserver opcode and 0xCC 0xDD required to encode the opcodes from the Gameserver.

Looks like you're not getting any response from the Gameserver at all which means you're correct, the Client is receiving an OK! from the Loginserver but not opening a socket to the Gameserver.

If your client was connecting but failing packets, then it's a packet problem. Because you are not connecting at all, this means its a platform specific problem such as the way you're running the client, in this case through wine on Linux.

I tried running my custom emulator on Linux and it runs flawlessly for windows clients but fails just like this for Linux clients, maybe some other developers can help explain why this happens, I'm betting money it's wine's networking setup not working correctly.

I'd start with doing an ipconfig from within a wine prefix and see what the setup is like, try ping 7777 with telnet if available.





Can confirm mate, it's a Linux specific networking problem with wine not an emulator problem.

this is the suspision! i will try it thanks :)
 
Upvote 0
Yes, so your client is compatible, but as Falke34 has always said,
"I still recommend you use Client 4.6 EU" :wink:

Most Aion emulators are half baked using old code bases with hacked together packets, as long as the static opcodes are changed, the obfuscation is updated and at minimum the SM_VERSION_CHECK Gameserver packet is updated, the client you're using will work, then it's just a matter of changing the opcodes to match and verifying the packet data.

I think 4.6 EU and 4.5 NA use similar packet structures.
 
Upvote 0
Most Aion emulators are half baked using old code bases with hacked together packets, as long as the static opcodes are changed, the obfuscation is updated and at minimum the SM_VERSION_CHECK Gameserver packet is updated, the client you're using will work, then it's just a matter of changing the opcodes to match and verifying the packet data.

I think 4.6 EU and 4.5 NA use similar packet structures.
I know what you're saying, i understand and i agree with you.
There may be compatibility between 4.6 EU and 4.5 NA clients (it depends on the version),
but is there any difference between packets and some IDs are different.
 
Last edited:
Upvote 0
Back