[Profile] Brutal Key Farm

rabasack · Nov 7, 2014

error again

Exception during bot tick.System.Exception: Process must have frozen or gotten out of sync: InjectionFinishedEvent_was_never_fired
at GreyMagic.Executor.WaitForInjection(Int32 timeout)
at GreyMagic.Executor.Execute(Int32 timeout)
at GreyMagic.Executor.GrabFrame()
at GreyMagic.ExternalProcessMemory.AcquireFrame(Boolean isHardLock)
at Zeta.Bot.BotMain.()

help me pls :/

FrankNStein · Nov 7, 2014

After another session of key runs results are like this:

Code:

[Keys] Counts: 
           Act 1 => 37 
           Act 2 => 29
           Act 3 => 36
           Act 4 => 38
[Keys] Stats:
           LF => 20,3
           LQ => 30,8
           M => 36,5
           UQ => 37,8
           UF => 48,3
           IQR => 7

Within those approx. 9 hours difference highest/lowest key count went down from 19 to 9. Looks kinda like a success story to me - even though it's not perfectly leveling key counts. But well, that was to be expected by something as simple as this

.

I had changed another thing I didn't mention yet (sry

): I commented out the <Shuffle> tag surrounding the act orders alongside changing the condition tag. Reason is more than one time I noticed DB logging it would only skip one act 'cause of above-median key count but then went forth only doing two out of three remaining acts before restarting the game

. Commenting out said tag solved that 'issue'.

Right now I'll go back to KeyAboveMedian(keyActorID) function and leave that <Shuffle> tag unused to see what happens now.

[Edit:]
After another session with KeyAboveMedian(keyActorID) and without Shuffle tag results are as follows:

Code:

[Keys] Counts: 
           Act 1 => 49 
           Act 2 => 46
           Act 3 => 49
           Act 4 => 49
[Keys] Stats:
           LF => 43,4
           LQ => 46,8
           M => 49
           UQ => 49
           UF => 52,4
           IQR => 2,3

Obviously KeyAboveMedian(keyActorID) does a better job at leveling those key counts than the other function. No surprise here, as this statistics function offers more control over act runs.

Yet disabling the Shuffle tag seems to help with these "early leaving game" situation mentioned earlier and results in longer runs and a more evenly distributed key count across acts and wardens. At least it seems to be that way. In the next step I will put the Shuffle tag back in (a.k.a. official profile

) and see if the key counts diverge again.

Anyhow: I would definitely like to see new results from people who posted their stats with large spreads between key counts until now AFTER they disabled the Shuffle tag for their runs to verify my impression.

kililin · Nov 7, 2014

FrankNStein said:
After another session of key runs results are like this:

Code:

[Keys] Counts: Act 1 => 37 Act 2 => 29 Act 3 => 36 Act 4 => 38 [Keys] Stats: LF => 20,3 LQ => 30,8 M => 36,5 UQ => 37,8 UF => 48,3 IQR => 7

Within those approx. 9 hours difference highest/lowest key count went down from 19 to 9. Looks kinda like a success story to me - even though it's not perfectly leveling key counts. But well, that was to be expected by something as simple as this .

I had changed another thing I didn't mention yet (sry ): I commented out the <Shuffle> tag surrounding the act orders alongside changing the condition tag. Reason is more than one time I noticed DB logging it would only skip one act 'cause of above-median key count but then went forth only doing two out of three remaining acts before restarting the game . Commenting out said tag solved that 'issue'.

Right now I'll go back to KeyAboveMedian(keyActorID) function and leave that <Shuffle> tag unused to see what happens now.

[Edit:]
After another session with KeyAboveMedian(keyActorID) and without Shuffle tag results are as follows:

Code:

[Keys] Counts: Act 1 => 49 Act 2 => 46 Act 3 => 49 Act 4 => 49 [Keys] Stats: LF => 43,4 LQ => 46,8 M => 49 UQ => 49 UF => 52,4 IQR => 2,3

Obviously KeyAboveMedian(keyActorID) does a better job at leveling those key counts than the other function. No surprise here, as this statistics function offers more control over act runs.

Yet disabling the Shuffle tag seems to help with these "early leaving game" situation mentioned earlier and results in longer runs and a more evenly distributed key count across acts and wardens. At least it seems to be that way. In the next step I will put the Shuffle tag back in (a.k.a. official profile ) and see if the key counts diverge again.

Anyhow: I would definitely like to see new results from people who posted their stats with large spreads between key counts until now AFTER they disabled the Shuffle tag for their runs to verify my impression.

Oh, thanks man! How can i disable "Shuffle" tag? And, "KeyAboveMedian" or "HighestKeyCountId" ? Thanks again..

xzjv · Nov 7, 2014

