Valhalla Legends Archive

Member Forums => Spht's Forum => Topic started by: Joe[x86] on August 24, 2006, 10:48 PM

Title: SphtBot -- SID_REQUIREDWORK ix86BlueDrake.mpq
Post by: Joe[x86] on August 24, 2006, 10:48 PM
[22:44:47] Connected to Battle.net!
[22:44:47] Connected to Battle.net logon server!
[22:44:47] Logon protocol set to NLS v1.01.
[22:44:47] Checking versions and CD-key...
[22:44:47] New IX86ver0.mpq available, downloading...
[22:44:49] Passed version and CD-key check!
[22:44:49] Attempting to log on...
[22:44:49] Unrecognized BNCS packet SID_004C received:
0000:  69 78 38 36 42 6C 75 65 44 72 61 6B 65 2E 6D 70   ix86BlueDrake.mp
0010:  71 00                                             q.
[22:44:50] Successfully downloaded IX86ver0.mpq from Battle.net!
[22:44:50] Verifying logon proof...
[22:44:51] Successfully logged on!

According to Hdx:
[22:46:35] <Hdx@USEast> Joe
[22:46:40] <Hdx@USEast> Everyone gets that.
[22:46:53] <Hdx@USEast> Theve been using blue drake for about four months IIRC.
Title: Re: SphtBot -- SID_REQUIREDWORK ix86BlueDrake.mpq
Post by: UserLoser on August 24, 2006, 11:38 PM
Yes..this is rather old news.  Since mid June Battle.net has been requiring an extrawork library to be executed to patch disconnect/scroll/maphacks.  By doing so, it saves them from compiling a new patch for something so simple.
Title: Re: SphtBot -- SID_REQUIREDWORK ix86BlueDrake.mpq
Post by: Spht on August 25, 2006, 10:59 AM
Installing KillExtraWork.bcp (http://www.valhallalegends.com/spht/plugins/KillExtraWork.bcp) will prevent that notification from displaying on the bot.
Title: Re: SphtBot -- SID_REQUIREDWORK ix86BlueDrake.mpq
Post by: UserLoser on August 25, 2006, 12:02 PM
Quote from: Spht on August 25, 2006, 10:59 AM
Installing KillExtraWork.bcp (http://www.valhallalegends.com/spht/plugins/KillExtraWork.bcp) will prevent that notification from displaying on the bot.

Are you sure KillExtraWork ignores 0x4a and 0x4c?
Title: Re: SphtBot -- SID_REQUIREDWORK ix86BlueDrake.mpq
Post by: Joe[x86] on August 27, 2006, 12:52 AM
Ah, I was wondering what it did.