[Guide] Optimize your Botting [Windows/Honorbuddy/WoW/VMWare]

Try the new VMware Workstion 11: VMware Workstation: Multiple Operating Systems Linux, Windows 8 & More | United States

There you can increase the virtual video memory up to 2gb.

 

give your wows a higher priority...

 

I've set high priority to wow and hb : same problem

And I already bought a used licence for VM10 and people who use VM10 dont have this problem ...

 

setting on pm

 

This thread is awesome. bl4ck you are awesome.
So many things that make a huge difference.
Long live the thread!

 

Indeed thanks bl4ck, i did everything you said i'm now at 15fps on all 5 bots, it's not really fluid but its enough to no die in dongeons I will try to get what I'm doing wrong when I've time

Thanks again

 

You have 15 fps! if you want set more like 20.

 

Indeed, but even with a 15fps setting I still drop to 5-7fps during fights so I dont want to touch it
Seems the problem is related to the processor now, used 1 processor and 6 cores, virtualisation and HT enabled with my i7 3770k and I'm almost @100%, seems a VMware configuration problem

 

Set 1 cpu and 4 cores and run pls only one bot(any dungeon) in vm and let me know what it is cpu usage in host and guest but after ~ 10 min than you run.

 

1 cpu and 4 cores makes absolutely no sense

 

for managing reasons. you can much easier manage your bots if u are running like 10 bots or tho

 

Can I run 2 bots on the same PC? with vpn ofc!

 

Hey my Problem is that HB doesnt start more then 3x didnt know why - can anyone help me and maybe optimized my vm more

would pay for the time
write me email pls support@spuds-gaming.de

[18:53:01.364 N] Honorbuddy v2.5.12646.765 started.
[18:53:01.845 N] Logging in...
[18:53:04.284 N] T: 5247264106246572461 H: 1677147062
[18:53:08.813 D] System.ArgumentException: Process with an Id of 3804 is not running.
at System.Diagnostics.Process.GetProcessById(Int32 processId, String machineName)
at System.Diagnostics.Process.GetProcessById(Int32 processId)
at Honorbuddy.MainWindow.<FindAndAttachToWoW>d__50.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Honorbuddy.MainWindow.<HandleSuccess>d__28.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Honorbuddy.MainWindow.<AfterAuth>d__1b.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Honorbuddy.MainWindow.<Authenticate>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Honorbuddy.MainWindow.<Window_Loaded>d__82.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__4(Object state)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

 

Is there an updated wtf.config file please ?

 

Im interested in this as well for the 6.1 patch

 

Yes upgrade please

 

We need bl4ck =D

 

I've read through some posts with some individuals claiming that Blizzard can see your MAC address. Incorrect! The only device that will ever see your MAC address is the initial router with your ISP requesting datagram packets, beyond that Blizzard has no access to it.

MAC address's are not sent through the header! A MAC address is a layer 2 protocol.
https://panopticlick.eff.org/

 

Is World of Warcraft a browser game?

 

If Blizz would let you start managing your garrison via browser or app I would say yes