Error message when DB creates a new game.

[Awe]

Hello. I've noticed with my bots, every time DB creates a new game, it tries to reload the same game again even though it's already in the game. This causes an error message (attached). The profile continues to run normally after the error message is closed. This error only happens upon starting a new game. Between profiles within the same game is Ok. Logs are attached, and here is the offending lines from the logs:

[05:57:29.748 N] Waiting 7.5 seconds before next game...
[05:57:37.354 N] Creating new game, Params: <Act:A1 Difficulty:Inferno Quest:72801 QuestStep:36 ResumeFromSave:False IsPrivate:True Handicap:0>
[05:57:38.864 N] Waiting 11.1 seconds before next game...
...
[05:57:49.984 N] Creating new game, Params: <Act:A1 Difficulty:Inferno Quest:72801 QuestStep:36 ResumeFromSave:False IsPrivate:True Handicap:0>
[05:57:51.746 D] Replaced hook [ProfileOrderBehavior_Hook] d3cc3206-e45b-4c71-9bf1-1b7d10ee43ad
[05:57:51.750 N] Closing error dialog


I've tried versions 294,295 and BETA 140. I've tried many profiles from this forum - A1 Champion, A3 Champion, gnome, tinnakiazer etc all produce the same error.
Any help is appreciated.

 

[CodenameG]

are you sure your following all the requirements to run the profile your trying to run, most profiles at the very least require Trinity be installed. make sure you read though the thread where you got the profile.

 

[Awe]

Yes I've been using Trinity. I've tried versions from 1.6.3.4, 1.7.1.9 thru to 1.7.1.16 - doesn't make any difference.

For the purposes of logging this problem in the support thread I've followed the guide which recommends removing all plugins, which I have and the problem still occurs.

 

[CodenameG]

install the latest version of trinity and whatever else the profile maker requires, and give it another shot, if your still having issues then upload a new log as an attachment.

 

[Awe]

Thanks for your help with this.

I've tested rrrix Act 3 profile for this test. Trinity 1.7.1.14 and Quest Tool 1.2.0 used with DB 295.
After starting fresh, the problem of double starting was gone. I then set out to uncover why I was receiving the error on my other builds. And i think I've found it.

I've been able to replicate the problem by starting 1 toon on the US server, and the same toon on the EU server. Other threads had mentioned you can bot the same toon on both servers simultaneously.
I started the D3 instances using D3Starter, and using the same DB directory (different DB directories still cause the same problem).
The first DB is Ok and doesn't double start. The second DB however has this issue. I have attached logs of both DB's as evidence.

Hopefully someone else can replicate this problem as well, or is it just me?

 

[Tony]

first of all you have to read the requirements (if there are any) on profile's thread for the profile to run

some profiles need a plugin or more in order to work

also on multiprofiles(profile that got more than one subprofile) you must load on DB the "Start Here" part



about Trinity now

in case Trinity is required for the profile(some profiles are made to work with Trinity only) you have to use,if it not required its up to you to use it or not



now,if you decide to use Trinity,you have to use Trinity's combat routine as well


in any case the quest step and the difficulty for the profile you are trying to use must be unlocked


also you must use the latest and most updated versions of everything (plugin,profile,DB)


so,let me know how it goes

 

[Awe]

Ok so I've used Trinity 1.7.1.16 and Quest Tools 1.2.0 and DB Beta 140. I'm still using profile rrrix Act3, GilesPlugin combat routine, and yes the toon on both servers has completed the game in Inferno and can play in all areas.

I can still replicate the issue, however this time there are extra lines of error messages in the logs for memory read errors just after creating the first game.

Remember this error doesn't stop the toon from playing - the error message is flashed on the screen very quickly and the profile continues to run as normal. Unless you were looking at the screen at that split second you wouldn't notice it.

 

[Tony]

you mean in game errors?

 

[Awe]

When the double start occurs, once the "first" start has logged in the toon into the game, the "second" start kicks in after x seconds. When this happens, you see the error message in game (uploaded pic in first post).

[05:57:29.748 N] Waiting 7.5 seconds before next game... OK
[05:57:37.354 N] Creating new game, Params: <Act:A1 Difficulty:Inferno Quest:72801 QuestStep:36 ResumeFromSave:False IsPrivate:True Handicap:0> First start - OK
[05:57:38.864 N] Waiting 11.1 seconds before next game... PROBLEM
... Waiting 11.1 seconds
[05:57:49.984 N] Creating new game, Params: <Act:A1 Difficulty:Inferno Quest:72801 QuestStep:36 ResumeFromSave:False IsPrivate:True Handicap:0> Second start - PROBLEM
[05:57:51.746 D] Replaced hook [ProfileOrderBehavior_Hook] d3cc3206-e45b-4c71-9bf1-1b7d10ee43ad
[05:57:51.750 N] Closing error dialog ERROR MESSAGE IN GAME

 

[Tony]

the are many reasons for an error to pop,including lag
if it doesnt make DB to stop you are ok

 

[Awe]

the are many reasons for an error to pop,including lag
if it doesnt make DB to stop you are ok

Hi Tony. I've tested this phenomenon over and over and it only occurs when I run the same toon on the US and EU servers simultaneously. If I only run the toon on either server, there's no problem.

If I only experience the problem when playing on both servers, this must mean my setup is correct and something is wrong with DB? Can you please test this out on your rig and advise if you experience the same thing?

I know you're saying don't worry about it, but the error message occurs when starting a new game which could flag blizz...

 

[iCKR]

Hi Tony. I've tested this phenomenon over and over and it only occurs when I run the same toon on the US and EU servers simultaneously. If I only run the toon on either server, there's no problem.

If I only experience the problem when playing on both servers, this must mean my setup is correct and something is wrong with DB? Can you please test this out on your rig and advise if you experience the same thing?

I know you're saying don't worry about it, but the error message occurs when starting a new game which could flag blizz...

relax, I've been botting through error messages and my 8 toons have not once gotten banned. Initially, yes ofcourse i was like you. But I highly doubt blizzard flags users out like that.

However, on a side note, i've not been able to replicate your error.

 

[Awe]

Thanks for checking jonckr. Always helps to get a second opinion

Cheers.