[Beta] Demonbuddy daily beta builds

same for me! sometimes it will run for a very long time but it will always happen eventually.

 

To solve that just edit the GlobalSettings.xml at the Settings folder of DB.

Code:

<?xml version="1.0" encoding="utf-8"?>
<GlobalSettings>
  <LastProfile>C:\Users\YOUR_USER\DemonBuddyFolder\ProfilesFolder\Profile.xml</LastProfile>
  <LogLevel>Normal</LogLevel>
  <LoginKey>3M5H9M2J5V5Q8I6X3F4Y</LoginKey>
  <PluginsPath>Plugins</PluginsPath>
  [SIZE=6][B]<ReloadPluginsOnFileChange>true</ReloadPluginsOnFileChange>[/B][/SIZE]
  <CombatRoutinePath>Routines</CombatRoutinePath>
  [SIZE=6][B]<ReloadRoutinesOnFileChange>true</ReloadRoutinesOnFileChange>[/B][/SIZE]
  <FullInventoryHandling>Ignore</FullInventoryHandling>
  <DeathHandling>Ignore</DeathHandling>
  [SIZE=6][B]<KeepGameInForeground>true</KeepGameInForeground>[/B][/SIZE]
  <WindowLeft>998</WindowLeft>
  <WindowTop>424</WindowTop>
  <WindowWidth>595</WindowWidth>
  <WindowHeight>419</WindowHeight>
  <WindowState>Normal</WindowState>
  <RecentProfiles>
    <Recent Path="C:\Users\YOUR_USER\DemonBuddyFolder\ProfilesFolder\Profile.xml" Name="Profile" />
  </RecentProfiles>
  <LogoutInactivityTime>0</LogoutInactivityTime>
  <GameWaitTimeMin>2</GameWaitTimeMin>
  <GameWaitTimeMax>7</GameWaitTimeMax>
</GlobalSettings>

 

I use http://www.thebuddyforum.com/demonbuddy-forum/plugins/82535-standalone-yet-another-relogger.html relogger, and if i don't use it i will get night with out botting, because diablo 3 just crashes every NIGHT, only NIGHT, all day is fine, but NIGHT - crash:

Code:

