I've been playing around with the packet structure used in connecting to
battlenet, and am considering making a sort of "battle manager" that turns
the game from a realistic battlefield scenario into something more like a
piece of military software - helping you organize your men, etc. Anyone
know if work like this has already been done?
note: due to the... err... nature.. of this product, I'm not likely to
distribute a working copy of it (if I do it) unless it's set to announce
what it is in-game. This is meant more as a project on battlefield
management and low-level AI, and using it competitively wouldn't be
particularly fair (unless the other person was doing the same).
If you are that talented, visit us on Battle.net. What you are
describing has been done.
Grok
Valhalla Legends
Web: http://www.valhallalegends.com
Battle.Net: use-bncs02.battle.net
Channel: Clan [vL]
How arrogant you are, if your skill in that game is as big as your mouth,
visit us in hell.
.-.
How do I go about that? I assume you mean in one of their lobbies.
>"Grok[vL]" <nos...@email.net> wrote in message
>news:069D93356F53F12E.D59B1BE1...@lp.airnews.net...
>> On Thu, 7 Mar 2002 14:21:46 -0600, "Everett Hickey" <lit...@ev1.net>
>> wrote:
>>
>> >I've heard that there are "bots" that are able to take on the role of an
>> >opponent in starcraft, acting like another copy of the game on the
>network.
>> >
>> >I've been playing around with the packet structure used in connecting to
>> >battlenet, and am considering making a sort of "battle manager" that
>turns
>> >the game from a realistic battlefield scenario into something more like a
>> >piece of military software - helping you organize your men, etc. Anyone
>> >know if work like this has already been done?
>> >
>> >note: due to the... err... nature.. of this product, I'm not likely to
>> >distribute a working copy of it (if I do it) unless it's set to announce
>> >what it is in-game. This is meant more as a project on battlefield
>> >management and low-level AI, and using it competitively wouldn't be
>> >particularly fair (unless the other person was doing the same).
>> >
>>
>> If you are that talented, visit us on Battle.net. What you are
>> describing has been done.
>
>How do I go about that? I assume you mean in one of their lobbies.
>
Oh, just log on USEast, preferably after downloading and installing
our gateway registry entries:
http://www.valhallalegends.com/patches/gateway.reg
That file lets you choose the exact server on which you want to play,
rather than just:
USEast
USWest
Europe
Asia
you get a full list like this:
USEast #1
USEast #2
USEast #3 .. up to USEast #5
USWest #1
USWest #2 .. up to USWest #6
Europe #1
Europe #2
Europe #3
Asia #1
Asia #2 .. all the way to Asia #13
Then just '/join Clan [vL]' to get to our channel. If the bot is on
protect mode and bans you, just try again later. If a member bans
you, don't take it personally, just try again later. In any case,
whisper [vL]Grok and if I'm not away, I will respond quicker if you
whisper that you're a programmer interested in joining.
In the meantime, you might want to read a little bit about our clan,
just go to http://www.valhallalegends.com and click on About [vL], and
Clan Rules. There's enough info there for you to get an idea about
us. We're mostly programmers, network engineers, system
administrators, and hackers. We know far more about the battle.net
protocols than bnetd does, judging by their source code and
documentation. They have a great many undocumented packets which we
have been using for a long time.
I'm usually in the channel in the evening, or very late at night,
Eastern time.
Valhalla Legends is not necessarily a gaming clan. They just like to muck
with the binary protocol that Blizzard uses, and they create bots and other
such fun things. I'm also pretty sure they came up with the Win2K UDP fix
for Starcraft, which was finally implemented in 1.09.
Yeh that was kinda funny. One full year about 1.08 came out, 1.09 was
released and the Win2K UDP thread drop was the only major bug fixed.
About six months before 1.09, we were chatting with Blizzard and asked
why it had never been fixed. The Battle.Net programmer said "If I
knew what was wrong and how to fix it, I would."
That was surprising to us since we had sent no less than 8 detailed
reports in describing exactly the cause of the error and what to do to
fix it.
So this time, Adron and Skywing not only included a description and
discussion of the problem, but reverse engineered the Starcraft code
and converted it back to C, and then fixed it before giving to the
programmer. So all they had to do was paste it in their source and
recompile!
From 1.08 to 1.09 though, we had to rely on SCEnhancements, which is a
product of Skywing's, with derivates from Adron's research. SCE also
has a public version which includes a lot of nice chat enhancements
for battle.net.
We're not quite done patching it up to 1.09b though, since we're so
busy studying Warcraft III Beta and finding bugs there.