[Plugin] YAR - Yet Another Relogger

[DeadManRun]

Hi here are my Log:

YAR:

V [23.02.2016 00:54:33] Relogger Thread Starting!
N [23.02.2016 00:54:33] rrrix's Yet Another Relogger fork Version 1.1.0.0
N [23.02.2016 00:54:36] <CRU - LON> We are scheduled to start
N [23.02.2016 00:54:36] <CRU - LON> Language set: German : deDE
N [23.02.2016 00:54:36] <CRU - LON> Region set: Europe : eu.actual.battle.net
N [23.02.2016 00:54:48] <CRU - LON> Diablo:6344: Found D3 Main Window (1704668)
N [23.02.2016 00:54:51] <CRU - LON> Diablo:6344: Waiting for process to become ready
N [23.02.2016 00:54:52] <CRU - LON> Diablo:6344: Process is ready
N [23.02.2016 00:54:52] <CRU - LON> Demonbuddy start delay, waiting 10 seconds
N [23.02.2016 00:55:02] <CRU - LON> Installing latest plugin: C:\Users\Hugo\Desktop\DeamonBuddy\1.DeamonBuddy\DB-455-LON\Plugins\YAR\Plugin.cs
N [23.02.2016 00:55:02] <CRU - LON> Demonbuddy:6088: Waiting for process to become ready
N [23.02.2016 00:55:03] <CRU - LON> Found Demonbuddy: MainWindow (853640)
N [23.02.2016 00:55:03] <CRU - LON> Demonbuddy:6088: Process is ready
N [23.02.2016 00:55:03] <CRU - LON> Demonbuddy:6088: Waiting for demonbuddy to log into Diablo
N [23.02.2016 00:55:12] <CRU - LON> Stopping
N [23.02.2016 00:55:12] <CRU - LON> Demonbuddy:6088: Closing window
N [23.02.2016 00:55:12] <CRU - LON> Diablo:6344: Kill process
V [23.02.2016 00:55:12] Relogger Thread Starting!
N [23.02.2016 00:55:14] Closed!

DB:

