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

I don't know how to use the BOT

X

xerxes69

New Member
Joined
Jan 27, 2019
Messages
12
Reaction score
0
I installed DemonBuddy and bought a 1 week KEY. The bot wants me to run Diablo 3 as 32 bit version. I run diablo 3 off the b.net app so how can I do that?

Also is there a setup guide on how to use the bot/install/run it? can someone link me? I don't see any sticky setup guides. Also another thing is when I close the bot I have to reinstall it every time because the bot will not open again once it's closed.

Op. Windows 10
 
In battle.net click on the diablo3 > options > game settings > check launch 32-bit client
upload_2019-1-28_21-35-53.webp
 
If you close the bot and it doesnt re-open. Task manager force close demonbuddy tasks.
 
@rawkus123 DemonBuddy doesn't show up in the taskmanager. Is it under another name? I finally got the bot to work with profiles and it ran through 1 Nef Rift before diablo 3 crashed. Now that it's all messed up I cannot re-open demonbuddy. I'll have to re-install it and configure everything again. Demonbuddy will not even re-open after I've restarted my computer. Any tips?
 
upload your log file as an attachment plz
 
I've figured out a temporary fix. Any time I need to reopen demonbuddy I back up my demonbuddy folder and then uninstall the program. After I reinstall demonbuddy all I do is replace the new demonbuddy folder with my old one so I can keep all of my settings. Kind of a pain but Idk what else to do. The bot seems to run ok as I ran some rifts for about 2 hours with no problem. I just cannot re-open the bot once it's closed. even after a restart of my computer.
 
Negative. I've tried to run it and re-run it with windows defender off. same results. Could it be the frame work? I mean I'm able to get the bot up and running with all of the features. Restarting it seems to be my only problem besides the FPS issues.
 
After searching the forum some more I found your Beta version located here
HTML: 
http://updates.buddyauth.com/GetNewest?filter=DemonbuddyBETA
which is DemonbuddyBETA 1.1.789. I was useing DemonBuddy 1.1.551 before and was not able to restart the program. Now with the new beta 1.1.789 I'm able to restart the bot with no problem. It seems the FPS issue is slightly better than it was before but it's still pretty bad. Also another thing to note is I'm having a problem running GreaterRifts ( I wasn't having problems before ). The hero keeps opening Nef rifts... NOT GreaterRifts. I've checked all the settings 5x and ran the profile 5x (I have 24 keys and gold). I was unable to fix this problem by loading the GreaterRift profile from the old Demonbuddy version. I tried to upload both logs I have but I keep getting an error "File is to large for our server" It's possible that some how the names of the profiles are mixed up but I also checked both xml files, they seem correct.

I'll have to keep using Demonbuddy 1.1.551, The beta version doesn't seem to work when running any type of rift.

List of problems I've encountered Beta 1.1.789
-Hero opens Nef Rifts when I loaded a greaterRift profile.
-Once in nef rift my hero will try to run the rift but end up doubling back to the entrance where he gets stuck and the bot leaves/starts a new game
-Error Reading GreaterRift Keys (in the log) But I have 24 of them and my limit is set to 1

What I tried to do to fix it
-Reinstall beta 1.1.789
-Swap files between beta 1.1.789 and 1.1.551
-After reinstall I was able to run a Nef rift for 2 minutes before he got stuck again and restarted a new game.

(picture of my keys and the log)
https://imgur.com/a/8H2Bw60

An error I get before every Rift I noticed
Code: 
19:55:59,072 [INFO] [Trinity 2.6.448] Set Routine Selection: DemonHunterUnhallowed
19:56:11,285 [INFO] [Trinity 2.6.448] Saving Settings
19:56:11,502 [INFO] [Trinity 2.6.448] Saving Config file
19:57:14,181 [INFO] Loaded profile Adventurer - Nephalem Rift
19:57:19,007 [ERROR] Compiler Error: error CS2012: Cannot open 'C:\Users\Bobby\Desktop\DemonbuddyBETA 1.1.789 (1)\CompiledAssemblies\636843020914399777\TrinityRoutine.dll' for writing -- 'The process cannot access the file 'C:\Users\Bobby\Desktop\DemonbuddyBETA 1.1.789 (1)\CompiledAssemblies\636843020914399777\TrinityRoutine.dll' because it is being used by another process.'



