[StandAlone] Yet Another Relogger!

Thx in advance!

 

hi sinterlkaas ,You are use the VS2010?
i use vs2012 it give this error C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(4264,5): error MSB3073,from 0.1.9.0,but YetAnotherRelogger.exe can work fine.

 

Any success adding custom username/password (winuser) to ProcessStartInfo ?

 

sinterlkaas, great plugin! Can u add another foreground checker (for diablo 3 not demonbuddy). Its much faster on vmware when on top.
ForegroundChecker

 

Session killer is not working

Using last version of YAR.

Getting messages:
[13:52:45.353 N] Authentication failed!
[13:52:45.354 N] Logging in...
[13:52:45.553 N] Max Sessions

 

The foreground checker already is working for diablo it is just to bring DB to front and then switch back to diablo .. useful when you have like 5+ bots and not using giles plugin to show the btag in title
but you are asking to keep diablo ontop no matter what happens force it to top again ?

To be honest I did not try yet but it is still on my todo list .. Today I was thinking about some possibilities on how I want to implement it and what it should do

The session killer is working bot not always 100% accurate I will improve it in a later release please be patience

 

Hi, I know i have read somewhere from someone in this topic and I would just like to bring it up again if it was overlooked,

I would like next to the "Pause" button a button of "Force Resize". It would help allot for when I need to read some stats of an items so i know the value and so I can later make an easy resizing back to 360*240 or whatever resolution I have.
btw, thanks for everything you have done, great job!

This idea aint mine, i'm just bumping it if it was bypassed.

 

deleted

 

Recently updated 0.0.0.4 to 0.1.8.5 and not liking it so far, I need to pause the bot and the relogger if I want to do something. Is it possible to get a link to 0.0.0.4 or be able to disable this feature please .

 

here is the log:


[2012/12/4 4:01:00] <Diablo BOT> We are scheduled to stop
[2012/12/4 4:01:00] <Diablo BOT> Next scheduled start: 4/12 11:1
[2012/12/4 4:01:00] <Diablo BOT> Diablo:4944: Kill process
[2012/12/4 4:01:00] <Diablo BOT> Demonbuddy:5536: Failed to close! kill process
[2012/12/4 11:01:00] <Diablo BOT> We are scheduled to start
[2012/12/4 11:01:00] <Diablo BOT> Next scheduled stop: 5/12 10:1
[2012/12/4 11:01:00] <Diablo BOT> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[2012/12/4 11:01:00] <Diablo BOT> Language set: Chinese : zhCN
[2012/12/4 11:01:00] <Diablo BOT> Region set: America : us.actual.battle.net
[2012/12/4 11:01:08] <Diablo BOT> Diablo:4524: Found D3 Main Window (1180874)
[2012/12/4 11:01:10] <Diablo BOT> Diablo:4524: Waiting for process to become ready
[2012/12/4 11:01:12] <Diablo BOT> Diablo:4524: Process is ready
[2012/12/4 11:01:12] <Diablo BOT> Demonbuddy start delay, waiting 10 seconds
[2012/12/4 11:01:22] <Diablo BOT> Demonbuddy:5536: Found matching log: D:\games\Demonbuddy 1.0.1204.287\Logs\5536 2012-12-03 11.37.txt
[2012/12/4 11:01:24] <Diablo BOT> BuddyAuth: No session found.
[2012/12/4 11:01:24] <Diablo BOT> Current profile: "BigRed_START_HERE.xml" Runs:2 Time:180 mintues (D:\games\Linked+1.1\Linked 1.1\BigRed_START_HERE.xml)
[2012/12/4 11:01:24] <Diablo BOT> Using a already generated Kickstart profile: D:\games\Linked+1.1\Linked 1.1\YAR_Kickstart.xml
[2012/12/4 11:01:24] <Diablo BOT> Checking plugin: D:\games\Demonbuddy 1.0.1204.287\Plugins\YAR\Plugin.cs
[2012/12/4 11:01:24] <Diablo BOT> Plugin is installed and latest version
[2012/12/4 11:01:24] <Diablo BOT> Demonbuddy:4568: Waiting for process to become ready
[2012/12/4 11:01:24] <Diablo BOT> Found Demonbuddy: MainWindow (722714)
[2012/12/4 11:01:24] <Diablo BOT> Demonbuddy:4568: Process is ready
[2012/12/4 11:04:24] <Diablo BOT> Demonbuddy:4568: Failed to initialize
[2012/12/4 11:04:24] <Diablo BOT> Demonbuddy:4568: Forced to close!
[2012/12/4 11:04:26] <Diablo BOT> Demonbuddy:4568: Found matching log: D:\games\Demonbuddy 1.0.1204.287\Logs\4568 2012-12-04 11.01.txt
[2012/12/4 11:04:28] <Diablo BOT> BuddyAuth: No session found.
[2012/12/4 11:04:28] <Diablo BOT> Current profile: "BigRed_START_HERE.xml" Runs:2 Time:180 mintues (D:\games\Linked+1.1\Linked 1.1\BigRed_START_HERE.xml)
[2012/12/4 11:04:28] <Diablo BOT> Using a already generated Kickstart profile: D:\games\Linked+1.1\Linked 1.1\YAR_Kickstart.xml
[2012/12/4 11:04:28] <Diablo BOT> Checking plugin: D:\games\Demonbuddy 1.0.1204.287\Plugins\YAR\Plugin.cs
[2012/12/4 11:04:28] <Diablo BOT> Plugin is installed and latest version
[2012/12/4 11:04:28] <Diablo BOT> Demonbuddy:5672: Waiting for process to become ready
[2012/12/4 11:04:28] <Diablo BOT> Found Demonbuddy: MainWindow (1246388)
[2012/12/4 11:04:28] <Diablo BOT> Demonbuddy:5672: Process is ready
[2012/12/4 11:07:28] <Diablo BOT> Demonbuddy:5672: Failed to initialize more than 3 times
[2012/12/4 11:07:28] <Diablo BOT> Stopping
[2012/12/4 11:07:28] <Diablo BOT> Diablo:4524: Kill process
[2012/12/4 11:07:28] <Diablo BOT> Demonbuddy:5672: Failed to close! kill process
[2012/12/4 11:07:28] <Diablo BOT> Diablo:4524: Process is not running