2016-02-22 23:55:03,393 [1] INFO MainWindow (null) - Demonbuddy v1.1.2952.455 started
2016-02-22 23:55:03,446 [1] INFO MainWindow (null) - Logging in...
2016-02-22 23:55:03,480 [4] DEBUG MainWindow (null) - Logging in to BestLatency (37.187.151.148)
2016-02-22 23:55:03,678 [4] INFO MainWindow (null) - T: 5247603839462205317 H: 302607410
2016-02-22 23:55:04,164 [1] INFO MainWindow (null) - Attached to Diablo III with pid: 6344
2016-02-22 23:55:04,165 [1] DEBUG MainWindow (null) - Executable Path: C:\Users\Hugo\Desktop\DeamonBuddy\1.DeamonBuddy\DB-455-LON\Demonbuddy.exe
2016-02-22 23:55:04,165 [1] DEBUG MainWindow (null) - Platform: Microsoft Windows NT 6.2.9200.0
2016-02-22 23:55:04,171 [1] DEBUG AssemblyLoader`1 (null) - Reloading AssemblyLoader<Zeta.Bot.IBot> - BotManager.Reload
2016-02-22 23:55:04,220 [1] DEBUG BotManager (null) - Bots were reloaded. New bot list:
2016-02-22 23:55:04,221 [1] DEBUG BotManager (null) - Order Bot v1.1.2952.455
2016-02-22 23:55:04,220 [1] DEBUG BotManager (null) - Combat Bot v1.1.2952.455
2016-02-22 23:55:04,221 [1] DEBUG BotManager (null) - Script Runner v1.1.2952.455
2016-02-22 23:55:04,779 [1] INFO BotMain (null) - Current bot set to Order Bot
2016-02-22 23:55:04,783 [1] INFO ProfileManager (null) - Loaded profile YAR Kickstart
2016-02-22 23:55:04,827 [1] DEBUG AssemblyLoader`1 (null) - Reloading AssemblyLoader<Zeta.Bot.ICombat> - RoutineManager.Reload
2016-02-22 23:55:05,084 [1] INFO RoutineManager (null) - Chose Trinity as your combat routine
2016-02-22 23:55:05,086 [1] DEBUG TreeHooks (null) - Replaced hook [RoutineCombat] e1e1d2e1-7362-48e8-956a-d47101f99148
2016-02-22 23:55:05,086 [1] DEBUG RoutineManager (null) - Trinity v0.0.0.0
2016-02-22 23:55:05,086 [1] DEBUG RoutineManager (null) - Routines were reloaded. New routine list:
2016-02-22 23:55:05,086 [1] DEBUG RoutineManager (null) - Generic v1.1.2952.455
2016-02-22 23:55:05,087 [1] DEBUG BotMain (null) - Forcing profile reload.
2016-02-22 23:55:05,190 [1] INFO ProfileManager (null) - Loaded profile YAR Kickstart
2016-02-22 23:55:05,192 [1] INFO RoutineManager (null) - Chose Trinity as your combat routine
2016-02-22 23:55:05,191 [1] DEBUG BotMain (null) - Starting bot: Order Bot
2016-02-22 23:55:05,192 [1] DEBUG TreeHooks (null) - Replaced hook [RoutineCombat] ad2f0f97-14ec-4ec3-a7e7-a733c693fd9e
2016-02-22 23:55:05,198 [1] DEBUG TreeHooks (null) - Added new hook [RoutineBuffs] cebdade8-bb34-4628-9c6b-4ac4d7e1467d
2016-02-22 23:55:05,197 [1] DEBUG TreeHooks (null) - Added new hook [OutOfGame] 14d22438-57bd-4be5-9059-43018497b0de
2016-02-22 23:55:05,197 [1] DEBUG TreeHooks (null) - Added new hook [Death] a5c0df31-82e5-4881-b54c-6473742ee8de
2016-02-22 23:55:05,198 [1] DEBUG TreeHooks (null) - Added new hook [RoutineCombat] 8cb3a6c2-7156-4ed4-becd-e4665c172ccc
2016-02-22 23:55:05,199 [1] DEBUG TreeHooks (null) - Added new hook [Combat] 7d193d48-b100-4d98-a9a3-f661d52903ad
2016-02-22 23:55:05,202 [1] DEBUG TreeHooks (null) - Added new hook [IdentifyItems] 0b859f49-4b81-4a60-8aeb-85b2713f9f57
2016-02-22 23:55:05,203 [1] DEBUG TreeHooks (null) - Added new hook [StashItems] 09c0cf1f-c0c7-4e89-9e11-d51b8b4a6904
2016-02-22 23:55:05,203 [1] DEBUG TreeHooks (null) - Added new hook [SellAndRepair] 264f2e75-449f-44a2-a5ce-12c29f284345
2016-02-22 23:55:05,203 [1] DEBUG TreeHooks (null) - Added new hook [SalvageItems] 354547c8-e805-4c1b-ab00-f76ff27f53af
2016-02-22 23:55:05,205 [1] DEBUG TreeHooks (null) - Added new hook [VendorRun] 07d9ed96-cb8d-4e99-aff7-7d2918041989
2016-02-22 23:55:05,210 [1] DEBUG TreeHooks (null) - Added new hook [Loot] aae89a39-6ecb-4d24-a524-e893238984d8
2016-02-22 23:55:05,210 [1] DEBUG TreeHooks (null) - Replaced hook [BotBehavior] f32a760e-2d77-40e5-b72c-4b8e5d4560da
2016-02-22 23:55:05,211 [1] DEBUG BotMain (null) - Spooling up bot thread.
2016-02-22 23:55:05,212 [1] DEBUG BotMain (null) - Bot thread started.
2016-02-22 23:55:05,243 [Main Bot Thread] INFO BrainBehavior (null) - Logging into game
2016-02-22 23:55:12,340 [1] INFO BotMain (null) - Stopping the bot.
2016-02-22 23:55:12,340 [1] INFO BotMain (null) - Session lasted for: 00:00:07.1300000
2016-02-22 23:55:12,395 [16] INFO ZetaDia (null) - Diablo III Exited, Demonbuddy terminating in 20 seconds.
2016-02-22 23:55:17,336 [1] WARN BotMain (null) - Bot thread did not end within 5 seconds
2016-02-22 23:55:17,337 [Main Bot Thread] DEBUG BotMain (null) - Bot Thread Aborted Der Thread wurde abgebrochen.
2016-02-22 23:55:17,351 [1] DEBUG BotMain (null) - CurrentBot.Stop()
2016-02-22 23:55:17,619 [1] DEBUG BotMain (null) - Navigator.Clear()
2016-02-22 23:55:17,626 [1] DEBUG BotMain (null) - TreeHooks.Instance.ClearAll()
2016-02-22 23:55:17,626 [1] DEBUG BotMain (null) - OnStop Event Invoking
2016-02-22 23:55:17,627 [1] DEBUG ProfileOrderManager (null) - [OnBotStop] Resetting caches
2016-02-22 23:55:17,626 [1] INFO RoutineManager (null) - Chose Trinity as your combat routine
2016-02-22 23:55:17,626 [1] DEBUG TreeHooks (null) - Replaced hook [RoutineCombat] 510a7cd5-1680-44b6-a10f-30b5130e1327
2016-02-22 23:55:17,626 [1] DEBUG BotMain (null) - OnStop event
2016-02-22 23:55:17,630 [1] DEBUG MainWindow (null) - Forcing all open windows to close.

 

