[17:59:41.827] exceptions.InvalidVersion: Old game version (it wants you to download D2DV_IX86_111a_111b.mpq)
VerByte: 0x0B (Unchanged)
Verhash: 0x01000B00 (Unchanged.. Wierd..)
D2DV hashes: Here (Http://hdx.no-ip.org/Hashes/D2DV.zip)
D2XP hashes: Here (Http://hdx.no-ip.org/Hashes/D2XP.zip)
Patch Log:
Quote--------------------------------------------------------------------------
- Patch 1.11b
--------------------------------------------------------------------------
FIXES:
- Fixed a bug that could cause a crash when you return to chat after
playing a game on Battle.net.
- Fixed a bug that could cause a crash when the runeword "Peace" was
equipped on a hireling.
my packet logs show that the verhash asnt changed.. can someone conferm this plz? But the hashes work :P
~-~(HDX)~-~
[Mis-Informed]
If thats true.. Why dont we need to update SC/WC2/WC3 binaries?
~-~(HDX)~-~
Quote from: LordNevar on September 13, 2005, 06:30 PM
Please Note: That Battle.net updated all the clients today, including Warcraft II, this was not just a stationary patch for a specific game, this affected all games due to an unpdate to battle.net servers.
...no?
Quote from: LordNevar on September 13, 2005, 06:30 PM
an update to battle.net servers.
(Typo fixed in your post).
[19:49:25:1225] [BNET] - Connecting.
[19:49:25:1225] [BNET] - Connection Established.
[19:49:25:1225] [BNET] - Sending Login Information.
[19:49:26:1226] [BNET] - New Patch Required: (SEXP_IX86_113d_113e.mpq)
[19:49:26:1226] [BNET] - Disconnected.
Was mis informed, retract previous comment, was gone for 2 days, didn't know the clients updated previously.
1.13e was released the 12th. (yesterday)
Wc2 and wc3 have yet to patch, So your post is incorrect. They could be working on a new patch right now yes..
~-~(HDX)~-~
[edit]
Saw your edit after posting :P
There was a thread about 1.13e in this forum should of seen it .
~-~(HDX)~-~
I was gone for 2 days, and my bots were still on, I was told about 20 min ago, that there was an update when I was gone, sorry information was mishandled.
D2Game.dll? Edit: has that always been in there?
it dosent have D2Game.dll
D2 version binaries are Game.exe, D2Client.dll, BNclient.dll
And those are the files I ahve in the zip
~-~(HDX)~-~
Quote from: HdxBmx27 on September 13, 2005, 08:13 PM
it dosent have D2Game.dll
D2 version binaries are Game.exe, D2Client.dll, BNclient.dll
And those are the files I ahve in the zip
~-~(HDX)~-~
I updated and noticed D2Game.dll in my folder. Never seen that before :P Or maybe I never payed attention to that file.
Quote from: dxoigmn on September 13, 2005, 08:27 PM
Quote from: HdxBmx27 on September 13, 2005, 08:13 PM
it dosent have D2Game.dll
D2 version binaries are Game.exe, D2Client.dll, BNclient.dll
And those are the files I ahve in the zip
~-~(HDX)~-~
I updated and noticed D2Game.dll in my folder. Never seen that before :P Or maybe I never payed attention to that file.
D2Game.dll has always been there <.<
Quote from: l2k-Shadow on September 13, 2005, 09:26 PM
D2Game.dll has always been there <.<
Hahah okay. I guess I never paid attention to it :P
Hate to bring this back up, but maybe the time table in my post was wrong, looks like all clients but WC2 have been updated so far. Which leads me to believe one of 2 things, that the games are really messed up, and Blizzard/Battle.net have no idea how to fix them or what there doing. Or they have something else going on behind the scenes, and the reason Warden has been inactive lately is it. I don't have any of the clients installed or I would do it myself, if someone would be gracious enough to get me a packet log of D2, and W3 game creation It would be much appreciated. I would like to take a look at a few thing's and see what it is that there trying to do if anything.
Blizzard's developers aren't a bunch of cyberpunks armed with keyboards. I'm sure they know what they're doing.
Or, they're making balance changes and fixing crash bugs.
Or, making warden rock. :P
Quote from: Blaze on September 20, 2005, 02:28 PMOr, making warden rock. :P
I'll be happy if they ever fix the bug that caused it to ban people who used Logitech mice (like me).
My guess is that the people doing the patches are 3rd or 4th generation code teams, and have a half-ass idea of what the original and pre-them code is doing.
Quote from: rabbit on September 20, 2005, 08:53 PM
My guess is that the people doing the patches are 3rd or 4th generation code teams, and have a half-ass idea of what the original and pre-them code is doing.
If that were the case, we can expect a lot of patches in the upcoming months.
Back to the comment about the servers going down...
One of our webbots (a StealthBot using STW) showed that at least one USWest server went down for maintenance...
And it does seem odd that all these games would be updated at the same time, doesn't it?
No, why would that be? The timing means nothing, Blizzard is just trying to improve the online service. Why is that odd?
It's odd because SC get's 4 patches, even though it hasn't had any recently. WC3 also has had a patch, and the last time it updated was some time ago...on top of that, Diablo II got 2. All this within...I don't know how long.
SC 1.13 was released 6-29-05
WC 1.19b was released 9-21-05
They wernt THAT fast :/
~-~(HDX)~-~
QuoteSeptember 12, 2005
StarCraft Patch v1.13e
The StarCraft Patch v1.13e has been released to fix several bugs that contributed to game exploits. If you experience any errors while patching, please visit our troubleshooting page here.
http://www.blizzard.com/support/?
Corrent, I was refering to 1.13a
heres the full list:
SC 1.13a 6-29-05
D2 1.11a 8-01-05
SC 1.13b 8-11-05
SC 1.13c 8-22-05
SC 1.13d 9-06-05
SC 1.13e 9-12-05
D2 1.11b 9-13-05
W3 1.19a 9-19-05
W3 1.19b 9-21-05
~-~(HDX)~-~
Regular updates is something you should be glad for, because it minimizes hacking.
Perhaps he wants to hack...
Quote from: Explicit[nK] on September 24, 2005, 01:36 AM
Perhaps he wants to hack...
Naw i rarly play any of those games. I dont use this comp for gaming.
Oh well :/
~-~(HDX)~-~
They probably meant me.
But someone said somethinga bout how 1.13d fixed a bug from 1.13b...