What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
hi everyone anyone can't setup the program like this cause you can't add new?

NShG0vX.jpg

Go to Control Panel\Appearance and Personalization\Display -> Make text or other items larger and smaller and set to default (100%)
 
Go to Control Panel\Appearance and Personalization\Display -> Make text or other items larger and smaller and set to default (100%)
I didn't even know about that, thanks!

To everyone having problems with DB freezing/not starting in the first run: could you please attach a DB log of when that happens? I'm having some trouble reproducing this one.
 
I didn't even know about that, thanks!

To everyone having problems with DB freezing/not starting in the first run: could you please attach a DB log of when that happens? I'm having some trouble reproducing this one.
DB:
Attached to Diablo 3 with pid:6784
current bot set to Order Bot
Loaded profile YAR Kickstart
Chose Trinity as your combat routine
Loaded profile YAR Kickstart
Chose Trinity as your combat routine
Logging into game

YAR:
N [2016/3/4 星期五 上午 12:36:56] <Acc2_Mage> We are scheduled to start
N [2016/3/4 星期五 上午 12:36:56] <Acc2_Mage> Next scheduled stop: 4/3 0:0
N [2016/3/4 星期五 上午 12:36:56] <Acc2_Mage> Language set: Chinese : zhCN
N [2016/3/4 星期五 上午 12:36:56] <Acc2_Mage> Region set: China : cn.actual.battle.net
N [2016/3/4 星期五 上午 12:37:14] <Acc2_Mage> Diablo:6784: Found D3 Main Window (1114488)
N [2016/3/4 星期五 上午 12:37:19] <Acc2_Mage> Diablo:6784: Waiting for process to become ready
N [2016/3/4 星期五 上午 12:37:20] <Acc2_Mage> Diablo:6784: Process is ready
N [2016/3/4 星期五 上午 12:37:20] <Acc2_Mage> Demonbuddy start delay, waiting 5 seconds
N [2016/3/4 星期五 上午 12:37:25] <Acc2_Mage> Installing latest plugin: D:\DB\mage\Plugins\YAR\Plugin.cs
N [2016/3/4 星期五 上午 12:37:25] <Acc2_Mage> Installing latest bot: D:\DB\mage\Bots\YARBot\YARBot.cs
N [2016/3/4 星期五 上午 12:37:25] <Acc2_Mage> Demonbuddy:1612: Waiting for process to become ready
N [2016/3/4 星期五 上午 12:37:26] <Acc2_Mage> Found Demonbuddy - BETA: MainWindow (918566)
N [2016/3/4 星期五 上午 12:37:26] <Acc2_Mage> Demonbuddy:1612: Process is ready
N [2016/3/4 星期五 上午 12:37:26] <Acc2_Mage> Demonbuddy:1612: Waiting for demonbuddy to log into Diablo
 
Last edited:
HI,

Believe this is to relog in case D3 crash right ?
can anyone point me to any folder that clearly show how to set this up.

Thanks
 

Attachments

Last edited:
What exactly means kickstart? Should I check both boxes in kickstart or not?
Right now it doesn't matter if you enable it or not as we made it run by default to avoid some common problems with yar. Kickstart is the name rrrix gave to the code that makes sure DB doesn't crap itself when trying to load big profiles.

DB:
Attached to Diablo 3 with pid:6784
current bot set to Order Bot
Loaded profile YAR Kickstart
Chose Trinity as your combat routine
Loaded profile YAR Kickstart
Chose Trinity as your combat routine
Logging into game