I bought 3 sessions DB and bot for 4bots,every bot for 18 hours and have a rest for 6 hours.

 

The button is in settings, relogger, autoposition, in the bottom right corner <3

 

He did. You realize there is a randomization on that page right? Min/max. Adjust it and VIOALA randomization.

That being said, i do have a bug i believe, i think caused by the kickstarter that's generated.

Say you have a 7 bots, all launching at once with "start all". Say there are 4 profiles each bot could run. I think that whatever bot logs in first, generates that kickstarter profile, can fuck it up for the rest of the bots unless they are doing that particular profile as well. The issue eventually resolves itself over time, after a few relogs and the bots become out of sync with one another.

Example:

-Start 4 bots at once (using profile kickstarter - this is trying both generating new kickstarter everytime option, and not generating a new one each time)
-Bot 1 loads act 3 big red and runs it just fine
-Bot 2 loads act 2 profile
-Bot 2 now is confused as fuck in act 2, and runs around town like a dumbass for 5 minutes or so until it restarts
-Bot 3 randoms act 3 big red as well, and does the profile just fine
-Bot 4 randoms act 1,
-Bot 4 gets confused as fuck in act 1 town for 5 minutes until it restarts

I can't say for certain it's the kickstarter profile causing it, but i'm thinking it is.

 

I have problems with setting d3 on top (foreground checker)
This works 100% for me using System; using System.Diagnostics; using System.Threading; using YetAn - Pastebin.com

Code:

WinAPI.ShowWindow(hwnd, WinAPI.WindowShowStyle.Minimize);
Thread.Sleep(500);
WinAPI.ShowWindow(_lastDiablo, WinAPI.WindowShowStyle.Minimize);
Thread.Sleep(500);
WinAPI.ShowWindow(_lastDiablo, WinAPI.WindowShowStyle.ShowNormal);
Thread.Sleep(500);
WinAPI.SetForegroundWindow(_lastDiablo);

 

Do check out my thread if you are considering getting Isboxer and using YAR, link right below

 

How does the kickstart function work? When I have it enabled it makes my bots unable to run because it can't find the profile that is supposed to be connected to kickstart.

 

Alright, think about this dude...the thread kicks off at say 6:02. Diablo 3 has to load, then the bot has to load, then the bot logs in diablo 3. Depending on your connection, this is more waiting. EACH ONE of these events is a randomized value; rarely ever would these "seconds" be the same. Not to mention, there are so many other factors that will influence how fast / when shit loads up - other dead diablo 3's queued to load before your scheduled one, latency, cpu load in general, etc, etc. If blizzard was to give two fucks about the SECONDS in which people logged in, it wouldn't be until after they are authenticated. So basically, what your asking him to do, is completely pointless. (not trying to come off mean here, just explaining )

 

I'm having the same Issue!!! I have 5 bots and my CPU is on 80-90% why?!!!!

 

I don't know why it's happening to me too... High CPU Usage... I don't know why but now I can't run more than 5 bots or I will have CPU problems. Someone knows what happens?

Thanks!!

 

need more info to determine, like processor, d3pref whether it changed framerates etc etc. Showing cpu usage will not help in the investigation, for me previously only over 10 bots then cpu usage will spike up

 

- Intel Core I7 930 2.80Ghz Box Socket 1366

- Framerates on Diablo 3 on 40 FPS MAX and 40 FPS MIN

- D3Pref (what do you mean?)

- I must be able to run 10 bots or more with my PC...

If you need more info please tell me.

Thanks, really apprecciate it.

I would like to run 10 bots but I can't and I don't know if it's YAR or what's going wrong...