[jubisman]

And that still happens with the version I attached here?

 

[Cchester]

Hi Could you add a option to connect to China server please or just let me know how to set it up if not too complicated?

 

[jubisman]

What china server is that? D3's or DB's?

 

[junggi]

I have an error with it.

Here are my logs

Problem is when DB close it self, YAR try to re launch DB then it happens.

No start a bot, did not load profile, stuck at YAR kickstart.xml


Yar

N [2/23/2016 9:45:40 PM] <rift> Sending DifficultyLevel: Torment10
N [2/23/2016 9:45:55 PM] <rift> Demonbuddy: Process is not running
N [2/23/2016 9:45:55 PM] <rift> Demonbuddy:5396: Found matching log: C:\Users\GENESIS\Desktop\DemonbuddyBETA 1.1.2914.596\Logs\5396 2016-02-23 20.29.txt
N [2/23/2016 9:46:05 PM] <rift> Demonbuddy:5396: Failed to find login time
N [2/23/2016 9:46:05 PM] <rift> Installing latest plugin: C:\Users\GENESIS\Desktop\DemonbuddyBETA 1.1.2914.596\Plugins\YAR\Plugin.cs
N [2/23/2016 9:46:05 PM] <rift> Demonbuddy:224: Waiting for process to become ready
N [2/23/2016 9:46:07 PM] <rift> Found Demonbuddy - BETA: MainWindow (985166)
N [2/23/2016 9:46:07 PM] <rift> Demonbuddy:224: Process is ready
N [2/23/2016 9:46:07 PM] <rift> Demonbuddy:224: Waiting for demonbuddy to log into Diablo
N [2/23/2016 9:46:20 PM] <rift> Sending DifficultyLevel: Torment10
N [2/23/2016 9:46:20 PM] <rift> Sending Current Profile to Load C:\Users\GENESIS\Desktop\DemonbuddyBETA 1.1.2914.596\Profiles\Adventurer\GreaterRift.xml
N [2/23/2016 9:46:20 PM] <rift> Demonbuddy:224: Initialized! We are ready to go
N [2/23/2016 9:46:21 PM] <rift> Check Force Enable Plugins? False

DB