YAR:
N [2016/3/4 星期五 上午 12:36:56] <Acc2_Mage> We are scheduled to start
N [2016/3/4 星期五 上午 12:36:56] <Acc2_Mage> Next scheduled stop: 4/3 0:0
N [2016/3/4 星期五 上午 12:36:56] <Acc2_Mage> Language set: Chinese : zhCN
N [2016/3/4 星期五 上午 12:36:56] <Acc2_Mage> Region set: China : cn.actual.battle.net
N [2016/3/4 星期五 上午 12:37:14] <Acc2_Mage> Diablo:6784: Found D3 Main Window (1114488)
N [2016/3/4 星期五 上午 12:37:19] <Acc2_Mage> Diablo:6784: Waiting for process to become ready
N [2016/3/4 星期五 上午 12:37:20] <Acc2_Mage> Diablo:6784: Process is ready
N [2016/3/4 星期五 上午 12:37:20] <Acc2_Mage> Demonbuddy start delay, waiting 5 seconds
N [2016/3/4 星期五 上午 12:37:25] <Acc2_Mage> Installing latest plugin: D:\DB\mage\Plugins\YAR\Plugin.cs
N [2016/3/4 星期五 上午 12:37:25] <Acc2_Mage> Installing latest bot: D:\DB\mage\Bots\YARBot\YARBot.cs
N [2016/3/4 星期五 上午 12:37:25] <Acc2_Mage> Demonbuddy:1612: Waiting for process to become ready
N [2016/3/4 星期五 上午 12:37:26] <Acc2_Mage> Found Demonbuddy - BETA: MainWindow (918566)
N [2016/3/4 星期五 上午 12:37:26] <Acc2_Mage> Demonbuddy:1612: Process is ready
N [2016/3/4 星期五 上午 12:37:26] <Acc2_Mage> Demonbuddy:1612: Waiting for demonbuddy to log into Diablo
Is that all of the DB log? Doesn't it even log in successfully?

HI,

Believe this is to relog in case D3 crash right ?
can anyone point me to any folder that clearly show how to set this up.

Thanks
It is. There's a guide somewhere in the guides section if you want, but it's really not hard to set up. Just go to the LatestBuild folder and run the .exe, then click New and follow the steps.

i didnt install autofollow
where can i find that?
AutoFollow is not necessary to run YAR, it's just a plugin for multibotting, so don't worry (unless you want to multibot :))
 
It logged in successfully, but DB will be freezing after that (more specifically, about 2 or 3 seconds after log in).
 
I feel like an idiot... but I don't know how to add the bot. It doesn't have the 'add' button or scheduler like in https://www.thebuddyforum.com/demonbuddy-forum/plugins/82535-standalone-relogger.html, and I don't see anything in the settings for it either. Am I missing something easy?

ruB4J8e.png

Yes you are missing big time.
First you have to find the folder named " Latest build" in this relogger program.
The inside of "Latest build " folder has a icon.
you click the icon and it will all start correctly. Then you press "new" button" on the middle of the section, far right side of the relogger.
and follow prompt.
 
Last edited:
Use the symlink instead of the actual .exe

Hi Jubisman, Thanks for the hard work and keep this valuable program alive.

what is symlink? do you mean short cut link? I used the short cut link and DB freezes for good.
DB showed following:

Attached to Diablo III with PID 2300
Current bot set to Order Bot
Loaded profile YAR kickstart
Choose Trinity as your combat routine
Loaded profile Yar Kickstart
Choose Trinity as your combat routine
Logging into game

Then, frozen....
 
Last edited:
DB:
Attached to Diablo 3 with pid:6784
current bot set to Order Bot
Loaded profile YAR Kickstart
Chose Trinity as your combat routine
Loaded profile YAR Kickstart
Chose Trinity as your combat routine
Logging into game

YAR:
N [2016/3/4 星期五 上午 12:36:56] <Acc2_Mage> We are scheduled to start
N [2016/3/4 星期五 上午 12:36:56] <Acc2_Mage> Next scheduled stop: 4/3 0:0
N [2016/3/4 星期五 上午 12:36:56] <Acc2_Mage> Language set: Chinese : zhCN
N [2016/3/4 星期五 上午 12:36:56] <Acc2_Mage> Region set: China : cn.actual.battle.net
N [2016/3/4 星期五 上午 12:37:14] <Acc2_Mage> Diablo:6784: Found D3 Main Window (1114488)
N [2016/3/4 星期五 上午 12:37:19] <Acc2_Mage> Diablo:6784: Waiting for process to become ready
N [2016/3/4 星期五 上午 12:37:20] <Acc2_Mage> Diablo:6784: Process is ready
N [2016/3/4 星期五 上午 12:37:20] <Acc2_Mage> Demonbuddy start delay, waiting 5 seconds
N [2016/3/4 星期五 上午 12:37:25] <Acc2_Mage> Installing latest plugin: D:\DB\mage\Plugins\YAR\Plugin.cs
N [2016/3/4 星期五 上午 12:37:25] <Acc2_Mage> Installing latest bot: D:\DB\mage\Bots\YARBot\YARBot.cs
N [2016/3/4 星期五 上午 12:37:25] <Acc2_Mage> Demonbuddy:1612: Waiting for process to become ready
N [2016/3/4 星期五 上午 12:37:26] <Acc2_Mage> Found Demonbuddy - BETA: MainWindow (918566)
N [2016/3/4 星期五 上午 12:37:26] <Acc2_Mage> Demonbuddy:1612: Process is ready
N [2016/3/4 星期五 上午 12:37:26] <Acc2_Mage> Demonbuddy:1612: Waiting for demonbuddy to log into Diablo
Hi Jubisman, Thanks for the hard work and keep this valuable program alive.

