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.
I was wondering if you could add some code into YAR to close a few error dialogs I've been getting.

Or, better yet help try to find a fix?

Anyways, here are the errors.

1 : http://i47.tinypic.com/2u89l5f.png

2 : http://i50.tinypic.com/szvfwh.png

3 : http://i46.tinypic.com/2s7fiq0.png

They appear in that order, and it will only close diablo is all three have been clicked.

Running Windows XP SP3 , Ive installed all windows updates, and im up to date with the current .net framework.

If you need any additional info, just let me know.
 
NerD said:
I was wondering if you could add some code into YAR to close a few error dialogs I've been getting.
Click to expand...

Been having those for a good while now, it's not related to YAR for me though.
Solution?
I couldn't find one, and believe me, i did try.

But you could try windows recovery/fresh diablo/demonbuddy installation.
Last solution: Reinstall your computer.
 
What's the difference between the patching Apoc starter does, and running as another user?

EDIT: I just started using .92, and noticed a bug where it does not load profiles properly on relog when monster power is set to "disabled" in YAR.
This causes DB to just wait for profile selection, causing eventual relog loop.
Setting MP in YAR seems to resolve this.

EDIT 2: Scratch that. Sometimes setting MP in YAR resolves it. Others, I have to select the profile manually in DB, then restart DB so that it loads all the plugins and continues logging.
 
Last edited:
Well been using the new beta most of today and figured I would drop by and give you some feedback on it (v 0.1.9.2)

- Tried a few different configurations and can not seem to get the hotkeys working

- When I select a specific profile it still only runs the profile in the first spot... (Randomization is working flawlessly though i might add)

- The new Community Trinity now uses "Trinity" as the combat routine instead of "GilesPlugin", has to be manually corrected in xml file

- DB window not coming to front for selected D3 window, receiving msg in log file "Bring attached Demonbuddy to front" but it still remains out of focus (**This issue is intermittent, it works sometimes but mostly doesn't. **)

- YAR seems to be able to get completely unsync'd with what profile DB is actually running, great example I get this in the log "Next profile: E:\Diablo III\__DB__\v288\Profiles\YAR_Kickstart.xml" yet the current and next profile is completely different. This particular bot is running rrrix's Full Questing - All Acts - Complete - Tested, which is also the same profile that is selected under YAR's profile selection. Also ironically this profile is actually in E:\Diablo III\__DB__\v288.Questing-1.1.8\Profiles\, thats also where the YAR_Kickstart.xml file is actually generated/created.


Overall I think this plugin is working excellently despite the minor problems.. Nothing has gone wrong that I wouldn't consider a minor bump in the road of beta development. Keep up the great work.
 
YAR.webp
Code: 
See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidOperationException: Couldn?t register the hot key.
   at YetAnotherRelogger.Helpers.Tools.KeyboardHook.RegisterHotKey(ModifierKeys modifier, Keys key)
   at YetAnotherRelogger.Helpers.Hotkeys.GlobalHotkeys.Load()
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.296 (RTMGDR.030319-2900)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
YetAnotherRelogger
    Assembly Version: 0.0.0.5
    Win32 Version: 
    CodeBase: file:///C:/Soft/YetAnotherRelogger%20%5Bv0.1.9.2%5D/YetAnotherRelogger.exe
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.296 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.278 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.282 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.233 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
kvqjvhl3
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.296 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.233 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
 
Last edited:
Is anyone successfully using the randomization in the profile scheduler?

I've added three profiles but it isn't alterting. I've ticked off Randomize. What are your settings for kickstarter? Maybe that's the reason why it's not working
 
[2012-12-10 09:56:23] Relogger Thread Starting!
[2012-12-10 09:56:23] Yet Another Relogger Version 0.1.9.2
[2012-12-10 09:56:23] ## Loading Hotkeys ##
[2012-12-10 09:56:23] Register hotkey: Reposition - Control+R
[2012-12-10 09:56:23] Register hotkey: full screen - Control+F
[2012-12-10 09:56:26] <xxx> We are scheduled to start
[2012-12-10 09:56:26] <xxx> Next scheduled stop: 11-12 7:1
[2012-12-10 09:56:26] PingCheck: Ping -> Google
[2012-12-10 09:56:26] PingCheck: 173.194.35.180 -> 45ms
[2012-12-10 09:56:26] <xxx> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[2012-12-10 09:56:26] <xxx> Replacing D3Prefs for user: MattD3
[2012-12-10 09:56:26] <xxx> Copy custom D3Prefs file to: C:\Users\MattD3\Documents\Diablo III\D3Prefs.txt
[2012-12-10 09:56:26] <xxx> Failed to copy D3Prefs file: System.UnauthorizedAccessException: Odmowa dostępu do ścieżki ?C:\Users\MattD3\Documents\Diablo III\D3Prefs.txt?.
w System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
w System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)
w YetAnotherRelogger.Helpers.Bot.DiabloClass.D3Prefs()
Click to expand...

why D3Prefs file it's not working? anyone got it succesfully using custom D3prefs?