DemonbuddyBETA v1.1.2972.607 started
This is a BETA build of Demonbuddy. This is not meant for general usage. Please report any issues you may have in the beta thread on our forums.
This build may have bugs. Use at your own risk!
Logging in...
Logging in to SoutheastAsia (122.248.233.213)
T: 5247604914100920329 H: 1055382387
Attached to Diablo III with pid: 4244
Executable Path: C:\Users\GENESIS\Desktop\DemonbuddyBETA 1.1.2914.596\Demonbuddy.exe
Platform: Microsoft Windows NT 6.1.7601 Service Pack 1
Reloading AssemblyLoader<Zeta.Bot.IBot> - BotManager.Reload
Bots were reloaded. New bot list:
Combat Bot v1.1.2972.607
Script Runner v1.1.2972.607
Order Bot v1.1.2972.607
Reloading AssemblyLoader<Zeta.Common.Plugins.IPlugin> - Initializing plugins
[Adventurer] (1.3.4.18) initialized.
[Trinity 2.14.45] Initialized v2.14.45
[YetAnotherRelogger] YAR Plugin Initialized with PID: 224
[YetAnotherRelogger] YAR Plugin Enabled with PID: 224
[YetAnotherRelogger] Starting YAR Thread
[YetAnotherRelogger] YAR Worker Thread Started
[YetAnotherRelogger] Recieved DifficultyLevel: Torment10
[YetAnotherRelogger] Requesting Profile (Current=Null)
Current bot set to Order Bot
Loaded profile Adventurer - Greater Rift
[Adventurer] (1.3.4.18) enabled.
[QuestTools][Plugin] v3.5.13 Enabled
[QuestTools][BotBehaviorQueue] Inserting BotBehaviorQueue Hook
Inserted new hook [BotBehavior @0] 6b1bcd35-2885-47a8-91e4-ae7e848bc600
[Trinity 2.14.45] OnEnable start
[Trinity 2.14.45] Loading BattleTag Settings
[Adventurer] Plugin is up-to-date.
[Trinity 2.14.45] Configuration file loaded
[Trinity 2.14.45] Configuration loaded successfully.
[Trinity 2.14.45] Loading Paragon Priority
[Trinity 2.14.45] Loading Avoidance Data
[Trinity 2.14.45] Using Trinity Unstucker
[Trinity 2.14.45] Bot TPS set to 15
[Trinity 2.14.45] ENABLED: Trinity v2.14.45 now in action!
Setting up Trinity Logging
There are 5 plugins
[YetAnotherRelogger] Plugins Compiled matched
Error while invoking eventSystem.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at QuestTools.Helpers.ProfileUtils.ProcessProfile()
at QuestTools.Helpers.BotEvents.ProfileManager_OnProfileLoaded(Object sender, EventArgs e)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at Zeta.Bot.ProfileManager.​*‎‪‫‪​*​‎‬​‪**​‏‫***‏‫***(Delegate , Object[] )

Loaded profile YAR Kickstart
Reloading AssemblyLoader<Zeta.Bot.ICombat> - RoutineManager.Reload
Chose Trinity as your combat routine
Replaced hook [RoutineCombat] 8c27d6ac-e4d7-4b79-a712-67c7f91782dd
Routines were reloaded. New routine list:
Trinity v0.0.0.0
Generic v1.1.2972.607
Forcing profile reload.
Error while invoking eventSystem.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at QuestTools.Helpers.ProfileUtils.ProcessProfile()
at QuestTools.Helpers.BotEvents.ProfileManager_OnProfileLoaded(Object sender, EventArgs e)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at Zeta.Bot.ProfileManager.​*‎‪‫‪​*​‎‬​‪**​‏‫***‏‫***(Delegate , Object[] )

