Valhalla Legends Forums Archive | Battle.net Bot Development References | More Packet 0x51 Information

AuthorMessageTime
UserLoser.
BroodWar's Battle.snp:

[pre].text:190178E4 loc_190178E4: ; CODE XREF: Parse0x51+37j
.text:190178E4 cmp eax, 102h
.text:190178E9 jnz short loc_1901795D
.text:190178EB push offset aUserMustReinst ; "user must reinstall and patch"
.text:190178F0 call sub_190023C0
.text:190178F5 add esp, 4
.text:190178F8 pop esi
.text:190178F9 add esp, 8[/pre]

Never seen this, not on BNLS doc - is it still around?
January 1, 2004, 2:22 AM
Skywing
It's another status code that isn't ever used in the wild (Diablo II refers to this as downgrade required).
January 1, 2004, 8:52 PM
Arta
I wonder what would make the server decide to send it... when would you ever need to reinstall as opposed to just applying another patch? Patches don't enforce an earlier version, the updater will quite happily apply an old patch to a current version, so hmmm...
January 1, 2004, 9:04 PM
Skywing
[quote author=Arta[vL] link=board=17;threadid=4543;start=0#msg37949 date=1072991095]
I wonder what would make the server decide to send it... when would you ever need to reinstall as opposed to just applying another patch? Patches don't enforce an earlier version, the updater will quite happily apply an old patch to a current version, so hmmm...
[/quote]
IIRC, the game just puts up an error messagebox and disconnects. Because the patching system can already handle reverting to older versions (automatically), it's even more unlikely that this would ever be used.
January 1, 2004, 9:07 PM
UserLoser.
Hmm, I do remember one time where my brother downloaded a patch on D2, and was forced to reinstall the game
January 1, 2004, 9:16 PM
Skywing
[quote author=UserLoser. link=board=17;threadid=4543;start=0#msg37951 date=1072991794]
Hmm, I do remember one time where my brother downloaded a patch on D2, and was forced to reinstall the game
[/quote]
IIRC, there were two D2 v1.09d versions; if you got the first version, you would have needed to reinstall. However, the server simply reported a failed version check. The time window for getting the bad v1.09d was fairly small (<1hour I believe).
January 1, 2004, 9:26 PM
UserLoser.
Hmm, D2XP's Bnclient.dll, 1.10:

[pre]
.text:6FF02C0C loc_6FF02C0C: ; CODE XREF: Parse0x51+AFj
.text:6FF02C0C cmp esi, 102h
.text:6FF02C12 jnz loc_6FF02D46
.text:6FF02C18 mov ecx, 1
.text:6FF02C1D call sub_6FF06580
.text:6FF02C22 mov dword_6FF1D2C4, ebx
.text:6FF02C28 push offset aUserMustRevert ; "User must revert to an older version"
[/pre]
January 3, 2004, 2:40 AM
Myndfyr
If there was a connection mechanism to connect the D2 1.10 beta to Battle.net (there wasn't one provided in the user interface, but one may have been able to try to hack it), I presume something like this would have surfaced, as well.
January 8, 2004, 1:54 AM

Search