Valhalla Legends Archive

After opening a connection to Battle.net and successfully logging in using CHAT, if I try to open a second connection in CHAT, it will disconnect the first connection from Battle.net, but will not close the socket or return any error.

My question is, how could the program know if it was disconnected due to this, if Battle.net doesn't close the socket?

Don't connect a second? :P

yeah thats right because you connect using 1 because of the winsock connection. it connects using 1 of 2 things:
1) hostname
2) ip address

You can only have one chat connection per IP; trying to connect a second chat bot would result in Battle.net closing one of the two connections.
If you wish to know what event is triggered when this occurs, we need to know what language you're using.

Visual Basics..

It ain't triggering _Error or _Close on the Winsock.

In addition, the state of the winsock of the bot that got disconnected from Battle.net is still sckConnected. It's like if Battle.net disconnects the bot but doesn't close the connection with the person.

it's like unplugging your NIC - there's no notification.  Try sending SID_NULL (or some equivolant, like /time) every minute or so to check.

Would you happen to know the amount of data you must send to Battle.net before getting disconnected with "Flooded" error and is it different for CHAT and SEXP?

Basically I could do something like:

public function GotUnplugged() as boolean
on error goto hell
   socket.sendData chr(0)
   GotUnplugged = false
   exit function
hell:
   GotUnplugged = true
end function

Would that chr(0) be counted in the amount of data I sent for the anti-flood thing over at Battle.net?

Quote from: CMallette on April 12, 2004, 05:44 PM
Would you happen to know the amount of data you must send to Battle.net before getting disconnected with "Flooded" error and is it different for CHAT and SEXP?

Basically I could do something like:

Code Select Expand

public function GotUnplugged() as boolean
on error goto hell
   socket.sendData chr(0)
   GotUnplugged = false
   exit function
hell:
   GotUnplugged = true
end function

Would that chr(0) be counted in the amount of data I sent for the anti-flood thing over at Battle.net?

Look it up, it's been discussed many times.

And yes, the char(0) is part of the packet, so I would imagine it counts.

Quote from: CMallette on April 12, 2004, 04:10 PM
Visual Basics..

Oooh -- be careful when saying "Visual Basics" around here -- there are some extremely zealous people who will eat you if you don't remember that it's only singular, not plural.

Try it out a few times...

"Visual Basic"
"Visual Basic"
"Visual Basic"
"I am a newb", er... "Visual Basic"

Quote from: Myndfyre on April 12, 2004, 08:38 PM

Quote from: CMallette on April 12, 2004, 04:10 PM
Visual Basics..

Oooh -- be careful when saying "Visual Basics" around here -- there are some extremely zealous people who will eat you if you don't remember that it's only singular, not plural.

Try it out a few times...

"Visual Basic"
"Visual Basic"
"Visual Basic"
"I am a newb", er... "Visual Basic"

That was cuphead, but he is now otherwise disposed so that's the end of it.

Quote from: CMallette on April 12, 2004, 05:44 PM
Would you happen to know the amount of data you must send to Battle.net before getting disconnected with "Flooded" error and is it different for CHAT and SEXP?

Basically I could do something like:

Code Select Expand

public function GotUnplugged() as boolean
on error goto hell
   socket.sendData chr(0)
   GotUnplugged = false
   exit function
hell:
   GotUnplugged = true
end function

Would that chr(0) be counted in the amount of data I sent for the anti-flood thing over at Battle.net?

Yes, it would; under CHAT the only messages you can send are, well, chat messages. There is no binary protocol layer as exists with the game clients, so all messages count against your flood protection limit. Sending chr(0), however, will most likely get you disconnected immediately -- sending something more friendly, like /whoami or /time, is a better way to check the connection status.

Nice line label, by the way. :)

Quote from: Stealth on April 13, 2004, 12:20 AMNice line label, by the way. :)

This is such a good word, coming from someone new to programming.

Quote from: CMallette on April 12, 2004, 05:44 PM

Code Select Expand

on error goto hell