[StandAlone] Yet Another Relogger!

[w4rr3n]

URGENT!!!

There is a huge problem with v. 0.1.8.5 BETA

Sometimes when starting D3s, YAR will take up ALOT of CPU & GPU usage. I start my D3s one by one, and I noticed that sometimes after loading one, my GPU-Z was saying my GPU load was 90%!!! I would hear my GPU fans spinning LOUDLY. So after noticing it, I stopped the D3, and the loads would drop down to normal numbers. Then I would start the D3 back and everything was fine. But it would happen again later on. It's an easy fix by just stopping it if it is increasing the loads. But if possible please fix it so it does not do this when starting D3s after it restarts it automatically. It would suck to have your GPU running at 100% while you're not at home to monitor it.

in all respect, giving such scenarios will not help. Need more info to determine the true problem. Also initial spike is normal, but I have not seen continuous spikes for a long time since 1.8.5

 

[Icaros]

Sinterklaas, thanks for your work on this. This is really functionality that Demonbuddy should include out of the box, and it's a real life saver once you have any more than one bot to deal with.

Something I'd love to see is more options/gui for resizing windows.
The basic functionality is there, but it's currently fairly buried.

For example, if I resize my windows to 320x240, but want to check/mule from a bot, the current process is:
-click on window frame to have it resize up to 800x600
-Do what you need to in Diablo
-go to the settings panel, and into auto-position and click "reposition now"
-repeat for remaining bots

It would be great to see resizing options in the right click menu of each bot, and the window position button on the main panel.
Then it would almost function like ISBoxer, having one window as large focus, while all others are small and having the ability to cycle through the focused process.

It would also be great if unchecking "cascade windows" in auto position would tile the windows instead. Currently they all stack on top of each other.

Also curious, what is the "Force Working Area" option for? And is it intentional that the Demonbuddy auto-position options are greyed out?

Keep up the great work

 

[Njoda]

The biggest issue atm is the fact that often when returning after being away, some of your bots are "Stopped" - not "Scheduled stop". This basically means it wont start until you manually start it, and that defeats the very purpose of even having a relogger..

I got this to.

any fix?

 

[sinterlkaas]

Sinterklass, would be very cool if you could add some support for launching with different user keys:

http://www.thebuddyforum.com/demonb...2-starting-diablo-style-unique-client-id.html

Any possible way to implement this?
Would be very, very greatful and keep up the handsome donations
Cheers!

I am working on it already added a option to start Diablo with a different user

when will fix the 3 times relog and stuck problem?? this is really This thing really bothers me

URGENT!!!

There is a huge problem with v. 0.1.8.5 BETA

Sometimes when starting D3s, YAR will take up ALOT of CPU & GPU usage. I start my D3s one by one, and I noticed that sometimes after loading one, my GPU-Z was saying my GPU load was 90%!!! I would hear my GPU fans spinning LOUDLY. So after noticing it, I stopped the D3, and the loads would drop down to normal numbers. Then I would start the D3 back and everything was fine. But it would happen again later on. It's an easy fix by just stopping it if it is increasing the loads. But if possible please fix it so it does not do this when starting D3s after it restarts it automatically. It would suck to have your GPU running at 100% while you're not at home to monitor it.

I can not change anything about GPU load as for CPU load I already did some improvements and according to warren the CPU usage is much better in current 0.1.9.1 on github
and like warren also said the way you ask me to fix it is not going to help at all where is the information ? and ofc when you close all Diablos there will be no processes that use your CPU so it will drop ... if you rely on this to happen just untick some green blocks in your schedule to make this happen and you wont have the major CPU GPU load build up...

Sinterklaas, thanks for your work on this. This is really functionality that Demonbuddy should include out of the box, and it's a real life saver once you have any more than one bot to deal with.

Something I'd love to see is more options/gui for resizing windows.
The basic functionality is there, but it's currently fairly buried.

For example, if I resize my windows to 320x240, but want to check/mule from a bot, the current process is:
-click on window frame to have it resize up to 800x600
-Do what you need to in Diablo
-go to the settings panel, and into auto-position and click "reposition now"
-repeat for remaining bots

It would be great to see resizing options in the right click menu of each bot, and the window position button on the main panel.
Then it would almost function like ISBoxer, having one window as large focus, while all others are small and having the ability to cycle through the focused process.
It would also be great if unchecking "cascade windows" in auto position would tile the windows instead. Currently they all stack on top of each other.
Also curious, what is the "Force Working Area" option for? And is it intentional that the Demonbuddy auto-position options are greyed out?
Keep up the great work

Yes there will be more options for resizing.. Now it is incomplete and only functional for Diablo due to lack of time and other priorities I prefer to first fix those before I try to make more eye candy changes
if options are grayed out they are disabled or not in use yet

 

[ethanbryan]

i didnt see your reply about my question of "when will fix the 3 times relog and stuck problem?? this is really This thing really bothers me"

am i miss it? thanks

 

[Njoda]

So can you fix the problem where you have to start it again?
it can run for hours fine, suddenly its closed and i have to press start again :0

 

[sinterlkaas]

