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

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[StandAlone] Yet Another Relogger!

Status
Not open for further replies.
Ok, I'm posting another reply to this thread because I received no response from my previous one:

- This program was working for me flawlessly on 4 of my bots in the past.
- One day, my internet was very unstable and I did not have internet for 4-5 hours out of 6, and I had YAR on. This caused everything to crash and I had to force shut down my computer.
- After network problem got fixed this problem started occurring and I am unable to use YAR to bot.

Here is the problem:
-I start YAR, start one bot, everything works fine until the bot gets in a game. The bot would start lagging hard, and start freezing every 1-2 seconds. Then the bot will get in combat and my character end up attacking the mobs once or twice while lagging, then end up standing there to get killed. Same process repeats until the bot completely freezes and restart itself. Same cycle repeats.

Here is the Error log:
[23/01/2013 9:07:08 PM] Relogger Thread Starting!
[23/01/2013 9:07:10 PM] Yet Another Relogger Version 0.1.9.2
[23/01/2013 9:07:28 PM] Closed!
[23/01/2013 9:07:53 PM] Relogger Thread Starting!
[23/01/2013 9:07:54 PM] Yet Another Relogger Version 0.1.9.2
[23/01/2013 9:08:11 PM] Editing bot: bot
[23/01/2013 9:08:14 PM] <bot> We are scheduled to start
[23/01/2013 9:08:14 PM] <bot> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[23/01/2013 9:08:14 PM] <bot> Language set: English (US) : enUS
[23/01/2013 9:08:14 PM] <bot> Region set: America : us.actual.battle.net
[23/01/2013 9:08:26 PM] <bot> Diablo:6276: Found D3 Main Window (1902750)
[23/01/2013 9:08:32 PM] <bot> Diablo:6276: Waiting for process to become ready
[23/01/2013 9:08:34 PM] <bot> Diablo:6276: Process is ready
[23/01/2013 9:08:34 PM] <bot> Demonbuddy start delay, waiting 10 seconds
[23/01/2013 9:08:45 PM] <bot> Current profile: "Tinnkaizer v0.7.xml" Runs:0 Time:0 mintues (G:\Demonbuddy\Profiles\Tinnkaizer v0.7.xml)
[23/01/2013 9:08:45 PM] <bot> Using a already generated Kickstart profile: G:\Demonbuddy\Profiles\YAR_Kickstart.xml
[23/01/2013 9:08:45 PM] <bot> Checking plugin: G:\Demonbuddy\Plugins\YAR\Plugin.cs
[23/01/2013 9:08:45 PM] <bot> Plugin is installed and latest version
[23/01/2013 9:08:45 PM] <bot> Demonbuddy:5140: Waiting for process to become ready
[23/01/2013 9:08:46 PM] <bot> Found Demonbuddy: MainWindow (591838)
[23/01/2013 9:08:46 PM] <bot> Demonbuddy:5140: Process is ready
[23/01/2013 9:08:46 PM] <bot> Demonbuddy:5140: Waiting for demonbuddy to log into Diablo
[23/01/2013 9:09:11 PM] <bot> Demonbuddy:5140: Initialized! We are ready to go
[23/01/2013 9:09:43 PM] <bot> Demonbuddy:5140: is not in a game to long for unkown reason (30 seconds)
[23/01/2013 9:09:53 PM] <bot> Sending MonsterPowerLevel: Disabled
[23/01/2013 9:11:29 PM] <bot> Diablo:6276: Is unresponsive for more than 60 seconds
[23/01/2013 9:11:29 PM] <bot> Diablo:6276: Killing process
[23/01/2013 9:11:29 PM] <bot> Diablo:6276: Process is not running
[23/01/2013 9:11:29 PM] <bot> Demonbuddy:5140: Closing db
[23/01/2013 9:11:29 PM] <bot> Demonbuddy:5140: Waiting to close
[23/01/2013 9:11:31 PM] <bot> Demonbuddy:5140: Closed.
[23/01/2013 9:11:31 PM] <bot> Killing Agent.exe:6696
[23/01/2013 9:11:31 PM] <bot> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[23/01/2013 9:11:31 PM] <bot> Language set: English (US) : enUS
[23/01/2013 9:11:31 PM] <bot> Region set: America : us.actual.battle.net
[23/01/2013 9:11:43 PM] <bot> Diablo:4196: Found D3 Main Window (723022)
[23/01/2013 9:11:49 PM] <bot> Diablo:4196: Waiting for process to become ready
[23/01/2013 9:11:51 PM] <bot> Diablo:4196: Process is ready
[23/01/2013 9:11:51 PM] <bot> Demonbuddy start delay, waiting 10 seconds
[23/01/2013 9:12:01 PM] <bot> Demonbuddy:5140: Found matching log: G:\Demonbuddy\Logs\5140 2013-01-23 21.08.txt
[23/01/2013 9:12:01 PM] <bot> Found login time: 24/01/2013 5:08:48 AM
[23/01/2013 9:12:01 PM] <bot> Checking plugin: G:\Demonbuddy\Plugins\YAR\Plugin.cs
[23/01/2013 9:12:01 PM] <bot> Plugin is installed and latest version
[23/01/2013 9:12:01 PM] <bot> Demonbuddy:5276: Waiting for process to become ready
[23/01/2013 9:12:02 PM] <bot> Found Demonbuddy: MainWindow (1968286)
[23/01/2013 9:12:02 PM] <bot> Demonbuddy:5276: Process is ready
[23/01/2013 9:12:02 PM] <bot> Demonbuddy:5276: Waiting for demonbuddy to log into Diablo
[23/01/2013 9:12:19 PM] <bot> Stopping
[23/01/2013 9:12:19 PM] <bot> Diablo:4196: Kill process
[23/01/2013 9:12:19 PM] <bot> Demonbuddy:5276: Failed to close! kill process
[23/01/2013 9:12:19 PM] Relogger Thread Starting!
[23/01/2013 9:13:07 PM] Closed!