Loaded profile YAR Kickstart
Starting bot: Order Bot
Chose Trinity as your combat routine
Replaced hook [RoutineCombat] ba0a6019-d014-471b-bdbb-a7112b0b335b
Inserted new hook [BotBehavior @0] 2a8b857d-137d-4ff3-8905-0d04fbbbb2dd
Added new hook [OutOfGame] 5feae2db-b5e0-40a8-b347-484ab4b51a36
Added new hook [Death] 32e3c7ff-7bdb-4c82-9baf-f62f030df725
Added new hook [RoutineBuffs] 15d56a72-13fb-47e8-94a5-258baa133d11
Added new hook [RoutineCombat] 9b68b745-9fc4-4d75-a8d7-30b4d7ce1efa
Added new hook [Combat] df2e4e8f-f35f-4b0b-9acd-bc0e44591117
Added new hook [IdentifyItems] 92351f84-a790-4fc3-9428-87bb07a5216e
Added new hook [StashItems] de178583-4605-41b0-b220-4aac9bccc8af
Added new hook [SellAndRepair] d37af47e-1744-4e42-b2d6-f4340262cd0e
Added new hook [SalvageItems] f44d63e1-ddf8-40aa-9298-134db6898d71
Added new hook [VendorRun] 490b5d05-0c6f-44bd-b55d-a335e3915763
Added new hook [Loot] 401bd8a3-87d4-4b70-9d68-b0261e04f5f9
Replaced hook [BotBehavior] 14e8a6e0-645e-4971-994e-6917c6caaec5
[YetAnotherRelogger] Inserting YAR Hook
Inserted new hook [OutOfgame @0] ec494807-ae87-4208-8141-89ca39b19232
[QuestTools][BotEvents] Bot is Starting
[QuestTools][BotBehaviorQueue] Inserting BotBehaviorQueue Hook
Inserted new hook [BotBehavior @0] ce016247-dfdb-4f23-9fb4-f9029b5027b0
[Trinity 2.14.45] Bot Starting
[Trinity 2.14.45] Replacing Combat Hook
Replaced hook [Combat] 7dc26c77-1833-4dad-8103-e2c338bf92c5
[Trinity 2.14.45] Replacing VendorRun Hook
Replaced hook [VendorRun] 4654f4a8-2650-46ab-8446-5ec9ff38f983
[Trinity 2.14.45] Replacing Loot Hook
Replaced hook [Loot] db97ab53-9b35-44db-a3a3-9c17b4217385
[Trinity 2.14.45] Replacing Death Hook
Replaced hook [Death] 9d7733f1-1f69-4814-b55f-7a7eec02dbbc
[Trinity 2.14.45] Inserting GoldInactivity into TreeStart
Inserted new hook [TreeStart @0] a1a15fac-3c68-43ed-9c50-d884dfcddba5
[Trinity 2.14.45] Inserting XPInactivity into TreeStart
Inserted new hook [TreeStart @0] 16998e97-fde2-4b32-aab1-c34da5cd99df
[Trinity 2.14.45] Bot Starting, Resetting Gold Inactivity Timer
Spooling up bot thread.
Bot thread started.

 

[jubisman]

The exception seems to be related to QuestTools. Have you tried uninstalling it? It's not really needed anymore unless you're running questing profiles or uberbot.

 

[skynetwork]

not working for me too (latest DB 609 Beta, latest YAR from first page). just starts the game, then opens DB, getting errors, then closes diablo and restarts and so on... quest tools deleted btw...

this only happens when YAR starts my DB, no errors with db alone...

