• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • [StandAlone] Yet Another Relogger!

    Discussion in 'Archives' started by sinterlkaas, Oct 30, 2012.

    Thread Status:
    Not open for further replies.
    1. jackus

      jackus New Member

      Joined:
      Sep 4, 2012
      Messages:
      428
      Likes Received:
      0
      Trophy Points:
      0
      for some weird reason.. all my DB was set to Enable TPS [1]
       
    2. Nostran

      Nostran New Member

      Joined:
      Jul 22, 2011
      Messages:
      229
      Likes Received:
      0
      Trophy Points:
      0
      Has anyone gotten the session killer to work?
       
    3. amik

      amik New Member

      Joined:
      Oct 18, 2012
      Messages:
      9
      Likes Received:
      0
      Trophy Points:
      1
      Nevermind, somehow the fps got limited with D3Prefs, reducing ticks/s
       
    4. Immortality

      Immortality New Member

      Joined:
      Oct 22, 2012
      Messages:
      55
      Likes Received:
      0
      Trophy Points:
      0
      nvm
       
      Last edited: Dec 9, 2012
    5. jarrish

      jarrish New Member

      Joined:
      Jul 29, 2012
      Messages:
      33
      Likes Received:
      0
      Trophy Points:
      0
      Argh still can't start DB with other winuser (admin account). The requested operation requires elevation sh*t again......
      Diablo starts fine.
       
    6. flyingyan

      flyingyan Member

      Joined:
      Sep 28, 2012
      Messages:
      95
      Likes Received:
      3
      Trophy Points:
      8
      Great job. It works fine. But I have a problem, may be a bug?. The bot is running with no mistake, but sometimes the unresponsive time exceed 60 seconds, and then the game have to restart. I have used your "antiIdle" plugins and I set the frozen time to 300 seconds could solve this problem. Hope we could set this idle number in your next version.

      [2012/12/10 2:38:44] <Dwight Chandler> Diablo:1584: Is unresponsive for more than 60 seconds
      [2012/12/10 2:38:44] <Dwight Chandler> Diablo:1584: Killing process
      [2012/12/10 2:38:44] <Dwight Chandler> Diablo:1584: Process is not running
      [2012/12/10 2:38:44] <Dwight Chandler> Demonbuddy:3624: Closing db
      [2012/12/10 2:38:44] <Dwight Chandler> Demonbuddy:3624: Waiting to close
      [2012/12/10 2:38:47] <Dwight Chandler> Demonbuddy:3624: Closed.
       
      Last edited: Dec 9, 2012
    7. Wycleff

      Wycleff New Member

      Joined:
      Dec 1, 2012
      Messages:
      5
      Likes Received:
      0
      Trophy Points:
      0
      Yeah, Now the Profile Randomizer works good !
       
    8. DemonSexu

      DemonSexu New Member

      Joined:
      Aug 31, 2012
      Messages:
      61
      Likes Received:
      0
      Trophy Points:
      0
      Failed to load profile: Element Continue is not supported. Please check your XML and try again. (<Continue profile="02_Core.xml" />) Line 12 While trying to run Alkaizer Run 2.99.1 RC or .2 ... any help ?
       
    9. w4rr3n

      w4rr3n New Member

      Joined:
      Aug 21, 2012
      Messages:
      107
      Likes Received:
      0
      Trophy Points:
      0
      i have no idea what profile is that but I'm pretty sure its a plugin/DB problem check that you have the plugin required for that profile
       
    10. DemonSexu

      DemonSexu New Member

      Joined:
      Aug 31, 2012
      Messages:
      61
      Likes Received:
      0
      Trophy Points:
      0
    11. carguy

      carguy Member

      Joined:
      Jan 21, 2010
      Messages:
      573
      Likes Received:
      7
      Trophy Points:
      18
      I've already suggested the throttled relogger tess, he's working on it.

      As for the the randomize close db....It doesn't matter on the SECONDS. Yar doesn't simply logout...it kills the said D3 process. Meaning depending on your internet connection, and blizzards, you'll log out at a random timestamp anyway. Not to mention, not everyone's pc time is 100% synced with what their servers are either. So what is 1:29 for you, might end up being 1:28:32 for them.

      So, while yar has the command to close on exactly say 1:30, realistically what blizzard sees is going to random anyway.
       
      Last edited: Dec 9, 2012
    12. Geckoz

      Geckoz Member

      Joined:
      Aug 25, 2012
      Messages:
      157
      Likes Received:
      0
      Trophy Points:
      16
      Is there a difference between MP0 and Disabled in the profile management screen?
       
    13. sinterlkaas

      sinterlkaas New Member

      Joined:
      Jan 17, 2012
      Messages:
      536
      Likes Received:
      14
      Trophy Points:
      0
      It is not exact the same I did not add any linking for D3 stuff I will later

      This is a DB issue when using -autostart for db launch arguments .. try enabling Kickstart this should fix the problem

      the difference between MP0 and disabled is that MP0 will set the MP to Level 0 and disabled simply does nothing about MP and will use DB default settings
       
    14. Geckoz

      Geckoz Member

      Joined:
      Aug 25, 2012
      Messages:
      157
      Likes Received:
      0
      Trophy Points:
      16
      So I guess that means you can have Monster Power off in the in-game options, and YAR can enable it for you. Thats nice!
       
    15. Nostran

      Nostran New Member

      Joined:
      Jul 22, 2011
      Messages:
      229
      Likes Received:
      0
      Trophy Points:
      0
      Any ETA on Session Killer fix?
       
    16. Geckoz

      Geckoz Member

      Joined:
      Aug 25, 2012
      Messages:
      157
      Likes Received:
      0
      Trophy Points:
      16
      Sinterlklaas, I tried your user account option and it's working straight away. Is the purpose of it to get different registry IDs on the different sessions?

      Is it possible to use my *** with it somehow, or does it not actually log into the new user account?
       
    17. lolwatpear

      lolwatpear New Member

      Joined:
      Jun 13, 2012
      Messages:
      245
      Likes Received:
      0
      Trophy Points:
      0
      I have a set of a3 profiles set to mp 0, yet it says "[18:15:05.315 N] [YetAnotherRelogger] Recieved MonsterPowerLevel: 1"

      I do have a1 and a2 set to mp 1 though. Anyone having this problem?
       
    18. Geckoz

      Geckoz Member

      Joined:
      Aug 25, 2012
      Messages:
      157
      Likes Received:
      0
      Trophy Points:
      16
      Im having an issue where it doesnt actually pick between the different profiles Ive set up. Just keeps doing act1..
       
    19. barbarian6

      barbarian6 New Member

      Joined:
      Nov 28, 2012
      Messages:
      209
      Likes Received:
      0
      Trophy Points:
      0
      Windows user selection works great...However, it doesn't recognize D3prefs files...It runs all bots on defaults settings and can't make it run with higher MipBias...any way to fix it?
      also, once we set some key shortcuts, when we close and program again, they doesn't work.I have to edit them, click save and then they work...until i close the program and run again.
       
    20. aqh

      aqh Member

      Joined:
      Dec 11, 2011
      Messages:
      711
      Likes Received:
      0
      Trophy Points:
      16
      Hi there!

      I just installed YAR and so far i'm impressed :)

      Is there any way to disable the auto-focus the DB when the D3 is in focus?

      Code:
       
      
      [10-12-2012 02:03:36] <Bot 1> Diablo:10080: has focus. Bring attached Demonbuddy to front
      [10-12-2012 02:03:39] <Bot 1> Failed to bring Demonbuddy to fron
      [10-12-2012 02:03:42] <Bot 1> Diablo:10080: has focus. Bring attached Demonbuddy to front
      [10-12-2012 02:05:02] <Bot 1> Diablo:10080: has focus. Bring attached Demonbuddy to front
      [10-12-2012 02:05:05] <Bot 1> Failed to bring Demonbuddy to fron
      [10-12-2012 02:05:56] <Bot 1> Diablo:10080: has focus. Bring attached Demonbuddy to front
      [10-12-2012 02:05:59] <Bot 1> Failed to bring Demonbuddy to fron
      [10-12-2012 02:11:26] <Bot 1> Diablo:10080: has focus. Bring attached Demonbuddy to front
      [10-12-2012 02:11:29] <Bot 1> Failed to bring Demonbuddy to fron
      
       
      Last edited: Dec 9, 2012
    Thread Status:
    Not open for further replies.

    Share This Page