[StandAlone] Yet Another Relogger!

I tried using this but when it loaded up D3 it wouldn't input my username and password for me, it was just idle.

 

try removing the plugin YAR from your DB plugins ,and inputting your PW again in YAR. worked for me=)

 

Had the exact same problem at the exact same time as you yesterday ??
This was the first time I experienced this though.

 

Are anyone elses profiles looping after a relog? Using radsAtom 1.51 got my started profiles act 1,2,3 in the scheduler but after a relog it only stays in act one and does not load others.

BTW FANTASTIC WORK man. Donated some cash :_) more coming your way this week when payday comes.

 

Hello guys. How to enable an authenticator?
Sorry for this noob question
Image 1353922430-clip-40kb.jpg

 

this is TODO feature. no ETA time

 

Ya deleted YAR plugin restarted YAR.exe and still not inputting my password. A popup says theres no profile loaded. Please load profile before starting the bot.

Then this '

[02:44:37.949 N] Demonbuddy v1.0.1194.285 started
[02:44:37.992 N] Logging in...
[02:44:39.105 N] Attached to Diablo III with pid: 4956
[02:44:42.327 N] Failed to load profile: Element SafeMoveTo is not supported. Please check your XML and try again. (<SafeMoveTo questId="80322" stepId="-1" pathPrecision="2" x="291" y="233" z="0" xmlns="http://tempuri.org/rrrixProfiles.xsd" />) Line 137
[02:44:42.407 N] Chose Belphegor All-in-One as your combat routine.
[02:44:42.407 N] [Belphegor All-in-One 1.0.1194.285] Building method list
[02:44:42.407 N] [Belphegor All-in-One 1.0.1194.285] Added 66 methods
[02:44:42.417 N] [Belphegor All-in-One 1.0.1194.285] InvalidWrapper is a match!
[02:44:42.417 N] [Belphegor All-in-One 1.0.1194.285] Using InvalidWrapper for Combat (Priority: 0)
[02:44:42.417 N] [Belphegor All-in-One 1.0.1194.285] InvalidWrapper is a match!
[02:44:42.417 N] [Belphegor All-in-One 1.0.1194.285] Using InvalidWrapper for Buff (Priority: 0)
[02:44:42.417 N] [Belphegor All-in-One 1.0.1194.285] Movement support for Invalid is not currently implemented.
[02:44:42.427 N] [Belphegor All-in-One 1.0.1194.285] Behaviors created

 

yes the found matching log keeps on looping.

not sure which setting triggers it.

i downgrade back to 0.0.0.6 and its fine.

 

Although this is slightly off topic even though sinterlkaas said he would try add the feature in the future, but does everyone here have no reason to create a unique ID for each client to help avoid the ban hammer in the way that D3loader does? Because although I've tried YAR and think its absolutely amazing at what it does, I personally beleive that it may be unsafe until this unique ID per client has been achieved within YAR. Does anyone here have any/much experience with multiple bots(4+) running bots for any length of time without facing the banhammer, because as i'm relatively new to botting (<1 month) it's hard to find a level of "safety"(used loosely) to be comfortable with.

If YAR had a way of achieving and maintaining this unique ID it would fit all purposes perfectly, perhaps there would be a way of incorporating D3launcher's methods into the way YAR loads DB/D3 rather than using Apoc D3starter???

 

I think it would be possible to get unique ID using different windows users to launch each d3 client.

 

Suggestion (I actually mentioned this a few posts back):

Can you add a "max" relog attempts within X time setting? For example, if you relog (from a crash, dc, otherwise) more than 5 (x value) times within 1 hour (x value), wait 45 minutes (x value) before trying again. I think that's what actually partly fucked me when i got banned last month. With the auth servers shitting on me, having each account relog every 2 minutes for 8 hours at a time probably set off some flag somewhere.

 

Suggestion :

You can add possibility to run cmd before and after start cycle, with cmd I can copy custom D3Perf file and merge .reg with Unique ID specific to bot you start.

Many thanks

 

This is how i'm currently using D3Launcher with D3 A and DB A = User A, D3 B and DB B = User B etc, just wish it was implemented in YAR, must be noted however that Demonbuddy needs to be started with the same user as the d3 client else it cannot communicate correctly, but this actually seems to be a useful feature as it helps prevent DB from connecting to the wrong D3 client and causing issues such as if the DB was optimised for a barb and connected to a Monk acc or DB was configured on account A to have no protected stash pages but account B had 1 stash page protected etc.

This is what i requested previously which sinterlkaas said he would look into, however since then i've been thinking this method would probably have more chance for error prompting blizzard's security questions if done incorrectly once a client crashes etc and needs reloading as it would likely require additional safety delays before launch compared to just running as different users.

 

OK will try Thanks

 

Ok, I've found the reason why yar isn't filling my acc and pass. It only happens on accs with "." symbol in mail. Any idea how to fix that without changing mail? Thanks in advance

 

Still looping profiles ;(

 

[20:53:09.296 N] Logging in...
[20:53:10.166 N]
Max Sessions
[20:53:10.438 N] Authentication failed!

Over and over again. Happens every time D3 crashes and this plugin tries to restart it, anyone got a workaround?

 

yep same issue
it works after a while

on another issue


radsatom 1.51, trinity 1.6.3.4 neo edit and YAR tried 06,1.7.7,1.8.2
Loads my startact2.xml on lets say act 2 and in the schedule its set to load act 3 and then act 1 but it stays on act 2

any ideas?
btw I have to use Radsatom due to profiles

 

1.8.2 works with radstorm 1.53

and start.xml files work with scheduler as long as yar does not go into sleep mode or need to restart. The moment it restarts it will stay on the profile it restarted on, meaning if you have profiles that switch between acts or profiles with different randomization's it misfunctions after a restart. Maybe a way to fix this is to restart yar when it needs to restart and relog everything back in?

 

Help!

My relogger stopped working for no apparent reason today. The only thing that has been modified is my location (visiting parents place this week).

With this i got account locked - because of altered logging in habits - unlocked and everything is fine.
Although i start relogger, and all it does is goes into game, selects a waypoint randomly, does not precast any auras (playing barb), runs up to a pack of monsters and dies.

I have tried updating the relogger to 1.8.2, but that didnt help, so i downgraded back to 0.0.6... This was working perfectly until today. What can have happened??

I might add that if i run only the demonbuddy it works fine - just that if i go to sleep i know the whole thing is bound to crash, and with no relogger on top of that not many runs will be made... What has happened to my wonderful relogger?

(did not find any support thread for the relogger - hence why im writing here) Thanks in advance!