DemonbuddyBETA v1.1.2977.609 started
This is a BETA build of Demonbuddy. This is not meant for general usage. Please report any issues you may have in the beta thread on our forums.
This build may have bugs. Use at your own risk!
Logging in...
T: 5247605589274146737 H: 2977220213
Attached to Diablo III with pid: 7712
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
[Adventurer] (1.3.4.18) initialized.
[Trinity 2.14.45] Initialized v2.14.45
[ UberBot ] Initialized v0.5.2
[YetAnotherRelogger] YAR Plugin Initialized with PID: 5480
[YetAnotherRelogger] YAR Plugin Enabled with PID: 5480
[YetAnotherRelogger] Starting YAR Thread
[YetAnotherRelogger] YAR Worker Thread Started
[YetAnotherRelogger] Unknown response! "Error: Unknown process"
[YetAnotherRelogger] Requesting Profile (Current=C:\Games\Diablo III\DemonbuddyBETA 1.1.2977.609\Profiles\Kickstart.xml)
[YetAnotherRelogger] Unknown response! "Error: Unknown process"
[YetAnotherRelogger] Unknown response! "Error: Unknown process"
[Adventurer] (1.3.4.18) enabled.
[Trinity 2.14.45] OnEnable start
[Trinity 2.14.45] Loading BattleTag Settings
[Adventurer] Plugin is up-to-date.
[Trinity 2.14.45] Error while CopyTo Setting ItemListSettings : Exception has been thrown by the target of an invocation. Property: Grouping System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: The calling thread cannot access this object because a different thread owns it.
   at System.Windows.Threading.Dispatcher.VerifyAccess()
   at System.Windows.DependencyObject.GetValue(DependencyProperty dp)
   at System.Windows.Data.CollectionViewSource.EnsureView()
   at System.Windows.Data.CollectionViewSource.DeferHelper.Dispose()
   at Trinity.Settings.Loot.ItemListSettings.ChangeGrouping(GroupingType groupingType)
   at Trinity.Settings.Loot.ItemListSettings.set_Grouping(GroupingType value)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.Reflection.RuntimePropertyInfo.SetValue(Object obj, Object value, BindingFlags invokeAttr, Binder binder, Object[] index, CultureInfo culture)
   at System.Reflection.RuntimePropertyInfo.SetValue(Object obj, Object value, Object[] index)
   at Trinity.Config.TrinitySetting.CopyTo[T](ITrinitySetting`1 source, ITrinitySetting`1 destination)
[Trinity 2.14.45] Configuration file loaded
[Trinity 2.14.45] Configuration loaded successfully.
[Trinity 2.14.45] Loading Avoidance Data
[Trinity 2.14.45] Bot Starting
Setting up Trinity Logging
[Trinity 2.14.45] Replacing Combat Hook
[Trinity 2.14.45] Replacing VendorRun Hook
[Trinity 2.14.45] Replacing Loot Hook
[Trinity 2.14.45] Replacing Death Hook
[Trinity 2.14.45] Inserting GoldInactivity into TreeStart
[Trinity 2.14.45] Inserting XPInactivity into TreeStart
[Trinity 2.14.45] Bot Starting, Resetting Gold Inactivity Timer
[Trinity 2.14.45] ENABLED: Trinity v2.14.45 now in action!
[ UberBot ] v0.5.2 Enabled

 

[junggi]

still same issue after delete QT

DemonbuddyBETA v1.1.2977.609 started
This is a BETA build of Demonbuddy. This is not meant for general usage. Please report any issues you may have in the beta thread on our forums.
This build may have bugs. Use at your own risk!
Logging in...
T: 5247605657083431181 H: 2139938497
Attached to Diablo III with pid: 3244
[Adventurer] (1.3.4.18) initialized.
[Trinity 2.14.45] Initialized v2.14.45
[YetAnotherRelogger] YAR Plugin Initialized with PID: 656
[YetAnotherRelogger] YAR Plugin Enabled with PID: 656
[YetAnotherRelogger] Starting YAR Thread
[YetAnotherRelogger] YAR Worker Thread Started
[YetAnotherRelogger] Requesting Profile (Current=Null)
Current bot set to Order Bot
Loaded profile Adventurer - Greater Rift
[Adventurer] (1.3.4.18) enabled.
[Trinity 2.14.45] OnEnable start
[Trinity 2.14.45] Loading BattleTag Settings
[Adventurer] Plugin is up-to-date.
[Trinity 2.14.45] Configuration file loaded
[Trinity 2.14.45] Configuration loaded successfully.
[Trinity 2.14.45] Loading Avoidance Data
[Trinity 2.14.45] ENABLED: Trinity v2.14.45 now in action!
Setting up Trinity Logging
Loaded profile YAR Kickstart
Chose Trinity as your combat routine
[YetAnotherRelogger] Plugins Compiled matched
Loaded profile YAR Kickstart
Chose Trinity as your combat routine
[YetAnotherRelogger] Inserting YAR Hook
[Trinity 2.14.45] Bot Starting
[Trinity 2.14.45] Replacing Combat Hook
[Trinity 2.14.45] Replacing VendorRun Hook
[Trinity 2.14.45] Replacing Loot Hook
[Trinity 2.14.45] Replacing Death Hook
[Trinity 2.14.45] Inserting GoldInactivity into TreeStart
[Trinity 2.14.45] Inserting XPInactivity into TreeStart
[Trinity 2.14.45] Bot Starting, Resetting Gold Inactivity Timer

 

