What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Stealth Patch 17956..U.S. Deployed 8:00 pm EST

Status
Not open for further replies.
A

aicgod99

New Member
Joined
Jan 15, 2013
Messages
28
Reaction score
1
New Ninja Patch 17956

This Honorbuddy version only supports WoW Patch 17930 and you are on WoW Patch 17956. Please go to Releases to check for updates.
 
Indeed.

Funny thing: 2 of my accounts are on the same US server. Only 1 of the clients was auto-updated when I logged them on for the first time today.

Upon trying to login, I got a Blizzard Error #112, which as I understand has something to do with Blizz recognizing that files are not where they should be, or the version is not "complete". I do have some of my .EXE files in the WoW install folder renamed, such as Wow-64.exe...

I also noticed something else: a NEW FILE called Scan-64.dll.

This does not exist in the 17930 build.

See attached screenshot:

View attachment 121696
 
mrfoot said:
Indeed.

Funny thing: 2 of my accounts are on the same US server. Only 1 of the clients was auto-updated when I logged them on for the first time today.

Upon trying to login, I got a Blizzard Error #112, which as I understand has something to do with Blizz recognizing that files are not where they should be, or the version is not "complete". I do have some of my .EXE files in the WoW install folder renamed, such as Wow-64.exe...

I also noticed something else: a NEW FILE called Scan-64.dll.

This does not exist in the 17930 build.

See attached screenshot:

View attachment 121696
Click to expand...

We've had scan files since WoTLK if I remember correctly. I found one in my 3.3.5a client.
 
just went to log on 8:30pm EST, and ninja patch confirmed.

HB down again.

Sigh...
 
Jaladhjin said:
I don't mind waiting for updates but why doesn't BuddyUpdater get the update pushed ?

Hunting for them in a Test..Release or Beta thread is kind of annoying.. comparing game version numbers.. ain't nobody got time for that ;-)
Click to expand...


Yeah dude, I agree. It sucks.
 
Jaladhjin said:
I don't mind waiting for updates but why doesn't BuddyUpdater get the update pushed ?

Hunting for them in a Test..Release or Beta thread is kind of annoying.. comparing game version numbers.. ain't nobody got time for that ;-)
Click to expand...

Because in the case that warden was updated virtually everyone would be banned upon logging on with HB. Thats why there are test versions. Use at your own risk type deal till everything is ironed out.
 
We had Scan.dll previously, but I've not seen the Scan-64.dll.new file until today. And I last looked in that folder about a week ago when I was making a batch file to rename Scan.dll to Scan.bak.

I then found out it was pointless because they auto-generate it every time the Client launches. From my Googling, the main function of it is to detect Keyloggers at the time of Login before Warden and whatever else they deploy nowadays has time to load from the Server-side.

It actually can protect you from malicious software, if you're unlucky enough to get logged and lucky enough for WoW to pick up on the fact.

I only assume Scan-64.dll.new is something similar, likely intended to be a security enhancement. I know 32-bit and 64-bit memory spaces are quite different, from my experience trying to Sandbox programs.

I'm sure the Dev's already know all about what it is and will ensure it's not able to unravel the threads of HB as always. But it's interesting to see new files being injected behind the scenes onto my computer which are designed to read resident processes.
 
mrfoot said:
Indeed.

Funny thing: 2 of my accounts are on the same US server. Only 1 of the clients was auto-updated when I logged them on for the first time today.

Upon trying to login, I got a Blizzard Error #112, which as I understand has something to do with Blizz recognizing that files are not where they should be, or the version is not "complete". I do have some of my .EXE files in the WoW install folder renamed, such as Wow-64.exe...

I also noticed something else: a NEW FILE called Scan-64.dll.

This does not exist in the 17930 build.

See attached screenshot:

View attachment 121696
Click to expand...

I got the same error but it has resolved itself now
 
maniac69 said:
checks when u run game what os ur running 32/64bit ur running and has been in the folder the a while , times i renamed it to fool the launcher
Click to expand...

maniac69: It's not currently in any of my folders which are still on Build 17930... But then again I rarely run 64-bit or use the Launcher to load... I wonder it just like Scan.dll, Scan-64.dll will auto-generate whenever you launch 64-bit Client? If so, then this would indeed not be anything new or worth my mentioning.
 
Status
Not open for further replies.
Back
Top