[05.11.2012 20:20:02] Relogger Thread Starting!
[05.11.2012 20:20:02] Yet Another Relogger Version 0.0.0.3
[05.11.2012 20:20:04] <DB> We are scheduled to start
[05.11.2012 20:20:04] <DB> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[05.11.2012 20:20:04] <DB> Language set: English (Brittain) : enGB
[05.11.2012 20:20:04] <DB> Region set: Europe : eu.actual.battle.net
[05.11.2012 20:20:04] <DB> Diablo:3464: Waiting for process to become ready
[05.11.2012 20:20:12] <DB> Diablo:3464: Found D3 Main Window
[05.11.2012 20:20:12] <DB> Diablo:3464: Process is ready
[05.11.2012 20:20:12] <DB> Diablo III
[05.11.2012 20:20:14] <DB> Diablo:3464: Resizing window W:800 H:600
[05.11.2012 20:20:14] <DB> Diablo:3464: Moving window to X:0 Y:0
[05.11.2012 20:20:14] <DB> Diablo:3464: Process is ready
[05.11.2012 20:20:14] <DB> Current profile: "BigRed_START_HERE.xml" Runs:0 Time:0 mintues (C:\Users\Desktop\noForwardUnderbridge\noForwardUnderbridge\BigRed_START_HERE.xml)
[05.11.2012 20:20:14] <DB> Checking plugin: D:\Bot\DemonBuddy\Plugins\YAR\Plugin.cs
[05.11.2012 20:20:14] <DB> Plugin is installed and latest version
[05.11.2012 20:20:14] <DB> Demonbuddy:4632: Waiting for process to become ready
[05.11.2012 20:20:14] <DB> Demonbuddy:4632: Process is ready
[05.11.2012 20:20:15] <DB> Diablo:3464: has focus. Bring attached Demonbuddy to front
[05.11.2012 20:21:11] <DB> Diablo:3464: has focus. Bring attached Demonbuddy to front
[05.11.2012 20:27:08] <DB> Diablo:3464: has focus. Bring attached Demonbuddy to front
[05.11.2012 20:34:05] <DB> Diablo:3464: has focus. Bring attached Demonbuddy to front
[05.11.2012 20:34:45] <DB> Diablo:3464: has focus. Bring attached Demonbuddy to front
[05.11.2012 20:40:16] <DB> Diablo:3464: has focus. Bring attached Demonbuddy to front
[05.11.2012 20:42:11] <DB> Diablo:3464: has focus. Bring attached Demonbuddy to front
[05.11.2012 20:48:53] <DB> Diablo:3464: has focus. Bring attached Demonbuddy to front
[05.11.2012 20:50:56] <DB> Diablo:3464: has focus. Bring attached Demonbuddy to front
[05.11.2012 20:53:48] <DB> Diablo:3464: has focus. Bring attached Demonbuddy to front
[05.11.2012 20:54:10] <DB> Diablo:3464: has focus. Bring attached Demonbuddy to front
[05.11.2012 21:00:11] <DB> Diablo:3464: has focus. Bring attached Demonbuddy to front
[05.11.2012 21:00:21] <DB> Diablo:3464: has focus. Bring attached Demonbuddy to front
[05.11.2012 21:01:34] <DB> Diablo:3464: has focus. Bring attached Demonbuddy to front
[05.11.2012 21:30:13] <DB> Runs completed 1
[05.11.2012 22:05:44] <DB> Diablo:3464: Is unresponsive for more than 60 seconds
[05.11.2012 22:05:44] <DB> Diablo:3464: Killing process
[05.11.2012 22:05:45] <DB> Diablo:3464: Process is not running
[05.11.2012 22:05:45] <DB> Killing Agent.exe:1376
[05.11.2012 22:05:45] <DB> Language set: English (Brittain) : enGB
[05.11.2012 22:05:45] <DB> Region set: Europe : eu.actual.battle.net
[05.11.2012 22:05:45] <DB> Diablo:5100: Waiting for process to become ready
[05.11.2012 22:05:53] <DB> Diablo:5100: Found D3 Main Window
[05.11.2012 22:05:53] <DB> Diablo:5100: Process is ready
[05.11.2012 22:05:53] <DB> Diablo III
[05.11.2012 22:05:55] <DB> Diablo:5100: Resizing window W:800 H:600
[05.11.2012 22:05:55] <DB> Diablo:5100: Moving window to X:0 Y:0
[05.11.2012 22:05:55] <DB> Diablo:5100: Process is ready
[05.11.2012 22:05:55] <DB> Current profile: "BigRed_START_HERE.xml" Runs:0 Time:0 mintues (C:\Users\Desktop\noForwardUnderbridge\noForwardUnderbridge\BigRed_START_HERE.xml)
[05.11.2012 22:05:55] <DB> Checking plugin: D:\Bot\DemonBuddy\Plugins\YAR\Plugin.cs
[05.11.2012 22:05:55] <DB> Plugin is installed and latest version
[05.11.2012 22:05:55] <DB> Demonbuddy:3568: Waiting for process to become ready
[05.11.2012 22:05:55] <DB> Demonbuddy:3568: Process is ready
[05.11.2012 22:05:56] <DB> Diablo:5100: has focus. Bring attached Demonbuddy to front
[05.11.2012 22:21:17] <DB> Runs completed 1
[05.11.2012 23:16:19] <DB> Runs completed 2
[06.11.2012 0:25:04] <DB> Runs completed 3
[06.11.2012 1:30:49] <DB> Runs completed 4
[06.11.2012 2:35:50] <DB> Runs completed 5
[06.11.2012 3:47:19] <DB> Runs completed 6
[06.11.2012 4:50:41] <DB> Runs completed 7
[06.11.2012 5:34:51] <DB> Diablo:5100: Is unresponsive for more than 60 seconds
[06.11.2012 5:34:51] <DB> Diablo:5100: Killing process
[06.11.2012 5:34:52] <DB> Diablo:5100: Process is not running
[06.11.2012 5:34:52] <DB> Killing Agent.exe:4564
[06.11.2012 5:34:52] <DB> Language set: English (Brittain) : enGB
[06.11.2012 5:34:52] <DB> Region set: Europe : eu.actual.battle.net
[06.11.2012 5:34:52] <DB> Diablo:2660: Waiting for process to become ready
[06.11.2012 5:34:59] <DB> Diablo:2660: Found D3 Main Window
[06.11.2012 5:35:00] <DB> Diablo:2660: Process is ready
[06.11.2012 5:35:00] <DB> Diablo III
[06.11.2012 5:35:01] <DB> Diablo:2660: Resizing window W:800 H:600
[06.11.2012 5:35:01] <DB> Diablo:2660: Moving window to X:0 Y:0
[06.11.2012 5:35:01] <DB> Diablo:2660: Process is ready
[06.11.2012 5:35:01] <DB> Current profile: "BigRed_START_HERE.xml" Runs:0 Time:0 mintues (C:\Users\Desktop\noForwardUnderbridge\noForwardUnderbridge\BigRed_START_HERE.xml)
[06.11.2012 5:35:01] <DB> Checking plugin: D:\Bot\DemonBuddy\Plugins\YAR\Plugin.cs
[06.11.2012 5:35:01] <DB> Plugin is installed and latest version
[06.11.2012 5:35:01] <DB> Demonbuddy:1284: Waiting for process to become ready
[06.11.2012 5:35:01] <DB> Diablo:2660: has focus. Bring attached Demonbuddy to front
[06.11.2012 5:35:01] <DB> Demonbuddy:1284: Process is ready
[06.11.2012 6:03:25] <DB> Diablo:2660: has focus. Bring attached Demonbuddy to front
[06.11.2012 6:08:51] <DB> Diablo:2660: has focus. Bring attached Demonbuddy to front
[06.11.2012 6:09:22] <DB> Diablo:2660: has focus. Bring attached Demonbuddy to front
[06.11.2012 6:09:31] Closed!