FrankNStein said:
After another session of key runs results are like this:
Obviously KeyAboveMedian(keyActorID) does a better job at leveling those key counts than the other function. No surprise here, as this statistics function offers more control over act runs.

Yet disabling the Shuffle tag seems to help with these "early leaving game" situation mentioned earlier and results in longer runs and a more evenly distributed key count across acts and wardens. At least it seems to be that way. In the next step I will put the Shuffle tag back in (a.k.a. official profile ) and see if the key counts diverge again.

Anyhow: I would definitely like to see new results from people who posted their stats with large spreads between key counts until now AFTER they disabled the Shuffle tag for their runs to verify my impression.

Its possible that shuffle is interfering in some way, ShuffleTag randomizes the tags inside it, but should only effect the direct children. Not particularly useful for this profile but i wrote it mostly for bounty split farming - where u want each bot working on a different bounty.

Attached is the version i've been running if you wanna try it. You'll need latest QT off git.

xzjv · Nov 7, 2014

MadMayhem said:
Seems to have good results, but does anyone else have a problem with constantly getting stuck in the Oasis? It seems like I get stuck there before finding the warden more often then I don't.

1.10 should be a lot better about that, i added a tag called RandomMove to shunt the bot off the waypoint into a better position. it doesn't use navigation/path-finding so it shouldn't get stuck; but a couple of the following SafeMoveTos take the bot back over the waypoint again so its not 100%.

kililin · Nov 8, 2014

Db(Beta or release) is not recognizing latest QT from git.. =/

fuganator · Nov 8, 2014