[net2knight]

I have an error with it.

Here are my logs

Problem is when DB close it self, YAR try to re launch DB then it happens.

No start a bot, did not load profile, stuck at YAR kickstart.xml

I have the same problem。When i colse db manualy,DB restart by Yar，it stuck Until you restart Yar.

 

[noobseals]

Issue report (windows 7):
Sometime when D3 crashed the DB may be not responding (pop up a "DB is not responding" windows) and can not be closed.
The YAR log keep spamming :
[2016/2/26 星期五 上午 12:11:38] <Acc3_Bar> Diablo:7364: Process is not running
N [2016/2/26 星期五 上午 12:11:38] <Acc3_Bar> Demonbuddy:7468: Waiting for Demonbuddy to self close
N [2016/2/26 星期五 上午 12:11:39] <Acc3_Bar> Diablo:7364: Process is not running
N [2016/2/26 星期五 上午 12:11:39] <Acc3_Bar> Demonbuddy:7468: Waiting for Demonbuddy to self close
N [2016/2/26 星期五 上午 12:11:40] <Acc3_Bar> Diablo:7364: Process is not running
N [2016/2/26 星期五 上午 12:11:40] <Acc3_Bar> Demonbuddy:7468: Waiting for Demonbuddy to self close


A simple click on "close the program" could close the DB and let YAR restart again. Hope there will be a fix quickly

PS. I have ticked both allow killing diablo and DB if unreponsive in YAR settings.

 

[austin909]

When the game or DB crashed, YAR would reset game or DB.
But load the Kickstart.xml, and then stuck.
I have download the latest version R-YAR from svn and uncheck "use kickstart".
Why?
Thanks!

 

[jubisman]

I can reproduce the problem you guys are describing after a crash. Sorry about that, I'll try to fix it today.

I already added China server support. Hopefully it works properly, so if there's any Chinese users out here keep posted for when the new version comes out.

Issue report (windows 7):
Sometime when D3 crashed the DB may be not responding (pop up a "DB is not responding" windows) and can not be closed.
The YAR log keep spamming :
[2016/2/26 星期五 上午 12:11:38] <Acc3_Bar> Diablo:7364: Process is not running
N [2016/2/26 星期五 上午 12:11:38] <Acc3_Bar> Demonbuddy:7468: Waiting for Demonbuddy to self close
N [2016/2/26 星期五 上午 12:11:39] <Acc3_Bar> Diablo:7364: Process is not running
N [2016/2/26 星期五 上午 12:11:39] <Acc3_Bar> Demonbuddy:7468: Waiting for Demonbuddy to self close
N [2016/2/26 星期五 上午 12:11:40] <Acc3_Bar> Diablo:7364: Process is not running
N [2016/2/26 星期五 上午 12:11:40] <Acc3_Bar> Demonbuddy:7468: Waiting for Demonbuddy to self close


A simple click on "close the program" could close the DB and let YAR restart again. Hope there will be a fix quickly

PS. I have ticked both allow killing diablo and DB if unreponsive in YAR settings.

I saw this too, but DB did close after a short while, so I wouldn't worry about the exceptions too much.

 

[lawlumad88]