my approach on fixing this problem:
-Download a completely new demonbuddy and manually install all the plugins, combat routines, and profiles.
-Download a completely new copy of Diablo III.
-Download a fresh YAR.
-Tried the above three on all different drives on my PC, and I got the same problem.
-Recently I got desperate enough, I re-formatted my PC, and installed everything brand new.
-Same problem occurs and I am extremely frustrated after having to re-format my PC and everything.

If I do not use YAR, the bot runs smoothly, and I can run all 4 of my bots together. The my Diablo III freezes whenever I use YAR, even with only 1 Diablo III open.

I feel like I did everything that I can do (other than buying another PC) and I still cannot seem to find a solution to my problem.

Please let me know if any of you experienced the same issue. If you know a solution to my problem please let me know. Your help is appreciated...
 
System.IO.IOException: Pipe is broken.
at System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
at System.IO.Pipes.PipeStream.EndWrite(IAsyncResult asyncResult)
at System.IO.Pipes.PipeStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.IO.TextWriter.WriteLine(String value)
much errors like this and game restart, how to solve? i find this log in YAR logfile
 
when i use yar and new db .298 and trinity .16, db will say that there is no trinity combat routine, no matter what i chose from the drop down in my yar profile. before i updated, i had to type in "Trinity" in the yar profile and it worked. now the only combat routine i can get to work is belphegor... anyone knows if i'm doing sth wrong or how i can fix this?
 
Skazer said:
How can I use the authenticator settings ?
Click to expand...

you can't, they are not implemented.

i'm getting this message: "There is no profile loaded. Please load a profile before starting the bot". Kickstart is enabled. How to fix this?
 
SACBliQ.webp

Anyone? I cant find the solution.. When I leave it on and go away/sleep for couple of hours, that message is what I return to.
 
I tried to set Randomization in Week schedule (Min and Max minutes) many times but it doesn't work

For example
Min = 5
Max = 20
Schedule at 18.00

Bot should start 18.05 until 18.20

but it always start at schdule time (18.00)

Can everyone use this function?
Please advice me. Thank you.
 
maxmakung said:
I tried to set Randomization in Week schedule (Min and Max minutes) many times but it doesn't work

For example
Min = 5
Max = 20
Schedule at 18.00

Bot should start 18.05 until 18.20

but it always start at schdule time (18.00)

Can everyone use this function?
Please advice me. Thank you.
Click to expand...
works fine for me, didn't do anything about it. just set min and max time :x
 
