[StandAlone] Yet Another Relogger!

I don't know if I'm first reporting this bug, but it seems very serious:

I'm running bot on VM, latest DB/Trinity and nothing else, minimal d3prefs and high priority for D3. Sometimes, YAR decide just to kill both processes for no reasons. Right in the middle of the run, even when all works fine and internet connection is nice. First i thought its bcos of stucks or smth (though i never turn on yar's "gold inactivity"). I decided to check it, and watched it by myself several times. Here is the last yar's log:

[3/14/2013 5:56:54 PM] <[A3]_1> Sending MonsterPowerLevel: Level2
[3/14/2013 6:20:18 PM] <[A3]_1> Diablo:1516: Process is not running <==========
[3/14/2013 6:20:18 PM] <[A3]_1> Demonbuddy:2200: Closing db
[3/14/2013 6:20:18 PM] <[A3]_1> Demonbuddy:2200: Waiting to close
[3/14/2013 6:20:23 PM] <[A3]_1> Demonbuddy:2200: Closed.
[3/14/2013 6:20:23 PM] PingCheck: Ping -> www.google.com
[3/14/2013 6:20:23 PM] PingCheck: 173.194.71.103 -> 94ms
[3/14/2013 6:20:23 PM] <[A3]_1> Killing Agent.exe:1264
[3/14/2013 6:20:23 PM] <[A3]_1> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[3/14/2013 6:20:23 PM] <[A3]_1> Region set: Europe : eu.actual.battle.net
[3/14/2013 6:20:47 PM] <[A3]_1> Diablo:3436: Found D3 Main Window (1901914)
[3/14/2013 6:20:55 PM] <[A3]_1> Diablo:3436: Waiting for process to become ready
[3/14/2013 6:20:57 PM] <[A3]_1> Diablo:3436: Process is ready
[3/14/2013 6:20:57 PM] <[A3]_1> Demonbuddy start delay, waiting 17 seconds

Hey, "Process is not running"? Srsly? How about it actually WAS running and u just killed it with ur own hands u lil bastard ?Bot was feeling fine with 5nv stacks on FOS and was busy killing another rare pack ;p
There wasn't any error dialogue also. And actually when there is one, yar close it and writes about it in log.

Just wondering how many times he does it per night TT. That's sad. Anybody else with this?..

(just got another one while posting this, in other place this time:
[3/14/2013 6:42:36 PM] <[A3]_1> Sending MonsterPowerLevel: Level2
[3/14/2013 7:00:21 PM] <[A3]_1> Diablo:1536: Process is not running
[3/14/2013 7:00:21 PM] <[A3]_1> Demonbuddy:1044: Closing db)

[PERCENTAGE][/PERCENTAGE]

Here is another solution for you! a little bit late though :
in bot edit settings where yar gives u a box to select the routine, instead of chosing GilePlugin or Giles Routine just write down "Trinity" (exactly as it appears in file, "Trinity") then click "save". BUT AN IMPORTANT NOTE IS, we have a bug here: after u will edit ANYTHING in THIS bot settings again (anything, on any page, any time) routine setting will reset back to Belphegor - so you just need to remember to set it back to "Trinity" and click "save" again.

 

edit:fixed

 

Im facing the same problem here. What you did?

 

http://www.thebuddyforum.com/demonbuddy-forum/plugins/111260-r-yar-rrrixs-yar-fork.html

 

Okay got this very strange issue that has haunted me the past day.
So after patch everything worked perfectly until my main bot started getting this error and closes up starts up several times per hour

Exception: [Pipe is broken.]
System.IO.IOException: Pipe is broken.
at System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
at System.IO.Pipes.PipeStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.Pipes.PipeStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.IO.StreamWriter.Write(Char[] buffer, Int32 index, Int32 count)
at System.IO.TextWriter.WriteLine(String value)
at YetAnotherRelogger.Helpers.Communicator.HandleClie nt.Send(String msg)

It is really weird because i've tried to make a new profile on another computer on 2 different builds 2 different builds on my main computer and everytime it's only the main bot getting this error. my other 4 bots work just fine but i cannot really bot at all with my main bot. Does anyone have a slighest idea what might be causing this? This is really weird because I haven't made any changes to the settings and suddely the main bot starts closing and starting up few times an hour. other bots work just fine. And it can't be fixed by using other versions and even other computer. Still the same issue on just this particular bot.

 

still staying at the login screen... =/

 

After the patch, anybody getting more of these?

N [3/14/2013 11:35:31 PM] <BARB04> Diablo:3810: Process is not running

Happens randomly and crashes D3 because it doesn't detect it. I watched my bots for awhile and the problem occurs despite any issues with Diablo 3 (it doesn't hang or freeze).