what is symlink? do you mean short cut link? I used the short cut link and DB freezes for good.
DB showed following:

Attached to Diablo III with PID 2300
Current bot set to Order Bot
Loaded profile YAR kickstart
Choose Trinity as your combat routine
Loaded profile Yar Kickstart
Choose Trinity as your combat routine
Logging into game

Then, frozen....

The same with you.
DB version: 456.
I`ve tried the version released from Feb.22 & 28. All of them were freezing like this:
DB:
2016-03-06 04:03:17,444 [1] INFO MainWindow (null) - Demonbuddy v1.1.2977.456 started
2016-03-06 04:03:17,504 [1] INFO MainWindow (null) - Logging in...
2016-03-06 04:03:17,626 [3] DEBUG MainWindow (null) - Logging in to China (123.57.29.72)
2016-03-06 04:03:17,696 [3] INFO MainWindow (null) - T: 5247614356403666869 H: 3284566531
2016-03-06 04:03:18,146 [1] INFO MainWindow (null) - Attached to Diablo III with pid: 6668
2016-03-06 04:03:18,146 [1] DEBUG MainWindow (null) - Executable Path: E:\KCBLZ\D3DB\Demonbuddy 1.1.2977.456XMDJ78\Demonbuddy.exe
2016-03-06 04:03:18,146 [1] DEBUG MainWindow (null) - Platform: Microsoft Windows NT 6.1.7601 Service Pack 1
2016-03-06 04:03:18,151 [1] DEBUG AssemblyLoader`1 (null) - Reloading AssemblyLoader<Zeta.Bot.IBot> - BotManager.Reload
2016-03-06 04:03:22,696 [1] DEBUG BotManager (null) - Bots were reloaded. New bot list:
2016-03-06 04:03:22,696 [1] DEBUG BotManager (null) - YARKickstart v0.0.0.0
2016-03-06 04:03:22,696 [1] DEBUG BotManager (null) - Combat Bot v1.1.2977.456
2016-03-06 04:03:22,696 [1] DEBUG BotManager (null) - Script Runner v1.1.2977.456
2016-03-06 04:03:22,696 [1] DEBUG BotManager (null) - Order Bot v1.1.2977.456
2016-03-06 04:03:23,276 [1] INFO BotMain (null) - Current bot set to Order Bot
2016-03-06 04:03:23,276 [1] INFO ProfileManager (null) - Loaded profile YAR Kickstart
2016-03-06 04:03:23,321 [1] DEBUG AssemblyLoader`1 (null) - Reloading AssemblyLoader<Zeta.Bot.ICombat> - RoutineManager.Reload
2016-03-06 04:03:23,561 [1] INFO RoutineManager (null) - Chose Trinity as your combat routine
2016-03-06 04:03:23,561 [1] DEBUG TreeHooks (null) - Replaced hook [RoutineCombat] f8c518ed-ed5c-4216-be08-e2c62daddf27
2016-03-06 04:03:23,561 [1] DEBUG RoutineManager (null) - Routines were reloaded. New routine list:
2016-03-06 04:03:23,561 [1] DEBUG RoutineManager (null) - Trinity v0.0.0.0
2016-03-06 04:03:23,561 [1] DEBUG RoutineManager (null) - Generic v1.1.2977.456
2016-03-06 04:03:23,561 [1] DEBUG BotMain (null) - Forcing profile reload.
2016-03-06 04:03:23,671 [1] INFO ProfileManager (null) - Loaded profile YAR Kickstart
2016-03-06 04:03:23,671 [1] DEBUG BotMain (null) - Starting bot: Order Bot
2016-03-06 04:03:23,676 [1] INFO RoutineManager (null) - Chose Trinity as your combat routine
2016-03-06 04:03:23,676 [1] DEBUG TreeHooks (null) - Replaced hook [RoutineCombat] 2abc19c3-22db-4670-b437-040fab1435bb
2016-03-06 04:03:23,681 [1] DEBUG TreeHooks (null) - Added new hook [OutOfGame] 39fa96a1-4ea5-4fa9-ad51-d687a1b50b26
2016-03-06 04:03:23,681 [1] DEBUG TreeHooks (null) - Added new hook [Death] 45f4633b-f16d-48f1-9583-a57f285507a2
2016-03-06 04:03:23,681 [1] DEBUG TreeHooks (null) - Added new hook [RoutineBuffs] 65af858a-dcb5-4ace-b95b-4f02cc4d4e9a
2016-03-06 04:03:23,681 [1] DEBUG TreeHooks (null) - Added new hook [RoutineCombat] 22470867-de74-456c-94ac-ab6ec1269925
2016-03-06 04:03:23,681 [1] DEBUG TreeHooks (null) - Added new hook [Combat] d8b35b3a-533c-4cb6-a7b0-6df3fc65b7c3
2016-03-06 04:03:23,686 [1] DEBUG TreeHooks (null) - Added new hook [IdentifyItems] b08237ce-8b40-428f-8273-34ce8bd3e4c6
2016-03-06 04:03:23,686 [1] DEBUG TreeHooks (null) - Added new hook [StashItems] f9b9ff21-2c55-42be-83e6-ce836b3ab462
2016-03-06 04:03:23,686 [1] DEBUG TreeHooks (null) - Added new hook [SellAndRepair] 64b5d1a7-fb38-4802-8bda-92296a4ce2a2
2016-03-06 04:03:23,686 [1] DEBUG TreeHooks (null) - Added new hook [SalvageItems] e769914c-13cd-49d4-bb32-da70fa0e6b65
2016-03-06 04:03:23,691 [1] DEBUG TreeHooks (null) - Added new hook [VendorRun] 6caf0646-e72c-4632-9f70-20bbcbb6a37c
2016-03-06 04:03:23,691 [1] DEBUG TreeHooks (null) - Added new hook [Loot] 1c32eb78-663a-491f-ab59-89e7d7947bfa
2016-03-06 04:03:23,696 [1] DEBUG TreeHooks (null) - Replaced hook [BotBehavior] c716e345-1f8a-4a4d-9d23-22913d33b87a
2016-03-06 04:03:23,696 [1] DEBUG BotMain (null) - Spooling up bot thread.
2016-03-06 04:03:23,696 [1] DEBUG BotMain (null) - Bot thread started.
2016-03-06 04:03:23,721 [Main Bot Thread] INFO BrainBehavior (null) - Logging into game
2016-03-06 04:03:28,381 [Main Bot Thread] DEBUG AssemblyLoader`1 (null) - Reloading AssemblyLoader<Zeta.Common.Plugins.IPlugin> - Initializing plugins
2016-03-06 04:03:32,293 [Main Bot Thread] INFO Logger (null) - [Adventurer] (1.3.4.18) initialized.
2016-03-06 04:03:32,293 [Main Bot Thread] INFO RequestClicker (null) - [RequestClicker 1.0.0] Initialized
2016-03-06 04:03:32,298 [Main Bot Thread] INFO Logger (null) - [Trinity 2.14.42] Initialized v2.14.42
2016-03-06 04:03:32,298 [1] INFO Logger (null) - [Adventurer] (1.3.4.18) initialized.
2016-03-06 04:03:32,298 [1] INFO Logger (null) - [Adventurer] (1.3.4.18) enabled.
2016-03-06 04:03:32,303 [1] INFO Logger (null) - [QuestTools][Plugin] v3.5.13 Enabled
2016-03-06 04:03:32,553 [1] DEBUG Logger (null) - [QuestTools][BotBehaviorQueue] Inserting BotBehaviorQueue Hook
2016-03-06 04:03:32,553 [1] DEBUG TreeHooks (null) - Inserted new hook [BotBehavior @0] 4fe10186-399a-4db3-9963-5ddec8cd872c
2016-03-06 04:03:32,563 [1] INFO RequestClicker (null) - [RequestClicker 1.0.0] Initialized
2016-03-06 04:03:32,563 [1] INFO RequestClicker (null) - [RequestClicker 1.0.0] Enabled
2016-03-06 04:03:32,563 [1] INFO Logger (null) - [Trinity 2.14.42] OnEnable start
2016-03-06 04:03:32,568 [1] INFO Logger (null) - [Trinity 2.14.42] Loading BattleTag Settings
2016-03-06 04:03:32,828 [1] INFO Logger (null) - [Trinity 2.14.42] Configuration file loaded
2016-03-06 04:03:32,828 [1] INFO Logger (null) - [Trinity 2.14.42] Configuration loaded successfully.
2016-03-06 04:03:32,833 [1] DEBUG Logger (null) - [Trinity 2.14.42] Loading Paragon Priority
2016-03-06 04:03:32,833 [1] INFO Logger (null) - [Trinity 2.14.42] Loading Avoidance Data
2016-03-06 04:03:34,993 [15] INFO Logger (null) - [Adventurer] Plugin is up-to-date.
2016-03-06 04:03:35,108 [20] INFO Logger (null) - [Adventurer] Plugin is up-to-date.
Until here FREEZING, then I killed Demonbuddy manully through YAR.