see here:

Code:

[05.11.2012 22:05:44] <DB> Diablo:3464: Is unresponsive for more than 60 seconds
[05.11.2012 22:05:44] <DB> Diablo:3464: Killing process

and:

Code:

[06.11.2012 5:34:51] <DB> Diablo:5100: Is unresponsive for more than 60 seconds
[06.11.2012 5:34:51] <DB> Diablo:5100: Killing process

and this is on 70 beta, and 282 stable release too.

1-2 crashes per night, first crash already 3 NIGHT in a row starts in ~22:00, wtf? before i don't get any crash.

and here is db log:
View attachment 1284 2012-11-06 05.35.txt
View attachment 4632 2012-11-05 20.20.txt
View attachment 3568 2012-11-05 22.05.zip
please if you found why i got crashes help me.
also i test without plugins and too got crashes...

 

load profile with leave game still seems to have a weird error with reloading old profile on new game start, even with old profile already loaded

Code:

[20:09:59.123 N] Destruction Keys needed, running A1
[20:09:59.469 N] Loaded profile KeyHuntinn - A1 - Start
[20:09:59.469 N] Leaving game, reason: Profile loaded
[20:09:59.492 N] Last run acquired 28929 gold.
[20:10:04.493 N] Waiting 8.6 seconds before next game...
[20:10:13.147 N] Creating new game, Params: <Act:A1 Difficulty:Inferno Quest:72801 QuestStep:36 ResumeFromSave:False IsPrivate:True Handicap:1>
[20:10:19.733 N] GameChanged. Clearing actors
[20:10:19.822 N] ========== Grid segmentation resetting!!! ============
[20:10:19.823 N] Game joined, Reloading profile.
[20:10:20.109 N] Loaded profile KeyHuntinn - Act Picker
[20:10:20.176 N] Destruction Keys needed, running A1
[20:10:20.481 N] Loaded profile KeyHuntinn - A1 - Start
[20:10:20.481 N] Leaving game, reason: Profile loaded

 

