Thank you for the log, bot did try to use TownPortal for a good 5 minutes before exception; i'm not familiar with this one but according to rrrix it means D3 or DB froze, possible that TownPortal or something else still caused it to freeze. Have to see if it happens again or just a freak accident.
Thank you for the log, bot did try to use TownPortal for a good 5 minutes before exception; i'm not familiar with this one but according to rrrix it means D3 or DB froze, possible that TownPortal or something else still caused it to freeze. Have to see if it happens again or just a freak accident.
i just removed and updated all my framework stuff and gonna delete cache see if i can make sure the out of sync error doesnt happen again so we can see if its the progile or somthing with DB that causes the crash ill run it for a while and see
Yeah... i am going to have to switch to SafeMoveTos to give a better chance to find without backtracking, especially for A3 Stonefort, every now and then hes hiding on some pedestal somewhere really obscure.
Im not certain how it all works but considering the time to back track looking for the obscure spot, would it not be easier to say Leave game if you reach "X" (the end) and just start the game over or go to next KW?
thanks for your work on this ive gained 50+ keys of each so far.... so it is working fairly well.
That's one way to do it, go for fast main path through the level and then leave, the question is; is it worth the extra few seconds here and few seconds there to check more closely on obscure spots as you go. The quick path option will miss wardens and then you lose minutes. I don't know the best approach.
The new version attached has SafeMoveTo paths for A1-3 and the same Explore on A4.
* A1- is the kill path taken from A1 bounties, its pretty broad sweep.
* A2- is new, it took a long time to make and is VERY thorough, it shouldn't miss a warden.
* A3- is new, checks all the pedestal areas, it shouldn't miss a warden.
* turn on "enable beta features" in settings, this enables last known position on MoveToActor, something that still needs more testing but should in theory always know where an actor was last seen, even if DB doesn't know where it is anymore (because its dead and its corpse dissappeared or because its currently out of range). it does however, also enable the new condition parser for IF and When tags, which may break other profiles, so be aware of that.
edit >
heres an example of last known position, without it MoveToActor would have stopped and townportal without killing warden.
Code:
-~-..-~-..-~-..-~->-> Async Found A1 Keywarden! PEW PEW
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.Complex.AsyncLogMessageTag IsDone=True IsDoneCache=True LastStatus=Success
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.Complex.AsyncToggleTargetingTag IsDone=True IsDoneCache=True LastStatus=
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.Complex.AsyncToggleTargetingTag IsDone=True IsDoneCache=True LastStatus=Success
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.Movement.MoveToActorTag IsDone=False IsDoneCache=False LastStatus=
[QuestTools][MoveToActorTag] Can't find actor! using last known position <2115.255, 973.8032, 0.1000009> Distance=105.0037
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.Movement.MoveToActorTag IsDone=False IsDoneCache=False LastStatus=Success
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.Movement.MoveToActorTag IsDone=False IsDoneCache=False LastStatus=Success
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.Movement.MoveToActorTag IsDone=False IsDoneCache=False LastStatus=Success
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.Movement.MoveToActorTag IsDone=False IsDoneCache=False LastStatus=Success
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.Movement.MoveToActorTag IsDone=False IsDoneCache=False LastStatus=Success
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.Movement.MoveToActorTag IsDone=False IsDoneCache=False LastStatus=Success
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.Movement.MoveToActorTag IsDone=False IsDoneCache=False LastStatus=Success
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.Movement.MoveToActorTag IsDone=False IsDoneCache=False LastStatus=Success
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.Movement.MoveToActorTag IsDone=False IsDoneCache=False LastStatus=Success
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.Movement.MoveToActorTag IsDone=False IsDoneCache=False LastStatus=Success
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.Movement.MoveToActorTag IsDone=False IsDoneCache=False LastStatus=Success
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.Movement.MoveToActorTag IsDone=False IsDoneCache=False LastStatus=Success
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.Movement.MoveToActorTag IsDone=False IsDoneCache=False LastStatus=Success
[QuestTools][BotBehaviorQueue] A1 Key Success! Running 6 Behaviors
I told Tony (mod) that if you need something tested I would donate my time for the work you guys do here and the same goes for you here.... I'll test anything you need even though I have a working copy and 60+ key sets from your old version that is still working for me. So, let me know... ButI warn you I will need some more detailed instructions I am not a super computer guy just an avg Joe with no background.
this german/russian to me I am not sure what you mean = * turn on "enable beta features" in settings, this enables last known position on MoveToActor.
will DL a new copy of DB and QT and I'll do ^^^^^^^^^^^^^^^^ that too just ensure your instructions are clear and I'll run it over night and give feedback/logs if you let me know how to do that too. More than happy to help everyone that is creating the profiles that we all take for granted and use.
DEBUG BrainBehavior Exception during scheduling Pulse: System.NullReferenceException: Object reference not set to an instance of an object.
at Zeta.Bot.ProfileOrderManager.(IEnumerable`1 )
at Zeta.Bot.ProfileOrderManager.UpdateCurrentBehavior()
at Zeta.Bot.ProfileManager.UpdateCurrentProfileBehavior()
at Zeta.Bot.Logic.OrderBot.(Object , EventArgs )
at System.EventHandler.Invoke(Object sender, EventArgs e)
at Zeta.Bot.Logic.BrainBehavior.DoScheduling()
I keep getting spammed with that in log and it just stands still and does nothing . I see you mentioned to enable "enable beta features", I can't seem to even find that option on my quest tools plugin config
DEBUG BrainBehavior Exception during scheduling Pulse: System.NullReferenceException: Object reference not set to an instance of an object.
at Zeta.Bot.ProfileOrderManager.(IEnumerable`1 )
at Zeta.Bot.ProfileOrderManager.UpdateCurrentBehavior()
at Zeta.Bot.ProfileManager.UpdateCurrentProfileBehavior()
at Zeta.Bot.Logic.OrderBot.(Object , EventArgs )
at System.EventHandler.Invoke(Object sender, EventArgs e)
at Zeta.Bot.Logic.BrainBehavior.DoScheduling()
I keep getting spammed with that in log and it just stands still and does nothing . I see you mentioned to enable "enable beta features", I can't seem to even find that option on my quest tools plugin config
Ok - here's a basic guide of how to get the files.
EDIT >> >NOTE -= >?> you can just skip all this and download from this link https://www.assembla.com/code/questtools/git/nodes/master?_format=zip it will always give you the latest version from GIT >> Go to step 10 Turn on "Enable Beta Features" checkbox, in Questtools settings.
Download and Install TortoiseGIT software for windows. https://code.google.com/p/tortoisegit/. - it is a free, opensource software that i didn't make, its publicly available and widely used.
Create a new folder somewhere and go into it; while inside in the empty folder in Windows Explorer, right click and choose "Git Create Repository Here"
It will prompt you about some stuff, just keep the box unchecked and click okay
it then says some stuff, click ok
Next right click in the folder again and select TortoiseGIT, and PULL from the menu - Pull means Download
Next u have to put where to download it from, so click Arbitrary URL radio, and paste in https://git.assembla.com/questtools.git and the remote branch should be 'master' and u can probably leave the other settings.
It should download the files now and show a dialog like this
Now u can just copy the files to your DB plugins\QuestTools folder
Turn on "Enable Beta Features" checkbox, in Questtools settings.
Keep this one checked. Unchecked it on the first time. got error. Checked it again, all went be fine
Tx xzjv for the tutorial !
Edit : Did i do something wrong ?
1. Trinity V 2.1.21
2. Questtools V3.0.0 (Checked the beta thing)
3. BrutalKeyFarm V 1.05
4. DemonBuddy V1.1 r2150 Build 38 (Maybe i need the Beta one )
A. Tried the Zerg Version,
Everything run smooth, except that when i found the Keywarden, my saders keep spaming SteadyCharge instead of fighting him. B. Tried the Normal version.
1st : Act4 : I kill the warden, but not TP afterward, Keep spaming SteadyCharge
In the information window This is spamming :
[QuestTools][BotBehaviorQueue] Tag QuesTools.ProfileTags.TownPortalTag IsDone=False IsDoneCache=False LastStatus=Succes
on the bottom info, i'm switching betwen :
TownPortalTag:WaitTime: 2500, is done:False, QuestId:1, StepId:1...
Bot Paused
TownPortalTag:WaitTime: 2500, is done:False, QuestId:1, StepId:1...
Bot Paused
etc
Edit2 : Act3 runed smooth with normal version without spamming like a4 (i'll keep monitoring )
Edit3 : things run smooth with the DB Beta version and Zerg (Or semiZerg, i'm still fighting Elite on the road (Range set to 0)
Do you want i add some log ? (wich one do you want i check ?)
TP Bug (as mentionned above but act2 this time) : (hope you've got all you need)
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.TownPortalTag IsDone=False IsDoneCache=False LastStatus=Success
[Trinity][Performance] Execution of TargetCheck.OOCBuff took 200.22ms.
[Trinity][Performance] Execution of TargetCheck took 210.96ms.
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.TownPortalTag IsDone=False IsDoneCache=False LastStatus=Success
[Trinity][GlobalHandler] Gold unchanged for 172s
[Trinity][Performance] Execution of TargetCheck took 17.35ms.
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.TownPortalTag IsDone=False IsDoneCache=False LastStatus=Success
[Trinity][Performance] Execution of TargetCheck.OOCBuff took 200.10ms.
[Trinity][Performance] Execution of TargetCheck took 212.23ms.
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.TownPortalTag IsDone=False IsDoneCache=False LastStatus=Success
[Trinity][GlobalHandler] Gold unchanged for 179s
[Trinity][Performance] Execution of TargetCheck took 12.76ms.
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.TownPortalTag IsDone=False IsDoneCache=False LastStatus=Success
[Trinity][Performance] Execution of TargetCheck.OOCBuff took 199.46ms.
[Trinity][Performance] Execution of TargetCheck took 210.62ms.
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.TownPortalTag IsDone=False IsDoneCache=False LastStatus=Success
[Trinity][GlobalHandler] Gold unchanged for 185s
[Trinity][Performance] Execution of TargetCheck took 16.12ms.
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.TownPortalTag IsDone=False IsDoneCache=False LastStatus=Success
[Trinity][Performance] Execution of TargetCheck.OOCBuff took 199.56ms.
[Trinity][Performance] Execution of TargetCheck took 215.96ms.
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.TownPortalTag IsDone=False IsDoneCache=False LastStatus=Success
[Trinity][GlobalHandler] Gold unchanged for 191s
[Trinity][Performance] Execution of TargetCheck took 10.43ms.
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.TownPortalTag IsDone=False IsDoneCache=False LastStatus=Success
[Trinity][Performance] Execution of TargetCheck.OOCBuff took 199.74ms.
[Trinity][Performance] Execution of TargetCheck took 216.45ms.
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.TownPortalTag IsDone=False IsDoneCache=False LastStatus=Success
[Trinity][GlobalHandler] Gold unchanged for 198s
[Trinity][Performance] Execution of TargetCheck took 16.11ms.
[QuestTools][BotBehaviorQueue] Tag QuestTools.ProfileTags.TownPortalTag IsDone=False IsDoneCache=False LastStatus=Success
Ah, I just stupidly assumed the ezupdater plugin would grab the newest version for me. Got tortoisegit and the proper questtools, works great now thanks
TortoiseGiT not tortoise svn, they are different. If you try to use the link via svn it will ask for a password. Also for the tortoise git you also need to install Git for Windows in a windows environment
Yeah its because, as i said, u need to download QuestTools from the GIT.
Ok - here's a basic guide of how to get the files.
Download and Install TortoiseGIT software for windows. Google it since we're not allowed to post links to external downloads on forum. - it is a free, opensource software that i didn't make, its publicly available and widely used.
Create a new folder somewhere and go into it; while inside in the empty folder in Windows Explorer, right click and choose "Git Create Repository Here"
It will prompt you about some stuff, just keep the box unchecked and click okay
it then says some stuff, click ok
Next right click in the folder again and select TortoiseGIT, and PULL from the menu - Pull means Download
Next u have to put where to download it from, so click Arbitrary URL radio, and paste in https://git.assembla.com/questtools.git and the remote branch should be 'master' and u can probably leave the other settings.
It should download the files now and show a dialog like this
Now u can just copy the files to your DB plugins\QuestTools folder
As for the beta checkbox, i know its a bit confusing, but i did it in case we needed to release a version before the new experimental stuff has been fully tested, it defaults to OFF; turn it on in Questtools settings.
Is there an easy way I can disable certain acts? I have a ton of A4 keys from other (bounty) botting. This profile skips A4 as my highest key count, but then defaults over to A3, runs that successfully, and then gets questionable success on A2/1. I'm now ending up with a lot of extra A3 keys accumulating, and not much A2/1 action, since they seem to fail a lot for some reason.
Can I just temporarily comment out the A4/3 parts of the xml, or will that break the script?
Alternatively, can I just dump any extra A4 keys on an alt, so it sees my A3 keys equal to A4 keys, and only does A1&2?
edit: I just made an alternate version of the profile and deleted the A3/4 sections and it appears to be working fine at only doing 1+2. Is there a way you can work better balancing logic into a future release? The "don't do highest Act" is nice, but cutting it down to the lowest two acts if there's a significant key imbalance would be great too.
i must have done somthiung qwrong even following your guide when i open the folder and right click create Git it ask me for the path to git or w/e, so let me ask you this when i go to your GIT site and see all the changes i have a page that is for quest tools and gives me the option to gownload and when i do it makes a file called root.zip when i extract it it has all the quest tool files, is this the most current changes or will this not work
i actually just gt the git to set up but question still stands is the root.zip file the same as the git files
He didn't add that in the post, but it is necessary, it is mentioned in the install guide for tortoise git. It will ask for path if you don't install that as well
. I see you mentioned to enable "enable beta features", I can't seem to even find that option on my quest tools plugin config