Here is a log of the error I got after the 2 minute Nef Rift run before after he got stuck and it restarted.
Code: 
19:29:16,704 [ERROR] [Trinity 2.6.448] Exception in NephalemRiftTag: System.NullReferenceException: Object reference not set to an instance of an object.
   at Trinity.Components.Adventurer.Coroutines.ExplorationCoroutine.<Exploring>d__23.MoveNext() in C:\Users\Bobby\Desktop\DemonbuddyBETA 1.1.789 (1)\Plugins\Trinity\Components\Adventurer\Coroutines\ExplorationCoroutine.cs:line 211
--- 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`1.GetResult()
   at Trinity.Components.Adventurer.Coroutines.ExplorationCoroutine.<GetCoroutine>d__14.MoveNext() in C:\Users\Bobby\Desktop\DemonbuddyBETA 1.1.789 (1)\Plugins\Trinity\Components\Adventurer\Coroutines\ExplorationCoroutine.cs:line 99
--- 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`1.GetResult()
   at Trinity.Components.Adventurer.Coroutines.ExplorationCoroutine.<Explore>d__2.MoveNext() in C:\Users\Bobby\Desktop\DemonbuddyBETA 1.1.789 (1)\Plugins\Trinity\Components\Adventurer\Coroutines\ExplorationCoroutine.cs:line 28
--- 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`1.GetResult()
   at Trinity.Components.Adventurer.Coroutines.RiftCoroutines.RiftCoroutine.<ClearRift>d__36.MoveNext() in C:\Users\Bobby\Desktop\DemonbuddyBETA 1.1.789 (1)\Plugins\Trinity\Components\Adventurer\Coroutines\RiftCoroutines\RiftCoroutine.cs:line 225
--- 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`1.GetResult()
   at Trinity.Components.Adventurer.Coroutines.RiftCoroutines.RiftCoroutine.<RunRift>d__39.MoveNext() in C:\Users\Bobby\Desktop\DemonbuddyBETA 1.1.789 (1)\Plugins\Trinity\Components\Adventurer\Coroutines\RiftCoroutines\RiftCoroutine.cs:line 331
--- 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`1.GetResult()
   at Trinity.ProfileTags.RiftProfileBehavior.<MainTask>d__22.MoveNext() in C:\Users\Bobby\Desktop\DemonbuddyBETA 1.1.789 (1)\Plugins\Trinity\ProfileTags\RiftTag.cs:line 76
--- 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`1.GetResult()
   at Trinity.Components.QuestTools.BaseProfileBehavior.<Run>d__30.MoveNext() in C:\Users\Bobby\Desktop\DemonbuddyBETA 1.1.789 (1)\Plugins\Trinity\Components\QuestTools\BaseProfileBehavior.cs:line 103




here is some text from the bottom of the logs.
903 Error msg's
Code: 
2019-01-28 23:21:13,181 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.6.448] [Navigation] Failed
2019-01-28 23:21:13,215 [Main Bot Thread] INFO  MainGridProvider (null) - Starting new update routine.
2019-01-28 23:21:13,219 [Main Bot Thread] INFO  MainGridProvider (null) - Starting new update routine.
2019-01-28 23:21:13,218 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.6.448] NavigationCoroutine failed for <483.75, 268.75, -0.05971527> Distance=205.5466, within a range of (specified=15, actual=15). (ExplorationCoroutine.cs > Exploring )
2019-01-28 23:21:13,217 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.6.448] CanFullyClientPath=False
2019-01-28 23:21:13,218 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.6.448] [Navigation] Navigation Error (MoveResult: Failed, Distance: 207.3716) Failures=0.
2019-01-28 23:21:13,249 [Main Bot Thread] INFO  MainGridProvider (null) - Starting new update routine.
2019-01-28 23:21:13,251 [Main Bot Thread] INFO  MainGridProvider (null) - Starting new update routine.
2019-01-28 23:21:13,251 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.6.448] NavigationCoroutine failed for <483.75, 268.75, -0.05971527> Distance=205.5466, within a range of (specified=15, actual=15). (ExplorationCoroutine.cs > Exploring )
2019-01-28 23:21:13,250 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.6.448] CanFullyClientPath=False
2019-01-28 23:21:13,251 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.6.448] [Navigation] Navigation Error (MoveResult: Failed, Distance: 207.3716) Failures=1.
2019-01-28 23:21:13,284 [Main Bot Thread] INFO  MainGridProvider (null) - Starting new update routine.
2019-01-28 23:21:13,286 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.6.448] CanFullyClientPath=False
2019-01-28 23:21:13,286 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.6.448] [Navigation] Navigation Error (MoveResult: Failed, Distance: 207.3716) Failures=2.
2019-01-28 23:21:13,287 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.6.448] NavigationCoroutine failed for <483.75, 268.75, -0.05971527> Distance=205.5466, within a range of (specified=15, actual=15). (ExplorationCoroutine.cs > Exploring )
2019-01-28 23:21:13,287 [Main Bot Thread] INFO  MainGridProvider (null) - Starting new update routine.
2019-01-28 23:21:13,317 [Main Bot Thread] INFO  MainGridProvider (null) - Starting new update routine.
2019-01-28 23:21:13,320 [Main Bot Thread] INFO  MainGridProvider (null) - Starting new update routine.
2019-01-28 23:21:13,319 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.6.448] [Navigation] Navigation Error (MoveResult: Failed, Distance: 207.3716)


