I'm french so i will just take an exemple :
I'm on a server. When i go on with 2.0.5 version, i have this packet at connection :
Checking for new portals... none found
Connecting to Account Server...
Connecting <theserver>... connected
Sent packet : 0277 [84 bytes]
Received packet : 0069 [79 bytes] [Account Info]
-------------------Account Info----------------------
...
And the bot is going right
Now with the SVN version :
Checking for new portals... none found
Connecting to Account Server...
Connecting <theserver>... connected
Sent packet : 0064 [55 bytes]
Timeout on Account Server, reconnecting...
The 2 connections have been made under the same conditions. (same recvpackets.txt, same servers.txt, same config.txt)
So why there is a different connection with the SVN version, wich doesn't work ?
Change of the connection's method | 2.0.5 > 2.0.6 rev6464
Moderators: Moderators, Developers
Change of the connection's method | 2.0.5 > 2.0.6 rev6464
- Attachments
-
- recvpackets.txt
- (5.34 KiB) Downloaded 290 times
-
- servers.txt
- (194 Bytes) Downloaded 272 times
-
- Human
- Posts: 39
- Joined: 15 Apr 2008, 06:08
- Noob?: Yes
- Location: Russia, Velikiy Novgorod
- Contact:
Re: Change of the connection's method | 2.0.5 > 2.0.6 rev6464
change servertype
Re: Change of the connection's method | 2.0.5 > 2.0.6 rev6464
This is the same servertype for both versions (servertype 8)
I tried with servertype 8_x on SVN version but don't work.
I will try other servertype.
EDIT : The first packet sended by the SVN version is alway 0064, with all servertype.
I tried with servertype 8_x on SVN version but don't work.
I will try other servertype.
EDIT : The first packet sended by the SVN version is alway 0064, with all servertype.
-
- Super Moderators
- Posts: 801
- Joined: 06 May 2008, 12:47
- Noob?: No
Re: Change of the connection's method | 2.0.5 > 2.0.6 rev6464
ST 8 is obsolete.
bug is irrelevant
bug is irrelevant
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!