[Clientless]Torque 2.0

[backo]

Originally Posted by _Stryder_

I really hope for an update... it'll be very risky to use it at its current state.

How do you know that it's very risky? Nothing changed in the login protocol, except that the client has to wait 20 seconds before resending the login packet, if you send it before the 20 seconds you get disconnected. It's safe like before.

[mohamedanwar]

I agree with backo, its just lill bit slower now.
before was sending login packets every 1~3sec, now every 20sec.!

why new update needed? ...to fix it on 20 sec+ ? xD

[sessa]

Originally Posted by backo

How do you know that it's very risky? Nothing changed in the login protocol, except that the client has to wait 20 seconds before resending the login packet, if you send it before the 20 seconds you get disconnected. It's safe like before.

Something changed. There are words from person who created autologin program based on Torque autologin (not tLogin, another program):
Some packets changed. Old auto-loginer definitely can't work.
And I see Torque 2.0a can login only to free server and never seen succesful login to full server.
Please investigate this.

[recking]

Originally Posted by sessa

Something changed. There are words from person who created autologin program based on Torque autologin (not tLogin, another program):
Some packets changed. Old auto-loginer definitely can't work.
And I see Torque 2.0a can login only to free server and never seen succesful login to full server.
Please investigate this.

check your information sir... get some infos about the name "backo"...

i logged in with it today 4 times on two different servers.

[theoneofgod]

+1 again. nothing changed just the new loading progress bar and a 20 second login timeout. Safe to bot, as always.

[backo]

Originally Posted by sessa

Something changed. There are words from person who created autologin program based on Torque autologin (not tLogin, another program):
Some packets changed. Old auto-loginer definitely can't work.
And I see Torque 2.0a can login only to free server and never seen succesful login to full server.
Please investigate this.

It can login to full server, you just think that it can't because it takes longer now, it's a huge difference.. before we could send 4-5 login requests per second, and now just one request per 20 seconds. Only one thing changed, they've added 4 bytes to the "traffic" packet, the 4 bytes tell the client the wait time before sending the next login request, it's 20 always, if you send it before the 20 seconds you'll get disconnected.

Originally Posted by recking

check your information sir... get some infos about the name "backo"...

i logged in with it today 4 times on two different servers.

Originally Posted by theoneofgod

+1 again. nothing changed just the new loading progress bar and a 20 second login timeout. Safe to bot, as always.

right.


By the way, I've uploaded a 2.1 version since bot didn't had time for it. Just cleaned up some old code, and now you don't have to set the 20 second delay yourself.

[gandbusta92]

this might be kinda noobish.. but idk hoe to move around and ish.

:P

[bot90210]

I may make an update that will increase login speed, assuming there is infact no queue. It will make 5 login connections per cl and sync them, so that when one gets traffic it will dc and reconnect while another connection sends another request. This may or may not work and will require testing. The next version I release will include better parsing (increase success for cl -> client), fix the chat bug and fix anything else I see that needs fixing. Be patient, this will probably be awhile away because coding for Torque is ******* boring as it's all packet related and I'm working on some client based projects.

[gandbusta92]

where do you type the commands at in?

cant seem to understand teh function...

[theoneofgod]

Originally Posted by gandbusta92

where do you type the commands at in?

cant seem to understand teh function...

I don't use it, but I'm sure you have to PM the character on Torque, like trace me or something.

[killchill69]

it doesn´t work

[saphirox123]

Originally Posted by killchill69

it doesn´t work

May we know what doesn't work man ?

Here i use 2.0a and it's still working.

[bot90210]

It needs updating, nick just changed the login system, we didn't fix bugs. When I get this proj done ill do it.

[sessa]

Originally Posted by saphirox123

May we know what doesn't work man ?

Here i use 2.0a and it's still working.

Time from time even on free server Torque 2.1 shows in the log
<Disconnected>
and going to endless loop - I wait for 3 hours and it can't log in when this happened.
It not write
[13:17:59] Couldn't connect due to server traffic.
[13:17:59] Waiting 20 seconds before relogging
as usualy.
Same problem was with 2.0a. I'm sure there is some packed which Torque is not correctly works up.
Please investigate.

To recking: don't fear me with wellknown names I know whom I write and what I write. I'm programmer with wellknown name and worked several years in PC game development. Now I help with betatesting to some SRO-relating programmers.

[backo]

Originally Posted by sessa

Time from time even on free server Torque 2.1 shows in the log
<Disconnected>
and going to endless loop - I wait for 3 hours and it can't log in when this happened.
It not write
[13:17:59] Couldn't connect due to server traffic.
[13:17:59] Waiting 20 seconds before relogging
as usualy.
Same problem was with 2.0a. I'm sure there is some packed which Torque is not correctly works up.
Please investigate.

To recking: don't fear me with wellknown names I know whom I write and what I write. I'm programmer with wellknown name and worked several years in PC game development. Now I help with betatesting to some SRO-relating programmers.

A full log from start to end would help, I don't have much time lately but it worked fine in the few hours ive tested it. So if it happens again to you, copy/paste the log @ and post the link here.