Then the new DB process restart:
2016-03-06 04:05:24,437 [1] INFO MainWindow (null) - Logging in...
2016-03-06 04:05:24,552 [4] DEBUG MainWindow (null) - Logging in to China (123.57.29.72)
2016-03-06 04:05:24,572 [4] INFO MainWindow (null) - T: 5247614357672909379 H: 1020951196
2016-03-06 04:05:25,042 [1] INFO MainWindow (null) - Attached to Diablo III with pid: 6668
2016-03-06 04:05:25,042 [1] DEBUG MainWindow (null) - Executable Path: E:\KCBLZ\D3DB\Demonbuddy 1.1.2977.456XMDJ78\Demonbuddy.exe
2016-03-06 04:05:25,042 [1] DEBUG MainWindow (null) - Platform: Microsoft Windows NT 6.1.7601 Service Pack 1
2016-03-06 04:05:25,047 [1] DEBUG AssemblyLoader`1 (null) - Reloading AssemblyLoader<Zeta.Bot.IBot> - BotManager.Reload
2016-03-06 04:05:29,467 [1] DEBUG BotManager (null) - Bots were reloaded. New bot list:
2016-03-06 04:05:29,467 [1] DEBUG BotManager (null) - YARKickstart v0.0.0.0
2016-03-06 04:05:29,467 [1] DEBUG BotManager (null) - Combat Bot v1.1.2977.456
2016-03-06 04:05:29,467 [1] DEBUG BotManager (null) - Script Runner v1.1.2977.456
2016-03-06 04:05:29,467 [1] DEBUG BotManager (null) - Order Bot v1.1.2977.456
2016-03-06 04:05:29,917 [1] DEBUG AssemblyLoader`1 (null) - Reloading AssemblyLoader<Zeta.Common.Plugins.IPlugin> - Initializing plugins.
2016-03-06 04:05:33,983 [1] INFO Logger (null) - [Adventurer] (1.3.4.18) initialized.
2016-03-06 04:05:33,988 [1] INFO RequestClicker (null) - [RequestClicker 1.0.0] Initialized
2016-03-06 04:05:33,988 [1] INFO Logger (null) - [Trinity 2.14.42] Initialized v2.14.42
2016-03-06 04:05:33,993 [1] INFO YARPLUGIN (null) - [YetAnotherRelogger] YAR Plugin Enabled with PID: 8572
2016-03-06 04:05:33,993 [1] INFO YARPLUGIN (null) - [YetAnotherRelogger] Starting YAR Thread
2016-03-06 04:05:33,993 [YARWorker] INFO YARPLUGIN (null) - [YetAnotherRelogger] YAR Worker Thread Started
2016-03-06 04:05:34,098 [1] INFO YARPLUGIN (null) - [YetAnotherRelogger] Requesting Profile (Current=Null)
2016-03-06 04:05:34,108 [1] INFO YARPLUGIN (null) - [YetAnotherRelogger] Loading profile: E:\KCBLZ\D3DB\Demonbuddy 1.1.2977.456XMDJ78\Profiles\Adventurer\NephalemRift.xml
2016-03-06 04:05:34,243 [1] INFO BotMain (null) - Current bot set to Order Bot
2016-03-06 04:05:34,243 [1] INFO ProfileManager (null) - Loaded profile Adventurer - Nephalem Rift
2016-03-06 04:05:34,493 [1] INFO Logger (null) - [Adventurer] (1.3.4.18) enabled.
2016-03-06 04:05:34,498 [1] INFO Logger (null) - [QuestTools][Plugin] v3.5.13 Enabled
2016-03-06 04:05:34,748 [1] DEBUG Logger (null) - [QuestTools][BotBehaviorQueue] Inserting BotBehaviorQueue Hook
2016-03-06 04:05:34,748 [1] DEBUG TreeHooks (null) - Inserted new hook [BotBehavior @0] 557b912f-48c8-46c1-86cf-7310e7ae93c6
2016-03-06 04:05:34,758 [1] INFO RequestClicker (null) - [RequestClicker 1.0.0] Enabled
2016-03-06 04:05:34,758 [1] INFO Logger (null) - [Trinity 2.14.42] OnEnable start
2016-03-06 04:05:34,763 [1] INFO Logger (null) - [Trinity 2.14.42] Loading BattleTag Settings
2016-03-06 04:05:35,028 [1] INFO Logger (null) - [Trinity 2.14.42] Configuration file loaded
This NEW process of DB can run properly, no longer freezing again.