exactly this happens everytime to me when inactivity is triggered, im only using trinity and yar.
i post no logs because atm yar is spamming the logs so hard it makes no sence i think.

i think u should force inacitivity situations and not wait if it happens a night or not or ) this is a real big issues for everyone without atom plugin
really need this fixed please

 

hey thanks for replying "'thelol"

I tried this but its not working,
Let me show you what i mean



It doesn't show the option to choose my pluggins.

Thanks again,

Yuart

 

It can be you do not notice it, as it takes place rarely enough.
I watch after it 15-20 clock in twenty-four hours and 3-5 it takes place one time per days, in the moment of recognition of things there is a break of connection, after re-executing and personage hides in this corner to the wearing-out of timer of inaction

Too same takes place and at 2х of my acquaintances.

[11:26:38.959 N] ========== Grid segmentation resetting!!! ============
[11:28:40.749 N] [GilesTrinity] No more space to pickup a 2-slot item, now running town-run routine.
[11:28:40.749 N] Using town portal
[11:28:46.865 N] Using town portal
[11:29:05.894 N] Closing error dialog
[11:29:08.991 N] Waiting 7.6 seconds before next game...


[11:21:51.442 N] ========== Grid segmentation resetting!!! ============
[11:24:56.101 N] No more space to pickup a 2-slot item, town-run requested at next free moment.
[11:24:57.989 N] Using town portal
[11:25:11.407 N] Closing error dialog
[11:25:13.659 N] Waiting 7 seconds before next game...

P.S.
4 clients, 12 o'clock of work.
Inactivity Time DemonbuddyBETA 1.0.1154.70 - 2
Inactivity Timer RadsAtom - 0
While works perfectly.

P.P.S.
I beg pardon for my google of translate...

 

I got the same problem, Db cannot "see" plugins and i cannot change settings.

Edit:
Fixed: You must login to Diablo then launch DB.

 

Bump!!!!

 

What about diablo 3 crashes? :/
http://www.thebuddyforum.com/demonb...-daily-beta-builds-post844917.html#post844917
and http://www.thebuddyforum.com/demonb...upport/84520-dunno-why-my-diablo-crashes.html

 

Nice!! Could you please just paste the change you made?? I am asking becouse my Trinity is customised to my needs and I do not want to mess it up
Thx. Great Job.!

 

Dude you rock. Thanks for taking the time to find and fix the issue when it didnt even reside in DB. Over and above dude.

 

OK found it:

Original:

Code:

            // If we aren't in the game of a world is loading, don't do anything yet
            if (!ZetaDia.IsInGame || ZetaDia.IsLoadingWorld)
            {
                return RunStatus.[COLOR="#FF0000"]Running[/COLOR];
            }

Nesox fix:

Code:

            // If we aren't in the game of a world is loading, don't do anything yet
            if (!ZetaDia.IsInGame || ZetaDia.IsLoadingWorld)
            {
                return RunStatus.[COLOR="#008000"]Success[/COLOR];
            }

Line 4825

Thx Nesox again!

 

lol, in this thread devs does not answer, i create thread in support forum:
http://www.thebuddyforum.com/demonbuddy-forum/demonbuddy-support/84571-diablo-3-crashes.html
and they closed thread AGAIN without answer, great support.

 

Exactly, this is what they mean when they talk about "exceeding expectations". Respect!

 

FINALLY (yes, it's a nerdgasm)!
Testing the Trinity changes, Nesox. If that works, I love you long time.

 

Thats it???? does it work?

 

Well. Testing now. But it is the only difference between original file and Nesox fix. Just read the If statement and it's clear why it should work

 

_ Great job Nesox ! Keep going, you are doing very well