i didnt see your reply about my question of "when will fix the 3 times relog and stuck problem?? this is really This thing really bothers me"
am i miss it? thanks

So can you fix the problem where you have to start it again?
it can run for hours fine, suddenly its closed and i have to press start again :0

Ah yes sorry I will push current Github version as a release on forums the buddy auth should be fixed and 3 times login is still there but in a improved way I will make a new system for this but today I am busy with family visits

 

[sinterlkaas]

Update Version: 0.1.9.2

Version: 0.1.9.2 BETA

• Fixed diablo region selection when using multiple diablos on different regions and languages
• Fixed Random profile schedule not always selection the right profile
• Fixed BuddyAuth Session killer
• Added Monsterpower selection in profile schedule
• Added Advanced settings to launch diablo as a different windows user
  * Remove window frame wont be working anymore when process is launched as a different user

 

[Geckoz]

OH MY GOD!

If those fixes actually work, and I trust that they do, then - OMG

Thank you!

About the ability to run as a different user, is the purpose here that it uses another ID from the registry then? Or is it actually possible through having several users logged in, to run a *** on each of them, that connects to different IPs?

 

[Caxep]

Go to Settings folder, and open Bots.xml and change the part

[COLOR="#0000FF"]<CombatRoutine>[/COLOR][COLOR="#000000"]GilesPlugin[/COLOR][COLOR="#0000FF"]</CombatRoutine>[/COLOR]

to

[COLOR="#0000FF"]<CombatRoutine>[/COLOR][COLOR="#000000"]Trinity[/COLOR][COLOR="#0000FF"]</CombatRoutine>[/COLOR]

YAR replace this to old routine.

I have done differently. Just renamed "TrinityRoutine" folder into "Generic", "TrinityRoutine.cs" file into "GenericRoutine.cs" and in this file changed string "public override string Name { get { return "Trinity"; } }" to "public override string Name { get { return "Generic"; } }"

 

[satan2004]

God you are good! you should be employed by the Demonbuddy team!

but it still doesnt say Trinity in the combat routine option? since they updated with giles being gone

 

[sinterlkaas]

God you are good! you should be employed by the Demonbuddy team!

but it still doesnt say Trinity in the combat routine option? since they updated with giles being gone

It is now possible to just enter a custom name this should no longer crash the relogger

 

[Nostran]

Doesn't seem to work?

EDIT: Another issue:

[09.12.2012 12:32:29] Relogger Crashed! with message Thread was being aborted.
[09.12.2012 12:32:29] at System.Threading.Monitor.Enter(Object obj)
at System.Configuration.ApplicationSettingsBase.get_Item(String propertyName)
at YetAnotherRelogger.Helpers.ConnectionCheck.get_IsConnected()
at YetAnotherRelogger.Relogger.ReloggerWorker()
[09.12.2012 12:32:29] Waiting 10 seconds and try again!
[09.12.2012 12:32:39] Relogger Crashed! with message Thread was being aborted.
[09.12.2012 12:32:39] at System.Threading.Monitor.Enter(Object obj)
at System.Configuration.ApplicationSettingsBase.get_Item(String propertyName)
at YetAnotherRelogger.Helpers.ConnectionCheck.get_IsConnected()
at YetAnotherRelogger.Relogger.ReloggerWorker()
[09.12.2012 12:32:39] Waiting 10 seconds and try again!

 

[nagag]

hi thx for the awesome relogger . i find out the latest version support Blizzard authenticator . but the authenticator part is grey . i can't edit it . Please help

 

[Njoda]

It is now possible to just enter a custom name this should no longer crash the relogger

Did just dl your new.

well i cant put in a custom routine name?

 

[tesslerc]

sinkerlaas can you make it randomize the seconds when it closes D3 and DB?
it closes always on 00 seconds.
Launch has a delay for DB and has a delay until logged in so that is ok.

Also if it fails for 3 times in a row it just stops, so if internet is down for 1 hour and you aren't home for 12h - it won't auto start again.
I would set a delay for 1h until retrying again - that way it shouldn't hog the server incase of downtime.

 

[jackus]

Sinterlkaas
I use your relogger version 0.1.8.5 beta. And it is the best relogger there is! I use it with Giles Trinity version 1.6.3.4. The one he made before he use Rouge Vanish.

But the Trinity Community Edition 1.7.1.6 is better. But when I use your relogger with 1.7.1.6 DB uses 20-30% of my CPU!!! Do I have to remove your old Plugin and let YAR make a new plugin? Or does YAR not support the new version of Trinity?

Thank you for doing this

Keep up the good work

 

[codenamebob]

For all guys who use Trinity Routines like me
Go to Demonbuddy Routine path ...TrinityRoutine\TrinityRoutine.cs edit it with notepad
find " { get { return "Trinity"; } } " change to " { get { return "GilesPlugin"; } } " then save
open YAR select GilesPlugin as Combat routine

it works fine for me, sorry for my poor English

 

[amik]

Maybe it's me, but does anyone notice lower ticks/s in DB after updating?

 

[rbrinks]

new update works like D3Loader? Changing the Unique ID of diablo each windows user?