YAR Logs:
N [2016/3/6 12:02:40] ####[ Detecting Screens ]####
N [2016/3/6 12:02:40] - Primary Screen 0: X:0,Y:0,W:1600,H:900 Enabled:True
N [2016/3/6 12:02:40] Name: \\.\DISPLAY1
N [2016/3/6 12:02:40] Device: AMD Radeon R7 200 Series
N [2016/3/6 12:02:40] WorkingArea: X:0,Y:0,W:1600,H:872
N [2016/3/6 12:02:40] ######################
V [2016/3/6 12:02:40] Relogger Thread Starting!
N [2016/3/6 12:02:40] rrrix's Yet Another Relogger fork Version 1.1.0.0
N [2016/3/6 12:02:48] <xmdj77> We are scheduled to start
N [2016/3/6 12:02:48] <xmdj77> Language set: Chinese : zhCN
N [2016/3/6 12:02:48] <xmdj77> Region set: Asia : kr.actual.battle.net
N [2016/3/6 12:03:02] <xmdj77> Diablo:6668: Found D3 Main Window (2163560)
N [2016/3/6 12:03:05] <xmdj77> Diablo:6668: Waiting for process to become ready
N [2016/3/6 12:03:06] <xmdj77> Diablo:6668: Process is ready
N [2016/3/6 12:03:06] <xmdj77> Demonbuddy start delay, waiting 10 seconds
N [2016/3/6 12:03:16] <xmdj77> Installing latest plugin: E:\KCBLZ\D3DB\Demonbuddy 1.1.2977.456XMDJ78\Plugins\YAR\Plugin.cs
N [2016/3/6 12:03:16] <xmdj77> Installing latest bot: E:\KCBLZ\D3DB\Demonbuddy 1.1.2977.456XMDJ78\Bots\YARBot\YARBot.cs
N [2016/3/6 12:03:16] <xmdj77> Demonbuddy:8400: Waiting for process to become ready
N [2016/3/6 12:03:18] <xmdj77> Found Demonbuddy: MainWindow (1312322)
N [2016/3/6 12:03:18] <xmdj77> Demonbuddy:8400: Process is ready
N [2016/3/6 12:03:18] <xmdj77> Demonbuddy:8400: Waiting for demonbuddy to log into Diablo
N [2016/3/6 12:03:52] <xmdj77> Killing Demonbuddy
N [2016/3/6 12:03:52] <xmdj77> Demonbuddy:8400: Process is not responding, killing!
N [2016/3/6 12:03:53] <xmdj77> Demonbuddy:8400: Failed to initialize 1/15
N [2016/3/6 12:03:53] <xmdj77> Demonbuddy:8400: Found matching log: E:\KCBLZ\D3DB\Demonbuddy 1.1.2977.456XMDJ78\Logs\8400 2016-03-06 12.03.txt
N [2016/3/6 12:03:53] <xmdj77> Demonbuddy:8400: Failed to find login time
N [2016/3/6 12:03:53] <xmdj77> Installing latest plugin: E:\KCBLZ\D3DB\Demonbuddy 1.1.2977.456XMDJ78\Plugins\YAR\Plugin.cs
N [2016/3/6 12:03:53] <xmdj77> Installing latest bot: E:\KCBLZ\D3DB\Demonbuddy 1.1.2977.456XMDJ78\Bots\YARBot\YARBot.cs
N [2016/3/6 12:03:53] <xmdj77> Demonbuddy:8572: Waiting for process to become ready
N [2016/3/6 12:03:54] <xmdj77> Found Demonbuddy: MainWindow (2033036)
N [2016/3/6 12:03:54] <xmdj77> Demonbuddy:8572: Process is ready
N [2016/3/6 12:03:54] <xmdj77> Demonbuddy:8572: Waiting for demonbuddy to log into Diablo
Until here FREEZING, then I killed Demonbuddy manully through YAR.
N [2016/3/6 12:05:34] <xmdj77> Sending DifficultyLevel: Disabled
N [2016/3/6 12:05:34] <xmdj77> Current profile: "NephalemRift.xml" Runs:0 Time:0 mintues (E:\KCBLZ\D3DB\Demonbuddy 1.1.2977.456XMDJ78\Profiles\Adventurer\NephalemRift.xml)
N [2016/3/6 12:05:34] <xmdj77> Sending Current Profile to Load E:\KCBLZ\D3DB\Demonbuddy 1.1.2977.456XMDJ78\Profiles\Adventurer\NephalemRift.xml
N [2016/3/6 12:05:34] <xmdj77> Demonbuddy:8572: Initialized! We are ready to go
N [2016/3/6 12:05:35] <xmdj77> Check Force Enable Plugins? True
V [2016/3/6 12:05:57] <xmdj77> [GoldPerHour] New start coinage: 558,603,453,320
N [2016/3/6 12:10:18] <xmdj77> Runs completed 1
N [2016/3/6 12:10:18] <xmdj77> Sending DifficultyLevel: Torment10
N [2016/3/6 12:11:20] <xmdj77> Runs completed 2
N [2016/3/6 12:11:20] <xmdj77> Sending DifficultyLevel: Torment10
N [2016/3/6 12:13:15] <xmdj77> Runs completed 3
 
