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

[Release] Demonbuddy Release Thread

Status
Not open for further replies.
[16:04:49.104 N] Demonbuddy v1.0.422.79 started
[16:04:51.675 N] Logging in...
[16:04:51.933 N]
[16:04:51.953 N] Error attaching to Diablo III, Reason:System.IO.FileNotFoundException: Could not load file or assembly 'fasmdll_managed, Version=1.0.422.79, Culture=neutral, PublicKeyToken=f20f8f99ca0718ca' or one of its dependencies. The system cannot find the file specified.
File name: 'fasmdll_managed, Version=1.0.422.79, Culture=neutral, PublicKeyToken=f20f8f99ca0718ca'
at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
 
Last edited:
womping said:
Hi guys how do i fix this



WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Click to expand...

make sure that net framework 4 and VIsual C stuff is installed as described on first post
use the specific links
alo make sure that your windows are updated(after the installation)
 
17:06:36.961 N] Demonbuddy v1.0.422.79 started
[17:06:39.489 N] Logging in...
[17:06:40.578 N]
[17:06:40.678 N] Error attaching to Diablo III, Reason:System.AccessViolationException: Could not read bytes from 7272CE09 [299]!
at Zeta.MemoryManagement.ExternalProcessReader.(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.[T](IntPtr address, Boolean isRelative)
at ...ctor(ExternalProcessReader memory, IntPtr endscene)
at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)


I have installed all the updates and everything in the first post.
 
Just looks very odd :S
this is the only way i can show what i mean = [video=youtube;tKoezHCuyF0]http://www.youtube.com/watch?v=tKoezHCuyF0&feature=youtu.be[/video]
i mean it skips objects, and mobs / and basically has very wierd movement.
 
Jonte said:
17:06:36.961 N] Demonbuddy v1.0.422.79 started
[17:06:39.489 N] Logging in...
[17:06:40.578 N]
[17:06:40.678 N] Error attaching to Diablo III, Reason:System.AccessViolationException: Could not read bytes from 7272CE09 [299]!
at Zeta.MemoryManagement.ExternalProcessReader.(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.[T](IntPtr address, Boolean isRelative)
at ...ctor(ExternalProcessReader memory, IntPtr endscene)
at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)


I have installed all the updates and everything in the first post.
Click to expand...

run D3 and DB as admin
 
I was able to fix the crash.

Here is a stack trace for the devs:

