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

R-YAR - rrrix's YAR fork

Just pushed 0.2.0.20 executable ("LatestBuild") to github - I've disabled the bot stop/start AntiIdle stuff since it was crashing the latest Demonbuddy BETA.
 
at .19 yar didnt change mp lvl prom yar setting selected, (maybe is problem in my settings, got some diry copy/paste) if any 1 can check this
 
for me clean cashe help for this problem, but i rarely got it one time for some days.
try with less number of bots, maybe this is a problem

.12 version is last which close clients without any problems with that

While I appreciate the help zakne11, rebuilding the cache files didn't help at all.
 
TIMER.webp

I used gold timer, but it didn't work......


View attachment 2013-10-09 01.00.txt

R-YAR-0.2.0.16(Because 0.2.0.17 will let DB crash...)
Demonbuddy 1.0.1446.317
TrinityPlugin-1.7.3.7CN
QuestTools-1.3.11
 
made clean new settings on relise versionof db, and yar .20 didnt set mp which are set in it

this character settings work, and change mp (i think is copied from older db versions)
Code:
<CharacterSettings>
 [SIZE=4][COLOR="#FF0000"] <MonsterPowerLevel>10</MonsterPowerLevel>[/COLOR][/SIZE]
  <KillRadius>80</KillRadius>
  <LootRadius>100</LootRadius>
  <EnabledPlugins>
    <Value>QuestTools</Value>
    <Value>Trinity</Value>
    <Value>YAR Comms</Value>
  </EnabledPlugins>
  <RuleSetPath>Rules\WeightBasedRules.xml</RuleSetPath>
  <ItemWeightSetPath>Rules\DefaultWeightSet.xml</ItemWeightSetPath>
  <ProtectedBagSlots />
  <ProtectedStashPagesFix>None</ProtectedStashPagesFix>
  <RepairWhenDurabilityBelow>30</RepairWhenDurabilityBelow>
  <OpenLootContainers>false</OpenLootContainers>
  <OpenChests>false</OpenChests>
  <DestroyEnvironment>false</DestroyEnvironment>
  <CombatLooting>true</CombatLooting>
  <UseBookOfCain>true</UseBookOfCain>
</CharacterSettings>

and new just created in newest relise db
Code:
<CharacterSettings>
  <RepairWhenDurabilityBelow>32</RepairWhenDurabilityBelow>
  <RuleSetPath>Rules\WeightBasedRules.xml</RuleSetPath>
  <LootRadius>60</LootRadius>
  <CombatLooting>true</CombatLooting>
  <OpenLootContainers>false</OpenLootContainers>
  <OpenChests>false</OpenChests>
  <DestroyEnvironment>false</DestroyEnvironment>
  [SIZE=4][COLOR="#FF0000"]<MonsterPowerLevel>6</MonsterPowerLevel>[/COLOR][/SIZE]
  <KillRadius>40</KillRadius>
  <EnabledPlugins>
    <Value>QuestTools</Value>
    <Value>Trinity</Value>
  </EnabledPlugins>
  <ItemWeightSetPath>Rules\DefaultWeightSet.xml</ItemWeightSetPath>
  <ProtectedBagSlots />
  <ProtectedStashPagesFix>None</ProtectedStashPagesFix>
  <UseBookOfCain>true</UseBookOfCain>
</CharacterSettings>

the problem may be line of mp

edit:
new and older setting dosent work ( just yar for new db beta dont change mp in relese db, dont know how it works in beta)
 
you're doing it wrong :)

That can be set through the bot config window.

in the first tab in DB (the "main window") click:

Settings > Bot > Monster Power
 
yep, i know it can be, i use it now, but yar got self option to choose mp lvl (which dont work for me since new versions of yar for beta db)
and like to help you find solution by investigate some
 
R-YAR 0.2.0.17 beta is crashing DemonBuddy after opening it. 0.2.0.16 did not crash DemonBuddy.

Code:
Problem signature:
  Problem Event Name:	CLR20r3
  Problem Signature 01:	demonbuddy.exe
  Problem Signature 02:	1.0.1446.317
  Problem Signature 03:	52376d0e
  Problem Signature 04:	YAR_635170262138223226
  Problem Signature 05:	0.0.0.0
  Problem Signature 06:	52575316
  Problem Signature 07:	15
  Problem Signature 08:	51
  Problem Signature 09:	System.NullReferenceException
  OS Version:	6.1.7601.2.1.0.256.1
  Locale ID:	1033
  Additional Information 1:	0a9e
  Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:	0a9e
  Additional Information 4:	0a9e372d3b4ad19135b953a78882e789
 
Why does it auto close the game and bot and restart when I "stop" the bot on DB? On the original version it wouldn't do this and I could stop the bot to sell ah stuff etc. and start it back manually no prob. Now, it restarts the bot within like 30-40 secs after I stop it on DB. Antiidle is off b/c DB already takes care of this.

Plz don't tell me to be able to stop the bot to sell etc. I have to turn off YAR and restart all my games manually.
 