Code: 
2019-01-28 23:30:37,449 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.6.448] [ExplorationGrid] Updating grid for scene 'px_festeringWoods_Filler-px_festeringWoods_Filler-X1_LR_Tileset_Exterior_FesteringWoods-{600, 960}-{720, 1080}' with 36 new nodes
2019-01-28 23:30:37,449 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.6.448] [ExplorationGrid] Updating grid for scene 'px_festeringWoods_Filler-px_festeringWoods_Filler-X1_LR_Tileset_Exterior_FesteringWoods-{960, 1080}-{1080, 1200}' with 36 new nodes
2019-01-28 23:30:37,445 [Main Bot Thread] DEBUG Grid`1 (null) - [Update] called.
2019-01-28 23:30:37,445 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.6.448] [ExplorationGrid] Updating grid for scene 'px_festeringWoods_Border_SW_01-px_festeringWoods_Border_SW_01-X1_LR_Tileset_Exterior_FesteringWoods-{720, 1080}-{840, 1200}' with 36 new nodes
2019-01-28 23:30:37,452 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.6.448] [CacheManagement]  Refreshed Hotbar: ActiveSkills=6 PassiveSkills=4
2019-01-28 23:30:37,462 [Main Bot Thread] INFO  DefaultLogger (null) - [Trinity 2.6.448] Buff Cooldown: Power=P2_ItemPassive_Unique_Ring_020 (423244) Start=3874 End=4354 Duration=480 (8s) StartAttr=BuffIconStartTick1 Remaining=7.35s (91.88%) Finished=False Offset=-43 EndOffset=-484 CurrentTime=3917 EndCurrentTime=4358 Key=1 EnvironmentTick=7303140 Variant=
2019-01-28 23:30:37,446 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.6.448] [ExplorationGrid] Updating grid for scene 'px_festeringWoods_Border_NEW_01-px_festeringWoods_Border_NEW_01-X1_LR_Tileset_Exterior_FesteringWoods-{840, 840}-{960, 960}' with 36 new nodes
2019-01-28 23:30:37,462 [Main Bot Thread] INFO  DefaultLogger (null) - [Trinity 2.6.448] Buff Cooldown: Power=X1_DemonHunter_Vengeance (302846) Start=3001 End=4201 Duration=1200 (20s) StartAttr=BuffIconStartTick0 Remaining=6.95s (34.75%) Finished=False Offset=-916 EndOffset=-1333 CurrentTime=3917 EndCurrentTime=4334 Key=0 EnvironmentTick=7303156 Variant=
2019-01-28 23:30:37,463 [Main Bot Thread] INFO  DefaultLogger (null) - [Trinity 2.6.448] Buff Cooldown: Power=P2_ItemPassive_Unique_Ring_038 (430674) Start=3092 End=4052 Duration=960 (16s) StartAttr=BuffIconStartTick8 Remaining=2.95s (18.44%) Finished=False Offset=-825 EndOffset=-1002 CurrentTime=3917 EndCurrentTime=4094 Key=8 EnvironmentTick=7303156 Variant=AllElements
2019-01-28 23:30:37,463 [Main Bot Thread] INFO  DefaultLogger (null) - [Trinity 2.6.448] Skill Cooldown: Power=X1_DemonHunter_Vengeance (302846) Start=3001 End=4702 Duration=1701 (28.35s) StartAttr=PowerCooldownStart Remaining=15.3s (53.97%) Finished=False Offset=-916 EndOffset=-1834 CurrentTime=3917 EndCurrentTime=4835 Key=-1 EnvironmentTick=7303156

Code: 
2019-01-28 23:15:42,677 [Main Bot Thread] DEBUG TargetsCache (null) - [ShouldTargetActor] TARGET: Player, PowerGlobe, HealthGlobe, ProgressionGlobe, BuffedRegion, Gate, BloodShard
2019-01-28 23:15:42,911 [Main Bot Thread] DEBUG TargetsCache (null) - [ShouldTargetActor] TARGET: Player, PowerGlobe, HealthGlobe, ProgressionGlobe, BuffedRegion, Gate, BloodShard
2019-01-28 23:15:43,147 [Main Bot Thread] DEBUG TargetsCache (null) - [ShouldTargetActor] TARGET: Player, PowerGlobe, HealthGlobe, ProgressionGlobe, BuffedRegion, Gate, BloodShard
2019-01-28 23:15:43,386 [Main Bot Thread] DEBUG TargetsCache (null) - [ShouldTargetActor] TARGET: Player, PowerGlobe, HealthGlobe, ProgressionGlobe, BuffedRegion, Gate, BloodShard
2019-01-28 23:16:10,790 [1] INFO  BotMain (null) - Stopping the bot.
2019-01-28 23:16:10,790 [1] INFO  BotMain (null) - Session lasted for: 00:03:23.6843392
2019-01-28 23:16:10,886 [1] DEBUG BotMain (null) - CurrentBot.Stop()
2019-01-28 23:16:11,756 [1] DEBUG BotMain (null) - Navigator.Clear()
2019-01-28 23:16:11,758 [1] DEBUG TreeHooks (null) - Replaced hook [Death] 2e98e206-2f37-4aa7-867d-828d190c7f13
2019-01-28 23:16:11,773 [1] DEBUG ProfileOrderManager (null) - Resetting current behavior.
2019-01-28 23:16:11,759 [1] DEBUG BotMain (null) - OnStop Event Invoking
2019-01-28 23:16:11,758 [1] DEBUG TreeHooks (null) - Replaced hook [VendorRun] 47b0dd68-7bdf-4778-b23b-9561c2a35d81
2019-01-28 23:16:11,759 [1] DEBUG TreeHooks (null) - Inserted new hook [OutOfGame @0] 25bc5721-0f4c-4048-b294-06b0d9901aa2
2019-01-28 23:16:11,756 [1] DEBUG BotMain (null) - TreeHooks.Instance.ClearAll()
2019-01-28 23:16:11,772 [1] DEBUG ProfileOrderManager (null) - [OnBotStop] Resetting caches
2019-01-28 23:16:11,756 [1] INFO  RoutineManager (null) - Chose Trinity as your combat routine
2019-01-28 23:16:11,757 [1] DEBUG TreeHooks (null) - Replaced hook [RoutineCombat] a200e74b-39a1-4684-911f-36c1286ed2cd
2019-01-28 23:16:11,758 [1] INFO  HookManager (null) - Replacing Death Hook
2019-01-28 23:16:11,757 [1] INFO  HookManager (null) - Replacing Combat Hook
2019-01-28 23:16:11,757 [1] DEBUG TreeHooks (null) - Replaced hook [Combat] bfdab7c4-d854-450e-be86-4cf5fd9fa8c2
2019-01-28 23:16:11,759 [1] DEBUG BotMain (null) - OnStop event
2019-01-28 23:16:11,757 [1] INFO  HookManager (null) - Replacing VendorRun Hook
 
Last edited:
you should always use release build,since beta builds are teat builds

pm me your Skype in case you still got issues plz
 
You must log in or register to reply here.
Back
Top