N [1/25/2013 1:05:40 PM] <Europeanu 5> Standby!
N [1/25/2013 1:05:40 PM] <Europeanu 5> Diablo:7844: Kill process
N [1/25/2013 1:05:40 PM] <Europeanu 5> Demonbuddy:7444: Failed to close! kill process
N [1/25/2013 1:05:40 PM] <Europeanu 5> Diablo:7844: Process is not running
N [1/25/2013 1:05:40 PM] <Europeanu 5> Killing Agent.exe:8576
N [1/25/2013 1:05:40 PM] <Europeanu 5> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
N [1/25/2013 1:05:40 PM] <Europeanu 5> Language set: English (US) : enUS
N [1/25/2013 1:05:40 PM] <Europeanu 5> Region set: Europe : eu.actual.battle.net
N [1/25/2013 1:05:49 PM] <Europeanu 5> Stopping
N [1/25/2013 1:05:49 PM] <Europeanu 5> Diablo:5916: Kill process
N [1/25/2013 1:05:50 PM] <Europeanu 6> Stopping

Over and over and over for hours if i dont stop YAR. Now i just log them with YAR and close YAR and everything works fine i manually close them and open the next bots at setted schedule with yar...... atleast until its fixed...
 
ezpwnd said:
i'm getting this message: "There is no profile loaded. Please load a profile before starting the bot". Kickstart is enabled. How to fix this?
Click to expand...

this problem is still present, even though i'm using the experimental build atm. strange thing, first time i start yar it will usually work - but when one of the bots crashes and YAR needs to restart it the message will pop again.

db-window will show this:
[17:39:20.340 N] Demonbuddy v1.0.1309.298 started
[17:39:20.378 N] Logging in...
[17:39:20.917 N] Attached to Diablo III with pid: 6732
[17:39:23.718 N] Failed to load profile: Element TrinityMoveTo is not supported. Please check your XML and try again. (<TrinityMoveTo questId="101758" stepId="1" x="183.6722" y="720.6746" z="-47.19459" name="Arreat Core-11" navigation="true" />) Line 18
[17:39:23.809 N] Chose Trinity as your combat routine.
Click to expand...
 
Does anybody know why can't I use d3starter option? When enabled YAR just starts Diablo 3 Launcher, not the game, and trying to restart it every 10 seconds.
Here is what I see in YAR log:

[1/25/2013 22:31:48] <d3first> We are scheduled to start
[1/25/2013 22:31:48] <d3first> Killing Agent.exe:3860
[1/25/2013 22:31:48] <d3first> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[1/25/2013 22:31:48] <d3first> Language set: English : enGB
[1/25/2013 22:31:48] <d3first> Region set: Europe : eu.actual.battle.net
[1/25/2013 22:31:48] <d3first> D3Starter: Val: True
[1/25/2013 22:31:48] <d3first> D3Starter: Val: True
[1/25/2013 22:31:48] <d3first> D3Starter: Process ID 424 started.
[1/25/2013 22:31:48] <d3first> D3Starter: Patching process 424
[1/25/2013 22:31:48] <d3first> D3Starter: Patching file access at address: 81C29D
[1/25/2013 22:31:48] <d3first> D3Starter: Resuming process 424
[1/25/2013 22:31:50] <d3first> D3Starter: 1 game instances started! All done!
[1/25/2013 22:31:50] Relogger Crashed! with message Access is denied
[1/25/2013 22:31:50] at System.Diagnostics.Process.set_ProcessorAffinity(IntPtr value)
at YetAnotherRelogger.Helpers.Bot.DiabloClass.Start()
at YetAnotherRelogger.Relogger.StartBoth(BotClass bot)
at YetAnotherRelogger.Relogger.ReloggerWorker()
[1/25/2013 22:31:50] Waiting 10 seconds and try again!
Click to expand...
 
Last edited:
First of all, this program is amazing.

I just had a question in regards to loading individual D3 perfs. I want to assign unique D3 perfs to my non-bot clients as well, could you shed some light if this is possible without a 3rd party program?
 
Ptshck said:
Does anybody know why can't I use d3starter option? When enabled YAR just starts Diablo 3 Launcher, not the game, and trying to restart it every 10 seconds.
Here is what I see in YAR log:
Click to expand...
I have the same problem.
 
Status
Not open for further replies.
Back
Top