Playing a DH with Sentry build, i got a problem with Quest-tool and now i hope you can help me fix it somehow. when i set it to run G-rifts, and try to make it stop at some point in the trials it just keeps going to it cant handle it anymore, and thats a problem, the bot cant handle G-rift 40 and above, i have tryed to stop it at 15, just to let the sentrys take a few more lvls by themself, but the bot just goes and places more sentrys after trial 15. how can i fix this, so im able to bot G-rifts ?
Under fBaseXtensions set your Max Tiered Key @ whatever Grift your bot can handle(I am personally at a 35) (I stored tons of 36-40 keys but my bot cant handle that) And then in QuestTools Disable Combat at like 7 or 8 to start and see what kind of keys you get. (lower or raise this to get the key level you want)
even if i lower the setting to 7-8 or i keeps setting Sentrys up, that is my problem, it should be stopping but it dont fBaseXtensions is this another addon ?
set it to wave 5 or wave 6 under quest tool settings. also get the questtools.cs from this thread https://www.thebuddyforum.com/demon...178171-demon-hunter-m6-cold-rocket-build.html
i have now tryed all the stuff and diffent things i have been a ble to find, and thanks for the help you tryed to give. but im still having this problem, and my bot are still not able to do G-rifts by itself, because i keeps getting way to high for it to handle So if anyone have other fixes please link og tell me what have worked for you.
This is what your log should look like if it is working properly: Code: [Funky] Using Custom Cluster Settings! [QuestTools][RiftTrial] Starting Wave: 1 [QuestTools][RiftTrial] Starting Wave: 2 [QuestTools][RiftTrial] Starting Wave: 3 [QuestTools][RiftTrial] Starting Wave: 4 [QuestTools][RiftTrial] Starting Wave: 5 [QuestTools][RiftTrial] Reached Wave 5 Disabling Combat Forced townrun initiated! Reason:Abort Trial It will port to town and sit there for a second and then jump back in and fight a bit more(not sure why it does that)
It works by keeping track of the progress bar for each wave in the quest UI on the right, so its possible to get out of sync, but most of the time seems to get it right. It tries to go to town because that was the easiest way at the time to get it to stop, and you need to leave the area to to de-spawn sentries. We do need a better approach, maybe run to the edge of the area before trying to portal out and then stay in town until its over.
I dont mind the porting out, that seems to work for me. Its the jumping back in the Trial is what would be nice for it not to do.
i have seen i try to port out, but it does that in the middle of all the mobs, and there is no chance that will even go well hope there will be some kind of update to this soon, i dont care how it stops, it okay with me if it just stops doing anything and dies, just to end it at the right time the repair bills will not hurt, but and hurts abit that im not able to run G-rifts.
Best approach would be to make it just run to the top of trial area, possibly port to town from there. I've never had mobs be able to leash on me up there, while doing it manually.
I thought I was alone on this lol. I set to wave 5, and he would try to TP out at 5 once he gets hit he starts dropping more sentries and attacking and next thing you know I am on wave 7-8.. This happens every time because even if he manages to TP to town (which is rare) he sits in town for 3seconds then uses the TP to go back into trial and attacks again typically passing the wave anyways... Any ideas?
I have a problem with trials. My bot doesn't stop fighting after certain wave...Yes i know how it works, it's waves complete not wave number. what happens is, I have bot set up to fight 6 waves....after 6th wave bot is trying to tp, but get's interrupted by mobs, he stand still for few seconds and then starts fighting (WTF?!)...then he fights as long as he can complete thus receving highest possible key i guess part of the code responsible for interruption during tp makes bot fight in this situation but i don't know how to handle this... i have trinity 2.1.21 qt 2.1.40