EDIT:
Ok it wasn't doing copy because of "read only" attribute I set..However now is doing proper copy of D3prefs, but is not using this parametres..I have MipBias "9.000000", hardware class 1 etc. and it's still not reducing graphic look :( anyone can help?
 
Last edited:
Mine isn't closing crash dialogs and relaunching game / db.

This was the primary reason I started using this program and was hoping it would be able to relaunch after crashes.

Is there a way to do it that I am missing? Same problem as person few posts back.
 
ANyone else having issues where it starts the bot up but doesn't load a profile? Resulting in DB telling us to load a profile before pressing start.
 
don't want to be annoying, but i'm keep waking up to 1 or 2 bots "stopped". Is there anyway we could fix this? when i press start it tries, then stops, then i press start again and it works
 
I cant get it to work as another user - it keep starting diablo in fullscreen mode and default prefs, however d3prefs for that user are fine and if I start diablo from this user using my old bat file everething is fine too.
 
Hi, I have been never able to set up YAR properly for some reason, tho i have took some time to look for different solutions.
My problem is that YAR will never input neither Bnet account name or password into the game.
Everytime i try to run YAR it will always end on this log after it has successfuly opened diablo and demonbuddy (with Error: no routine was selected) : [10/12/2012 17:10:51] <Jerry> Demonbuddy:7676: Waiting for demonbuddy to log into Diablo
I'm trying to understand how the log in process happens and i would appreciate if someone would correct me on my thoughts;
The diablo gets opened, 10 sec delay between dbuddy, dbuddy gets opened (but it needs RadsAtom plugin or something like that), so the plugin can pass the login information to diablo..
I mean why would u display log information "Waiting for demonbuddy to log into Diablo".. like it's the plugin responsible for passing the login information to diablo..
But then we got the settup in YAR where we pass all the login information...
Someone please get me out of this big misconfusion.

Here's my log as well..
 

Attachments

hmm what exactly do i have to do to run the game on a different win user account? created one but yar does not seem to start d3 on it

-edit- figured it out
 
Last edited:
REQUEST: could you make clicking "close" NOT close YAR but minimise to tray when the relevant boxes are ticked. clicking the X minimises like it should, but close outright closes YAR and can be annoying having to reload all my bots which are running as different win users

Thanks!!


Oink said:
hmm what exactly do i have to do to run the game on a different win user account? created one but yar does not seem to start d3 on it
Click to expand...

Make sure you're username and password are set correctly, it might help if you user is an admin, not sure but the account must have a password and not left blank.
on step 5/5 on the general tab within the bot creation wizard make sure the check box for "use specific windows user for this bot" is ticked and you've logged into the windows account at least once so it creates the file structure etc.

Apart from that, aslong as you're running YAR as an admin it should work perfectly fine.

adikillah said:
Hi, I have been never able to set up YAR properly for some reason, tho i have took some time to look for different solutions.
My problem is that YAR will never input neither Bnet account name or password into the game.
Everytime i try to run YAR it will always end on this log after it has successfuly opened diablo and demonbuddy (with Error: no routine was selected) : [10/12/2012 17:10:51] <Jerry> Demonbuddy:7676: Waiting for demonbuddy to log into Diablo
I'm trying to understand how the log in process happens and i would appreciate if someone would correct me on my thoughts;
The diablo gets opened, 10 sec delay between dbuddy, dbuddy gets opened (but it needs RadsAtom plugin or something like that), so the plugin can pass the login information to diablo..
I mean why would u display log information "Waiting for demonbuddy to log into Diablo".. like it's the plugin responsible for passing the login information to diablo..
But then we got the settup in YAR where we pass all the login information...
Someone please get me out of this big misconfusion.

Here's my log as well..
Click to expand...

Make sure you have RadsAtom installed in your plugin folder if thats what its waiting for, although this should only be relevant to loading the profile correctly and not anything to do with logging into d3.

The way the login information is passed is YAR will store the details and run Demonbuddy with the login details as arguments such as if you logged in via a shortcut it would look something like: demonbuddy.exe" -bnetaccount xxx -bnetpassword xxx
this is why YAR will say it is waiting for demonbuddy to deal with logging into d3.

I've had problems with demonbuddy not logging into d3 only when d3 is being run in fullscreen which stops the bot from being able to enter the user/pass. make sure youre running windowed/windowed(fullscreen)
 
Got this error in Demonbuddy when trying to start Diablo using ISBoxer and different users with newest YAR:



[20:26:38.496 N] Error attaching to Diablo III, Reason:System.Exception: Could not successfully set up_synchronization_events!
at Zeta.MemoryManagement.Executor.method_5()
at Zeta.MemoryManagement.Executor..ctor(ExternalProcessReader memory, IntPtr endscene)
at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)
Click to expand...

First bot which is on my main user account works normally, problem occurs when i try to use different user.

Is that becouse of ISBoxer or i did smth wrong?

Edit:
Ok it works without isBoxer , is that possible to fix it to work with ISBoxer?
 
Last edited:
Status
Not open for further replies.
Back
Top