Loaded profile Zerg BKF Loader
[Trinity] Not in game, gold inactivity reset
Waiting 6.4 seconds before next game...
Creating new game. Params: [Act: OpenWorld, Difficulty: Torment6, Quest: -1, QuestStep: -1, ResumeFromSave: False, IsPrivate: True]
[Trinity] New Game - resetting everything
[Trinity] New Game, resetting Gold Inactivity Timer
Joined a game!
[Trinity] New Game - resetting everything
[Trinity] New Game, resetting Gold Inactivity Timer
Loaded profile Zerg BKF Loader
Game joined, Resetting profile caches.
[QuestTools][GridRoute] Generated new Weighted Nearest Minimap Unvisited Route with 23 nodes in 5ms
[QuestTools][ProfileSettingTag] Setting Condition=KeyMode to Zerg
Failed to load profile: Element RandomMove is not supported. Please check your XML and try again. (<RandomMove radius="60" />) Line 323
System.Exception: Element RandomMove is not supported. Please check your XML and try again. (<RandomMove radius="60" />) Line 323
at ..(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at ..(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at ..(XElement , Type )
at ...(XElement )
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at ..(XElement , PropertyInfo )
at ..(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at Zeta.Bot.Profile.Profile.Load(XElement element, String path)
at Zeta.Bot.Profile.Profile.Load(String path)
at Zeta.Bot.ProfileManager.Load(String profilePath, Boolean rememberPath)
Profile completed
Number of games completed: 23
Failed to load profile: Element RandomMove is not supported. Please check your XML and try again. (<RandomMove radius="60" />) Line 323
System.Exception: Element RandomMove is not supported. Please check your XML and try again. (<RandomMove radius="60" />) Line 323
at ..(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at ..(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at ..(XElement , Type )
at ...(XElement )
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at ..(XElement , PropertyInfo )
at ..(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at Zeta.Bot.Profile.Profile.Load(XElement element, String path)
at Zeta.Bot.Profile.Profile.Load(String path)
at Zeta.Bot.ProfileManager.Load(String profilePath, Boolean rememberPath)
Failed to load profile: Element RandomMove is not supported. Please check your XML and try again. (<RandomMove radius="60" />) Line 323
System.Exception: Element RandomMove is not supported. Please check your XML and try again. (<RandomMove radius="60" />) Line 323
at ..(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at ..(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at ..(XElement , Type )
at ...(XElement )
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at ..(XElement , PropertyInfo )
at ..(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at Zeta.Bot.Profile.Profile.Load(XElement element, String path)
at Zeta.Bot.Profile.Profile.Load(String path)
at Zeta.Bot.ProfileManager.Load(String profilePath, Boolean rememberPath)

And it keeps repeating.....this is with 1.10

xzjv · Nov 8, 2014

fuganator said:
Failed to load profile: Element RandomMove is not supported.

Yeah because u need latest QT from a GIT like i said.

go here https://www.assembla.com/code/questtools/git/nodes and click the download link on the right side

kililin said:
Db(Beta or release) is not recognizing latest QT from git.. =/

strange, i just tested it with .496 and .497

kililin · Nov 8, 2014

xzjv said:
Yeah because u need latest QT from a GIT like i said.

go here https://www.assembla.com/code/questtools/git/nodes and click the download link on the right side

Yeap, i did it. And QT do not appear in Db (Beta or Release)...

Sorry for my english..

EDIT:
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\Helpers\ActorHistory.cs(10,7) : warning CS0105: A diretiva using para 'Zeta.Common' apareceu anteriormente neste namespace
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\Helpers\ActorHistory.cs(11,7) : warning CS0105: A diretiva using para 'Zeta.Game' apareceu anteriormente neste namespace
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\Helpers\BotEvents.cs(111,26) : error CS0117: 'QuestTools.Helpers.ProfileUtils' não contém uma definição para 'ReplaceDefaultTags'
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\Helpers\ItemManager.cs(127,30) : warning CS0168: A variável 'ex' está declarada mas nunca foi usada
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\ProfileTags\CombatSettingTag.cs(88,34) : warning CS1998: Este método assíncrono não possui operadores 'await' e será executado de modo síncrono. É recomendável o uso do operador 'await' para aguardar chamadas à API desbloqueadas ou do operador 'await Task.Run(...)' para realizar um trabalho associado à CPU em um thread em segundo plano.
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\ProfileTags\ExploreDungeonTag.cs(556,34) : warning CS1998: Este método assíncrono não possui operadores 'await' e será executado de modo síncrono. É recomendável o uso do operador 'await' para aguardar chamadas à API desbloqueadas ou do operador 'await Task.Run(...)' para realizar um trabalho associado à CPU em um thread em segundo plano.
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\ProfileTags\QTOpenRiftWrapperTag.cs(118,34) : warning CS1998: Este método assíncrono não possui operadores 'await' e será executado de modo síncrono. É recomendável o uso do operador 'await' para aguardar chamadas à API desbloqueadas ou do operador 'await Task.Run(...)' para realizar um trabalho associado à CPU em um thread em segundo plano.
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\ProfileTags\ReloadProfileTag.cs(70,34) : warning CS1998: Este método assíncrono não possui operadores 'await' e será executado de modo síncrono. É recomendável o uso do operador 'await' para aguardar chamadas à API desbloqueadas ou do operador 'await Task.Run(...)' para realizar um trabalho associado à CPU em um thread em segundo plano.
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\ProfileTags\TownRunTag.cs(104,34) : warning CS1998: Este método assíncrono não possui operadores 'await' e será executado de modo síncrono. É recomendável o uso do operador 'await' para aguardar chamadas à API desbloqueadas ou do operador 'await Task.Run(...)' para realizar um trabalho associado à CPU em um thread em segundo plano.
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\ProfileTags\Movement\MoveToActorTag.cs(391,34) : warning CS0168: A variável 'ex' está declarada mas nunca foi usada
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\ProfileTags\Movement\SafeMoveToTag.cs(103,33) : warning CS1998: Este método assíncrono não possui operadores 'await' e será executado de modo síncrono. É recomendável o uso do operador 'await' para aguardar chamadas à API desbloqueadas ou do operador 'await Task.Run(...)' para realizar um trabalho associado à CPU em um thread em segundo plano.
Setting up Trinity Logging
[Trinity] Combat routine is not installed or is not latest version, installing! // VERSION 1.2.0
Chose Trinity as your combat routine
[Trinity] Initialized v2.2.0

xzjv · Nov 8, 2014

did u delete your old Questtools folder first?

kililin · Nov 8, 2014

xzjv said:
Yeah because u need latest QT from a GIT like i said.

go here https://www.assembla.com/code/questtools/git/nodes and click the download link on the right side

strange, i just tested it with .496 and .497

.497? where?

xzjv said:
did u delete your old Questtools folder first?

Yeap, fresh install:

Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\Helpers\ActorHisto ry.cs(10,7) : warning CS0105: A diretiva using para 'Zeta.Common' apareceu anteriormente neste namespace
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\Helpers\ActorHisto ry.cs(11,7) : warning CS0105: A diretiva using para 'Zeta.Game' apareceu anteriormente neste namespace
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\Helpers\BotEvents. cs(111,26) : error CS0117: 'QuestTools.Helpers.ProfileUtils' não contém uma definição para 'ReplaceDefaultTags'
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\Helpers\ItemManage r.cs(127,30) : warning CS0168: A variável 'ex' está declarada mas nunca foi usada
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\ProfileTags\Combat SettingTag.cs(88,34) : warning CS1998: Este método assíncrono não possui operadores 'await' e será executado de modo síncrono. É recomendável o uso do operador 'await' para aguardar chamadas à API desbloqueadas ou do operador 'await Task.Run(...)' para realizar um trabalho associado à CPU em um thread em segundo plano.
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\ProfileTags\Explor eDungeonTag.cs(556,34) : warning CS1998: Este método assíncrono não possui operadores 'await' e será executado de modo síncrono. É recomendável o uso do operador 'await' para aguardar chamadas à API desbloqueadas ou do operador 'await Task.Run(...)' para realizar um trabalho associado à CPU em um thread em segundo plano.
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\ProfileTags\QTOpen RiftWrapperTag.cs(118,34) : warning CS1998: Este método assíncrono não possui operadores 'await' e será executado de modo síncrono. É recomendável o uso do operador 'await' para aguardar chamadas à API desbloqueadas ou do operador 'await Task.Run(...)' para realizar um trabalho associado à CPU em um thread em segundo plano.
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\ProfileTags\Reload ProfileTag.cs(70,34) : warning CS1998: Este método assíncrono não possui operadores 'await' e será executado de modo síncrono. É recomendável o uso do operador 'await' para aguardar chamadas à API desbloqueadas ou do operador 'await Task.Run(...)' para realizar um trabalho associado à CPU em um thread em segundo plano.
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\ProfileTags\TownRu nTag.cs(104,34) : warning CS1998: Este método assíncrono não possui operadores 'await' e será executado de modo síncrono. É recomendável o uso do operador 'await' para aguardar chamadas à API desbloqueadas ou do operador 'await Task.Run(...)' para realizar um trabalho associado à CPU em um thread em segundo plano.
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\ProfileTags\Moveme nt\MoveToActorTag.cs(391,34) : warning CS0168: A variável 'ex' está declarada mas nunca foi usada
Compiler Error: c:\Users\****\Desktop\chato\DemonbuddyBETA 1.1.2180.496\Plugins\QuestTools\ProfileTags\Moveme nt\SafeMoveToTag.cs(103,33) : warning CS1998: Este método assíncrono não possui operadores 'await' e será executado de modo síncrono. É recomendável o uso do operador 'await' para aguardar chamadas à API desbloqueadas ou do operador 'await Task.Run(...)' para realizar um trabalho associado à CPU em um thread em segundo plano.
Setting up Trinity Logging
[Trinity] Combat routine is not installed or is not latest version, installing! // VERSION 1.2.0
Chose Trinity as your combat routine
[Trinity] Initialized v2.2.0

Try it: Proceed with the test, please download the latest QT like us (from git). And do a fresh install with DB Beta .496, do not use anything that is already on your computer. Maybe you can reproduce the problem..

Thanks and here I am watching, waiting for the answer. I will not sleep until I can leave the bot running. =)

xzjv · Nov 8, 2014

kililin · Nov 8, 2014

xzjv said:
ok hold on

Thanks and here I am watching, waiting for the answer. I will not sleep until I can leave the bot running. =)

3:41 a.m. atm xD

xzjv · Nov 8, 2014

kililin said:
.497? where?

from nesox lol

kililin said:
Try it: Proceed with the test, please download the latest QT like us (from git). And do a fresh install with DB Beta .496, do not use anything that is already on your computer. Maybe you can reproduce the problem..

Yeah i just tried with the download link and got same errors as you. looks like i forgot a file :S

kililin · Nov 8, 2014

xzjv said:
from nesox lol

Yeah i just tried with the download link and got same errors as you. looks like i forgot a file :S

Worked! Now i'm testing new BrutalKey 1.10.. Thanks xzjv!

About DB .497, already available the download link? or just for internal testing? Thanks again..

kililin · Nov 8, 2014

xzjv said:
from nesox lol

Yeah i just tried with the download link and got same errors as you. looks like i forgot a file :S

Is very good the new QT and BrutalKey 1.10. Finally my keys are balanced!! But I think I found a problem. After the new QT, the bot is ignoring Pools of Reflection.

Act 1 => 117
Act 2 => 117
Act 3 => 117
Act 4 => 117

infinity · Nov 8, 2014

xzjv said:
from nesox lol

Yeah i just tried with the download link and got same errors as you. looks like i forgot a file :S

Tested the same thing but he isn't Zerging but instead he is killing mobs like a retard :/ (zerg version with GSR 1.0.4.3)

FrankNStein · Nov 8, 2014

kililin said:
Is very good the new QT and BrutalKey 1.10. Finally my keys are balanced!! [...]

Yay, glad to hear that. Gonna give it a shot tomorrow =)

fuganator · Nov 9, 2014

It's working great so far. Only issue that I saw when I was checking in was a warden dropped 2 keys and only one was looted.

xzjv · Nov 9, 2014

fuganator said:
It's working great so far. Only issue that I saw when I was checking in was a warden dropped 2 keys and only one was looted.

huh, i had heard they could drop multiple but never seen it

[Profile] Brutal Key Farm

New Member

Attachments

New Member

New Member

Community Developer

Attachments

Community Developer

New Member

Member

Community Developer

New Member

Community Developer

New Member

Community Developer

New Member

Community Developer

Attachments

New Member

New Member

Member

New Member

Member

Community Developer