Last edited:
thanks jub
but my R-yar still doesnt work with renaming DB
how to fix this?
after 1 crash it cant find DB after DB renamed itslef
 
thanks jub
but my R-yar still doesnt work with renaming DB
how to fix this?
after 1 crash it cant find DB after DB renamed itslef
let YAR locate DB with the short cut named “Demonbuddy.exe” , NOT the renamed exe file
 
So whats the cause of:
Attached to Diablo III with PID 2300
Current bot set to Order Bot
Loaded profile YAR kickstart
Choose Trinity as your combat routine
Loaded profile Yar Kickstart
Choose Trinity as your combat routine
Logging into game

and DB basically being frozen at this point.
 
I'm using simplefollow cause itr works better than autofollow at this moment, but YAR it's not working ok, so I run 4 bots without YAR. My experience:

- Running 4 bots with YAR, only simplefollow, autofollow is not installed.
- For some strange reason, 4th account is being disconnected after a few minutes. Sometimes it works for some minutes, sometimes it works for less.
- One strange thing is that though 4th account is configured in YAR with the simplefollo reloger profile, if I start demonbuddy manually, it says YAR profile loaded... I don't know if this can be helpful...
 
thx
worked this time but new problem is DB has no plugin working at all when loged in
if i clicked top it had just frozen there
how to fix this?
thx
 
Hi Jubisman, Thanks for the hard work and keep this valuable program alive.

what is symlink? do you mean short cut link? I used the short cut link and DB freezes for good.
DB showed following:

Attached to Diablo III with PID 2300
Current bot set to Order Bot
Loaded profile YAR kickstart
Choose Trinity as your combat routine
Loaded profile Yar Kickstart
Choose Trinity as your combat routine
Logging into game

Then, frozen....

Only the first DB freezes. If we stop all and press " start" button to restart all in relogger, it works fine.
 
Back
Top