Automatic Verbyte updates?

[Topaz]

I've heard talk of this, but no one's really taken the initiative to announce it.

I propose that someone reverse engineer starcraft/broodwar and find the specific line that the verbyte is stored in. if possible, you could read from that line in the exe for the verbyte, thus eliminating the need for a verbyte change, so that the user only needs install new hashes.

[Networks]

I don't think that's possible but I am sure you can impliment a function to increment the verbyte to a correct one until it logs on. Such as Starcraft, since it increments by two. (IE: C5 to C7 to C9)

[Topaz]

And then you have the various skips from C9 to CB. Maybe start in hex, seeing as how C9 was 201, and CB is 203? There could be a conversion function, but blizzard can be unreliable. You'd also have to set options to change the current pattern, or have a mandatory update where it changes.

[tA-Kane]

BNLS is perfect for this.

You do not need to login to use BNLS.

You do not need to send your username or password or cd key to get the current version byte for any product.

[CrAz3D]

BNLS is perfect for this.

You do not need to login to use BNLS.

You do not need to send your username or password or cd key to get the current version byte for any product.

BNLS isn't the fastest thing that is updated though

[UserLoser.]

I've heard talk of this, but no one's really taken the initiative to announce it.

I propose that someone reverse engineer starcraft/broodwar and find the specific line that the verbyte is stored in. if possible, you could read from that line in the exe for the verbyte, thus eliminating the need for a verbyte change, so that the user only needs install new hashes.

UserLoser already did that, but never made use of it.  Someone resend me Starcraft.exe/battle.snp

[iago]

BNLS is perfect for this.

You do not need to login to use BNLS.

You do not need to send your username or password or cd key to get the current version byte for any product.

BNLS isn't the fastest thing that is updated though

So far, since I made RCRS (which is a weaker version of BNLS), the score is 1-1 (although I beat them by a day, and then they beat me by a few minutes )

But yeah, I found that part of Battle.snp a long time ago, but never made use of it :/

[Warrior]

I agree with Networks,  add 2 to the current VerByte if you fail version check in 0x51

[tA-Kane]

What if your bot is so old that the bot is outdated by 20 version bytes?

[MyndFyre]

What if your bot is so old that the bot is outdated by 20 version bytes?

Then it'll take a while to log in. 

[R.a.B.B.i.T]

Or have the user set a version byte in the config, and if it's not there go with the current byte.  If it failes version check, increment.  When it works, save the version byte.

[Topaz]

Or just read from battle.snp?

[Newby]

What if, by some horrible glitch in the bot that occured only once in a thousand blue moons, you sent the correct version byte but parsed the incoming data as stating it was wrong?

You'd be incrementing forever.

[Hdx]

Thats why you set a limit, Blizzard WILL NOT put out  50 patches without you noticing and updating your bot.
~-~(HDX)~-~

[Newby]

What if the bot producer stopped producing bots? How would it know?