• Welcome to Valhalla Legends Archive.
 

Telnet -aka Chat Bot

Started by SKiLLs, August 08, 2008, 04:17 AM

Previous topic - Next topic

SKiLLs

It's been a long time since i messed with this. Does Battle.net no longer accept telnet connection aka Chat Bots?

Barabajagal


SKiLLs

#2
No as in no Telnet and Battle.net no longer connect?

When did this happen? And did it also happen to SC:SW and D1:Demo?

Barabajagal

No binary clients have lost support. There is no Telnet CHAT connection anymore.

MyndFyre

Quote from: Andy on August 08, 2008, 06:03 AM
No binary clients have lost support. There is no Telnet CHAT connection anymore.
It is worthwhile to note that DSHR and DRTL can't go to private channels; I'm fairly sure the same is true for SSHR.
QuoteEvery generation of humans believed it had all the answers it needed, except for a few mysteries they assumed would be solved at any moment. And they all believed their ancestors were simplistic and deluded. What are the odds that you are the first generation of humans who will understand reality?

After 3 years, it's on the horizon.  The new JinxBot, and BN#, the managed Battle.net Client library.

Quote from: chyea on January 16, 2009, 05:05 PM
You've just located global warming.

Sixen

Quote from: MyndFyre[vL] on August 09, 2008, 12:21 AM
It is worthwhile to note that DSHR and DRTL can't go to private channels; I'm fairly sure the same is true for SSHR.

That's correct. Also, JSTR/JSHR cannot join private channels. They are all restricted to the client-specific public channels, Blizzard Tech Support, Open Tech Support, and The Void.

Although, with Battle.net 2.0 coming out with SC2, this has a possibility of changing.
Blizzard Tech Support/Op W@R - FallenArms
The Chat Gem Lives!
http://www.diablofans.com
http://www.sixen.org

Yegg

Quote from: Sixen on August 09, 2008, 12:29 AM
Quote from: MyndFyre[vL] on August 09, 2008, 12:21 AM
It is worthwhile to note that DSHR and DRTL can't go to private channels; I'm fairly sure the same is true for SSHR.

That's correct. Also, JSTR/JSHR cannot join private channels. They are all restricted to the client-specific public channels, Blizzard Tech Support, Open Tech Support, and The Void.

Although, with Battle.net 2.0 coming out with SC2, this has a possibility of changing.

Not that it's really important, but what did you mean by "client-specific public channels". I remember them being able to join Public Chat 1, 2, etc. as well as any channel labeled as Public created by either the chat user or another user.

UserLoser

Quote from: SKiLLs on August 08, 2008, 04:17 AM
It's been a long time since i messed with this. Does Battle.net no longer accept telnet connection aka Chat Bots?

why didn't you just start menu->run->telnet useast.battle.net 6112->c and test yourself

MyndFyre

Quote from: UserLoser on August 09, 2008, 01:25 PM
Quote from: SKiLLs on August 08, 2008, 04:17 AM
It's been a long time since i messed with this. Does Battle.net no longer accept telnet connection aka Chat Bots?

why didn't you just start menu->run->telnet useast.battle.net 6112->c and test yourself
Maybe he had and wanted to confirm that something wasn't wrong on his end?
QuoteEvery generation of humans believed it had all the answers it needed, except for a few mysteries they assumed would be solved at any moment. And they all believed their ancestors were simplistic and deluded. What are the odds that you are the first generation of humans who will understand reality?

After 3 years, it's on the horizon.  The new JinxBot, and BN#, the managed Battle.net Client library.

Quote from: chyea on January 16, 2009, 05:05 PM
You've just located global warming.

UserLoser

Quote from: MyndFyre[vL] on August 09, 2008, 02:36 PM
Quote from: UserLoser on August 09, 2008, 01:25 PM
Quote from: SKiLLs on August 08, 2008, 04:17 AM
It's been a long time since i messed with this. Does Battle.net no longer accept telnet connection aka Chat Bots?

why didn't you just start menu->run->telnet useast.battle.net 6112->c and test yourself
Maybe he had and wanted to confirm that something wasn't wrong on his end?

na i bet the guy asking doesn't even know what telnet is

Ringo

#10
iirc, the chat protocol still exist's, it's just not accessable to the public :(
I'm pretty sure it has moved to protocol 0x81 or 0x01 (since you don't get connection closed when you send 0x50 with CHAT client ID)
I guess how ever it works now, you can only get to chat with it, if you have a ready created account/password in the blizzard account database :P


Gl braking through that forcefield;

C > S
01                                                    .

C > S
FF 50 32 00 00 00 00 00 36 38 58 49 54 41 48 43       .P2.....68XITAHC
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00       ................
00 00 00 00 00 00 00 00 00 42 6C 69 7A 7A 61 72       .........Blizzar
64 00                                                 d.

S > C
FF 25 08 00 77 C3 24 07 FF 50 28 00 00 00 00 00       .%..w.$..P(.....
1D 88 44 5A 5E 17 15 00 00 8B 51 03 70 5F C7 01       ..DZ^.....Q.p_..
76 65 72 2D 49 58 38 36 2D 30 2E 6D 70 71 00 00       ver-IX86-0.mpq..

C > S
FF 51 1A 00 5A 6F 47 00 00 00 00 00 00 00 00 00       .Q..ZoG.........
00 00 00 00 00 00 00 00 00 00                         ..........

S > C
FF 51 09 00 01 01 00 00 00                            .Q.......

Barabajagal

Wonder what the right verbyte would be...

Sixen

Quote from: Yegg on August 09, 2008, 01:06 AM
Not that it's really important, but what did you mean by "client-specific public channels". I remember them being able to join Public Chat 1, 2, etc. as well as any channel labeled as Public created by either the chat user or another user.

Diablo Name
StarcraftJ Name



Only reason i'm back here is to see Ringo's reply.... /facepalm for bumping old topics, but whatever.
Blizzard Tech Support/Op W@R - FallenArms
The Chat Gem Lives!
http://www.diablofans.com
http://www.sixen.org