reconnect

03/15/2014 00:57 kakamankoko#1
Hey guys anyone have any idea on how to auto reconnect the client back when it disconnect
03/15/2014 05:16 Spirited#2
You would have to create some sort of bot to do that.
03/15/2014 07:49 kakamankoko#3
Quote:
Originally Posted by Spirited View Post
You would have to create some sort of bot to do that.
I made one but hunting fissconnect after like 15 mins so I need to reconnect the client
03/15/2014 08:37 Spirited#4
Quote:
Originally Posted by kakamankoko View Post
I made one but hunting fissconnect after like 15 mins so I need to reconnect the client
Can you tell us more about your bot and how it works? I mean, if it's your bot, you really should be able to write this on your own. What's the problem?
03/15/2014 14:00 kakamankoko#5
Quote:
Originally Posted by Spirited View Post
Can you tell us more about your bot and how it works? I mean, if it's your bot, you really should be able to write this on your own. What's the problem?
not mine i`m using proxy paradise added and i added many features to it and i need to add the reconnect
03/15/2014 17:07 Aceking#6
What you need to worry about is WHY its disconnecting after 15 minutes.
Its a pretty pointless bot if it just hunts for 15 minutes then disconnects you and logs back in again.

Out of curiosity, are you running it on the newest patch of conquer?
03/15/2014 17:32 kakamankoko#7
Quote:
Originally Posted by Aceking View Post
What you need to worry about is WHY its disconnecting after 15 minutes.
Its a pretty pointless bot if it just hunts for 15 minutes then disconnects you and logs back in again.

Out of curiosity, are you running it on the newest patch of conquer?
it`s my network proplems and no not the newest patch but it`s working on patch 5870 p server
03/15/2014 18:15 Spirited#8
Alright. Well, the nature of a proxy is to intercept traffic as a middle man attack. It takes up your client's connection and establishes a new connection to the server, yeah? So, when the proxy disconnects, don't let that disconnect the client; instead, make an attempt to reconnect by sending data to the account server and what not. It's not difficult, but it is a bit of work.
03/15/2014 18:55 kakamankoko#9
Quote:
Originally Posted by Spirited View Post
Alright. Well, the nature of a proxy is to intercept traffic as a middle man attack. It takes up your client's connection and establishes a new connection to the server, yeah? So, when the proxy disconnects, don't let that disconnect the client; instead, make an attempt to reconnect by sending data to the account server and what not. It's not difficult, but it is a bit of work.
I think I will not let it disconnect using the connection packet (1012) ? Correct me if I,m wrong and thanks for the information
03/18/2014 23:52 Benzaldehyde#10
Quote:
Originally Posted by kakamankoko View Post
I think I will not let it disconnect using the connection packet (1012) ? Correct me if I,m wrong and thanks for the information
If it was a simple matter of blocking the disconnect packet, every bot would be unstoppable. There are serverside checks for many operations on timed intervals, and if your client is sending packets at rates that don't match up or have faulty structures, expect the server to catch your ass and boot you; simple as that.
03/20/2014 21:12 pro4never#11
Quote:
Originally Posted by kakamankoko View Post
I think I will not let it disconnect using the connection packet (1012) ? Correct me if I,m wrong and thanks for the information
No. You need to not close the socket going Client<>Proxy when the server closes the connection.

You can then create a NEW connection from Proxy<>Server and continue where you left off (without the client ever realizing it was disconnected.


That being said, I think it's a bit difficult in newer patches because you'd have to basically be writing your own standalone authentication process (handling everything up until standard game begins and then letting client take over)

I could be wrong on that. Alternatively you could just write something in autoit or a similar scripting language to detect the disconnect message and have it manually log back in. Just write your proxy so that it saves settings between disconnect so it will continue where it left off when it first logs in.
04/02/2014 22:30 kakamankoko#12
Quote:
Originally Posted by pro4never View Post
No. You need to not close the socket going Client<>Proxy when the server closes the connection.

You can then create a NEW connection from Proxy<>Server and continue where you left off (without the client ever realizing it was disconnected.


That being said, I think it's a bit difficult in newer patches because you'd have to basically be writing your own standalone authentication process (handling everything up until standard game begins and then letting client take over)

I could be wrong on that. Alternatively you could just write something in autoit or a similar scripting language to detect the disconnect message and have it manually log back in. Just write your proxy so that it saves settings between disconnect so it will continue where it left off when it first logs in.
I prevent the client from disconnecting from the proxy but now how to create a new connection to proxy packet i see that your proxy sends it on serverconnection_onrecive but how to send it ?