@jubis:
1 out of my 3 char keep crashing with Yar:
[YetAnotherRelogger] Crash Exception detected
Exception during bot tick.Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Trinity.Combat.Abilities.BarbarianCombat.get_CanUseCallOfTheAncients()
at Trinity.Combat.Abilities.BarbarianCombat.GetPower()
at Trinity.Trinity.AbilitySelector(Boolean IsCurrentlyAvoiding, Boolean UseOOCBuff, Boolean UseDestructiblePower)
at Trinity.Trinity.TargetCheck(Object ret)
at Trinity.Helpers.BotManager.<MainCombatTask>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 Zeta.Bot.ActionRunCoroutine.\,or8mF0J0\]c_srBy3\]\,'U=Si\&.2c>Z6~J/Mj}R;MRXm7<\,6g8k".MoveNext()
--- End of inner exception stack trace ---
at Buddy.Coroutines.Coroutine.*​‎‫*​​‎*‎‪​**‎​*‫‎*​‬*(Boolean )
at Buddy.Coroutines.Coroutine.‫​*‫​‬‎***‎*‪‏​‪‫​‏*‎‫**‎**(Boolean )
at Buddy.Coroutines.Coroutine.Resume()
at Zeta.Bot.ActionRunCoroutine.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action.nikL"|$wf9\[FN}EV_?Hco?\\C!.MoveNext()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector.|-\& 3qFXwc?(d#sr|o\]=4-"z!.MoveNext()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Common.HookExecutor.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action.nikL"|$wf9\[FN}EV_?Hco?\\C!.MoveNext()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector.|-\& 3qFXwc?(d#sr|o\]=4-"z!.MoveNext()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Bot.BotMain.‫‫**​‏**‏**‪‏‫​‬‏​‎‪
‫** I can provide log if needed. This is older yar version since I still need simplefollower. Sorry for bothering with older version. How do i fix this problem? Only 1 of my follower experience this()

 

[Motnoose]

Has anyone been successfully able to get hotkeys working for re-sizing windows? Maybe I'm not doing something correctly or trying something that isnt possible. I have 3 screens up running 3mans in smaller windows, I'd like a hot key that will make whatever my active window is large and then a hotkey to make it small again. Is it even possible?

 

[noobseals]

I saw this too, but DB did close after a short while, so I wouldn't worry about the exceptions too much.

Yep it sometimes did close (I just saw it happened 5 mins ago). but sometimes did not. Every morning I can see not responding pops on my desktop, which have been stuck for hours according to YAR log.

 

[noobseals]

Hi lawlumad, I had the same spamming errors.
It seems to be an issue related to barbarian's Call of The Ancients. It works all good after I switched COTA to other skills.

 

[longbow16]

Hi developers, I came across a issue running DB with YAR, fyi, everything is fine with DB alone.

Here is the issue.
the D3 game window will disappear right after YAR open DB, every time.

I find out it is something wrong with the DB location path.
if I select DB link as the path, the issue occurs every time.

if I select the DB random name exe, it wouldn't close D3 game window.
But that wouldn't work due to DB create a new random name exe every time after running.
So if disconnected, YAR start over DB, then YAR can't recognize the new DB exe. end of Story.

Is there anyone else facing the same issue?

I am using win10, and I heard another win10 user facing the same problem.

Any solution?

 

[lawlumad88]

Hi lawlumad, I had the same spamming errors.
It seems to be an issue related to barbarian's Call of The Ancients. It works all good after I switched COTA to other skills.

i will try that. thank you

 

[Xenetron]

Hi developers, I came across a issue running DB with YAR, fyi, everything is fine with DB alone.

Here is the issue.
the D3 game window will disappear right after YAR open DB, every time.

I find out it is something wrong with the DB location path.
if I select DB link as the path, the issue occurs every time.

if I select the DB random name exe, it wouldn't close D3 game window.
But that wouldn't work due to DB create a new random name exe every time after running.
So if disconnected, YAR start over DB, then YAR can't recognize the new DB exe. end of Story.

Is there anyone else facing the same issue?

I am using win10, and I heard another win10 user facing the same problem.

Any solution?

Having the same problem as well. Rebooting computer seemed to have "fixed" it for a bit, but when relaunching again after a couple of times I get the same thing with D3 closing automatically. I haven't tried with the renamed .exe - if that fixes it, it's not really a fix since it isn't a solution. Hopefully jubis can look into it.

 

[jubisman]

Hey everyone. New version is out. It fixes DB not starting a game after crashing (thanks xzjv!) and adds the option to start the game in the Chinese server. If anyone else is having other issues and those persist with this new version, please let me know. I won't be working on YAR again today unfortunately, but I'll be checking this thread out from time to time.