Using .304 / Trinity 1.7.2.9 / Clones / Specific Users

 

Mine Works Fine. Ran It For 26 Hours Straight.

 

This is my issue, in the picture I linked, under "Status" for YAR, it says "Starting Demonbuddy." This is fine and all.... except, it doesn't seem to detect demonbuddy, even though... Demonbuddy is launched, and it has me join a game like usual, only to crash about 3 minutes into the run, due to it not being able to launch Demonbuddy... even though, as I said, it already is launched, and the bot is working. Any suggestions?

 

You took a screenshot of your PC DESKTOP - with a mobile?

 

Yes, my PrintScreen key on my keyboard is fucked up, so, I have to resort to that.

 

Have u filled in "week schedule" in bot settings of yar? Make sure all squares are green.
Just incase. Some ppl forget doing this. Happens.

 

I have problem with YAR and DB, when i run D3 with DBv304. it works properlly, but when i try to run it with YAR [newest version] it crashes before it even log-in.

 

Sure! Its all green! =(

 

Almost every time the Bot identified I get this error:

N [19.03.2013 00:45:04] <h> Demonbuddy:848: is not pulsing while it should to (60 seconds)
N [19.03.2013 00:45:04] <h> Sending MonsterPowerLevel: Disabled
N [19.03.2013 00:47:04] <h> We did not recieve any stats during 120 seconds!
N [19.03.2013 00:47:04] <h> Restarting...
N [19.03.2013 00:47:04] <h> Diablo:1240: Kill process

Can someone help me please

YARComm Plugin in enabled in DB

 

I'm having problems getting Yar to run. After a new game is started, demonbuddy gives me the log,

[18:58:29.491 N] Loaded profile YAR Profile Kickstart: Galkaizer_v4.xml
[18:58:29.491 N] Game joined, Resetting profile caches.
[18:58:29.504 N] ProfileOrderManager.OnGameJoined, Reloading profile.
[18:58:29.651 N] Loaded profile YAR Profile Kickstart: Galkaizer_v4.xml
[18:58:29.651 N] Game joined, Resetting profile caches.
[18:58:29.670 N] ProfileOrderManager.OnGameJoined, Reloading profile.
[18:58:29.818 N] Loaded profile YAR Profile Kickstart: Galkaizer_v4.xml
[18:58:29.818 N] Game joined, Resetting profile caches.
[18:58:29.830 N] ProfileOrderManager.OnGameJoined, Reloading profile.
[18:58:29.979 N] Loaded profile YAR Profile Kickstart: Galkaizer_v4.xml
[18:58:29.979 N] Game joined, Resetting profile caches.
[18:58:29.997 N] ProfileOrderManager.OnGameJoined, Reloading profile.
[18:58:30.145 N] Loaded profile YAR Profile Kickstart: Galkaizer_v4.xml
[18:58:30.145 N] Game joined, Resetting profile caches.
[18:58:30.157 N] ProfileOrderManager.OnGameJoined, Reloading profile.
[18:58:30.305 N] Loaded profile YAR Profile Kickstart: Galkaizer_v4.xml
[18:58:30.305 N] Game joined, Resetting profile caches.
[18:58:30.323 N] ProfileOrderManager.OnGameJoined, Reloading profile.
[18:58:30.472 N] Loaded profile YAR Profile Kickstart: Galkaizer_v4.xml
[18:58:30.472 N] Game joined, Resetting profile caches.
[18:58:30.484 N] ProfileOrderManager.OnGameJoined, Reloading profile.
[18:58:30.633 N] Loaded profile YAR Profile Kickstart: Galkaizer_v4.xml.

Ad infinitum

 

Hi Guys.

New to YAR i was doing all manually by now.
Everything works great - but i see there is a option to lower the instalation size (instead of copy each D3 it only takes ~200 MB) but i have problems with launch it.
Also i see there is D3Starter.exe in the YAR package but tbh i do not know what this program does.
I was trying to read this topic for any replays/guides but 200 pages is killing me...

If someone know how to set it up correct plz write

 

I keep getting this error how do I fix it plz

N [3/23/2013 5:57:40 PM] <XP> Demonbuddy:4856: Failed to initialize more than 3 times
N [3/23/2013 5:57:40 PM] <XP> Standby!
N [3/23/2013 5:57:40 PM] <XP> Diablo:6924: Kill process
N [3/23/2013 5:57:40 PM] <XP> Demonbuddy:4856: Failed to close! kill process

 

please sinterlkaas please.. comeback and fix the stuf.. TT

ye I have this also sometimes. Not very often though, but it completely stops botting, so its kinda dangerous. Any ideas how it could be fixd?..

 

Where are yar window size settings saved? (settings-relogger-autoposition-default 320x200).
I changed them from defaults but next boot it gets back to 320x200.