System.AccessViolationException was unhandled
Message=Could not read bytes from 00000000 [299]!
Source=Demonbuddy
StackTrace:
at Zeta.MemoryManagement.ExternalProcessReader.(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.[T](IntPtr address, Boolean isRelative)
at Zeta.Internals.Service.BnetHero.()
at Zeta.Internals.Service.BnetHero.get_BattleTagName()
at Zeta.CommonBot.Settings.CharacterSettings..ctor()
at Zeta.CommonBot.Settings.CharacterSettings.get_Instance()
at Demonbuddy.MainWindow.HandleSuccess()
at Demonbuddy.MainWindow.<Authenticate>b__7(Object o)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
InnerException:


The answer is obvious: You have to log in first.
 
nupogodi said:
I was able to fix the crash.

Here is a stack trace for the devs:

System.AccessViolationException was unhandled
Message=Could not read bytes from 00000000 [299]!
Source=Demonbuddy
StackTrace:
at Zeta.MemoryManagement.ExternalProcessReader.(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.[T](IntPtr address, Boolean isRelative)
at Zeta.Internals.Service.BnetHero.()
at Zeta.Internals.Service.BnetHero.get_BattleTagName()
at Zeta.CommonBot.Settings.CharacterSettings..ctor()
at Zeta.CommonBot.Settings.CharacterSettings.get_Instance()
at Demonbuddy.MainWindow.HandleSuccess()
at Demonbuddy.MainWindow.<Authenticate>b__7(Object o)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
InnerException:


The answer is obvious: You have to log in first.
Click to expand...

lols, thanks.
 
nupogodi said:
I was able to fix the crash.

Here is a stack trace for the devs:

System.AccessViolationException was unhandled
Message=Could not read bytes from 00000000 [299]!
Source=Demonbuddy
StackTrace:
at Zeta.MemoryManagement.ExternalProcessReader.(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.[T](IntPtr address, Boolean isRelative)
at Zeta.Internals.Service.BnetHero.()
at Zeta.Internals.Service.BnetHero.get_BattleTagName()
at Zeta.CommonBot.Settings.CharacterSettings..ctor()
at Zeta.CommonBot.Settings.CharacterSettings.get_Instance()
at Demonbuddy.MainWindow.HandleSuccess()
at Demonbuddy.MainWindow.<Authenticate>b__7(Object o)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
InnerException:


The answer is obvious: You have to log in first.
Click to expand...

I got this error, doesnt work even if I'm logged in :/ I run both D3 and DB as admin, still no go.
 
I really don't wanna be harsh, but... it's impossible not to. Hope you take the following as constructive as possible:

* It's slow as fuck
* It stops for several seconds (I assume this is in between hotspots)
* Doesn't loot chests (maybe it does if you set your loot radius to more than 0, but if you know anything about how farming gold works, you'd know that you don't wanna loot, but "absorb" gold via pick up radius)
* Doesn't break breakables
* It backtracks (I assume it backtracks to the hotspot if it goes off chasing mobs and passes it by)
* Doesn't sustain combat. I just watched it let a treasure goblin port out no problem.
* Doesn't use abilities "out of combat", meaning no chain Sprint for barbarians.
* Did I mention it's slow as fuck?

I love you guys and HB is the best thing to ever happen to my WoW career, but words cannot express just how disappointed I am in this aberration.
Now I actually believe Hawker when he said this wasn't good enough. It still isn't.

I really hope that by the time VS gets put out of business you have evolved this into a quality product.

Thanks, but no thanks.

That said, much <3.
 
Toney001 said:
I really don't wanna be harsh, but... it's impossible not to. Hope you take the following as constructive as possible:

* It's slow as fuck
* It stops for several seconds (I assume this is in between hotspots)
* Doesn't loot chests (maybe it does if you set your loot radius to more than 0, but if you know anything about how farming gold works, you'd know that you don't wanna loot, but "absorb" gold via pick up radius)
* Doesn't break breakables
* It backtracks (I assume it backtracks to the hotspot if it goes off chasing mobs and passes it by)
* Doesn't sustain combat. I just watched it let a treasure goblin port out no problem.
* Doesn't use abilities "out of combat", meaning no chain Sprint for barbarians.
* Did I mention it's slow as fuck?

I love you guys and HB is the best thing to ever happen to my WoW career, but words cannot express just how disappointed I am in this aberration.
Now I actually believe Hawker when he said this wasn't good enough. It still isn't.

I really hope that by the time VS gets put out of business you have evolved this into a quality product.

Thanks, but no thanks.

That said, much <3.
Click to expand...

This.
 
"Thanks for buying Demonbuddy - the 3rd party iablo 3 Bot."
From my email. Not a bug. But a typo. :P
 
[11:24:38.433 N] Demonbuddy v1.0.422.79 started
[11:25:03.677 N] Logging in...
[11:25:04.052 N]



This is all that happens everytime I login to the bot with my CD key they sent me.... the eff? No install instructions either?
 
Excellent bot, works great, plays safe as to avoid detection. Well done!

Only thing you gotta fix atm is the bot attacking sentries, that would give it away if a Blizz employee was watching.
 
Well prices are great.. and well, no wonder for how crappy it works now... You said that it will blow us away and every other bot will be crap.. But from what I see on stream is, that every other bot blows this away... I'm sure, that demonbuddy will be someday the best d3 bot.. but for now its no alternative for me... :sad:
 
Status
Not open for further replies.
Back
Top