as rixx write after my post, its temporary turned off while yar got problems with beta demonbuddy, use pauze yar to stop closing clients
 
Why does it auto close the game and bot and restart when I "stop" the bot on DB? On the original version it wouldn't do this and I could stop the bot to sell ah stuff etc. and start it back manually no prob. Now, it restarts the bot within like 30-40 secs after I stop it on DB. Antiidle is off b/c DB already takes care of this.

Plz don't tell me to be able to stop the bot to sell etc. I have to turn off YAR and restart all my games manually.

Just to clarify, the original version DID do this. You can hit the 'Pause' button and it pause YAR restarting anything.
 
0.2.0.21 posted to Post #1

I've baked this one for a while (herbfunk style :cool:) and it seems to suck less, so that's good.

Error Dialog Handling is baaack yay!

Compatible with Latest DB Beta, but not required...

Unfortunately I had to disable a bunch of Bot Restart logic and YAR can, on occasion, be a little twitchy about restarting bots.

Happy relogging!
 
rrrix.. can you please make this relogger start the bots when its started? ryar is crashing alot for me on windows vista.
 
rrrix.. can you please make this relogger start the bots when its started? ryar is crashing alot for me on windows vista.

Can you send me your logs? PM them if you're concerned. Lets fix the bug, not the symptom... i'm not making a relogger for a relogger...
 
Can you send me your logs? PM them if you're concerned. Lets fix the bug, not the symptom... i'm not making a relogger for a relogger...

Code:
V [04.10.2013 18:00:43] Relogger Thread Starting!N [04.10.2013 18:00:43] rrrix's Yet Another Relogger fork Version 0.2.0.16
D [04.10.2013 18:01:48] Exception: [Invoke eller BeginInvoke kan ikke kalles p? en kontroll f?r vindusreferansen er opprettet.]
System.InvalidOperationException: Invoke eller BeginInvoke kan ikke kalles p? en kontroll f?r vindusreferansen er opprettet.
   ved System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
   ved System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
   ved System.Windows.Forms.Control.Invoke(Delegate method)
   ved YetAnotherRelogger.StatsUpdater.CreateChartStats(BotClass bot, Chart graph, ChartValueType valueType)
D [04.10.2013 18:01:48] Exception: [Invoke eller BeginInvoke kan ikke kalles p? en kontroll f?r vindusreferansen er opprettet.]
System.InvalidOperationException: Invoke eller BeginInvoke kan ikke kalles p? en kontroll f?r vindusreferansen er opprettet.
   ved System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
   ved System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
   ved System.Windows.Forms.Control.Invoke(Delegate method)
   ved YetAnotherRelogger.StatsUpdater.CreateChartStats(BotClass bot, Chart graph, ChartValueType valueType)
D [04.10.2013 18:01:48] Exception: [Invoke eller BeginInvoke kan ikke kalles p? en kontroll f?r vindusreferansen er opprettet.]
System.InvalidOperationException: Invoke eller BeginInvoke kan ikke kalles p? en kontroll f?r vindusreferansen er opprettet.
   ved System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
   ved System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
   ved System.Windows.Forms.Control.Invoke(Delegate method)
   ved YetAnotherRelogger.StatsUpdater.CreateChartStats(BotClass bot, Chart graph, ChartValueType valueType)
D [04.10.2013 18:01:48] Exception: [Invoke eller BeginInvoke kan ikke kalles p? en kontroll f?r vindusreferansen er opprettet.]
System.InvalidOperationException: Invoke eller BeginInvoke kan ikke kalles p? en kontroll f?r vindusreferansen er opprettet.
   ved System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
   ved System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
   ved System.Windows.Forms.Control.Invoke(Delegate method)
   ved YetAnotherRelogger.StatsUpdater.CreateChartStats(BotClass bot, Chart graph, ChartValueType valueType)
N [04.10.2013 18:01:50] Closed!



V [04.10.2013 19:08:42] Relogger Thread Starting!
N [04.10.2013 19:08:42] rrrix's Yet Another Relogger fork Version 0.2.0.17
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout)
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:21:37] System.Threading.ThreadAbortException: Thread was being aborted.
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
   ved YetAnotherRelogger.Helpers.Stats.CpuRamUsage.Update()
N [04.10.2013 19:22:44] Closed!
 
I installed the new relogger version 2.0.21 but now it gives compiledassemblies errors that ddl files are used by another process (and its not possible) It also fails to load plugins.
 
Just to clarify, the original version DID do this. You can hit the 'Pause' button and it pause YAR restarting anything.


Just to over clarify.....the 1.9.2 beta version originally done by the maker DID NOT do this. That is the version I've always used and I have always stopped my bots that way.

Thanks for making me aware of the pause on YAR. I've never even noticed it lol.

Also thanks for working on this even though it really isn't your prob/responsibility.

And like Zakne11 says.......21 has basically made it unusable for me..my cpu usage stays 100% now
 
First I misstook the high CPU usage for a Trinity .8 issue ...

?dit: nvm
 
Back
Top