It's a bad idea to use the wave number to decide if bot stop trial rift. And it's hard to dig out the wave number. Using mob's top Hitpoints is a easy way. But we should test the rate of HP/wave. 2015.3.6： I have make a modification to solve the problem partially, by limitting the high level keys. These keys will be kept in box. https://www.thebuddyforum.com/demonbuddy-forum/plugins/trinity/206763-limit-rift-level-modified-questtools-3-3-2-a.html
does this acutally work? a side from that, rolling back to QuestTools 3.3.1 fixed any trial wave probs for me so far
did you manage to get this working? would be super keen to learn how you managed to incorporate the code into the exitsting scrpt!
Free bump I am also having problems with greater rifts as R-Rift is going too ham in the trials. Edit1: Couldn't we do a bitmap of the "wave #" part? we would have to have an image for each one but then it can reflect...if #31 showed up -> a) stop killing b) continue killing until next bitmap wave appears....?
I have the exact same problem. It just goes ham in trials completely distegarding the QuestTools settings about when to cease fire.... Any fixes for this so far? yours faithfully, Tumzie
I have made an modification to QuestTools to limit the Greater Rift Level. https://www.thebuddyforum.com/demonbuddy-forum/plugins/trinity/206763-limit-rift-level-modified-questtools-3-3-2-a.html When I set trial rift wave number to 9, the key levels will be from 27-40. My modification can limit bot fighting Greater Rifts below level 35. But that is not enough. I want Questtools limitting the trial result to 32-36， if the suitable level is 34.
guys, i rerolled back to QuestTools 3.3.1 and everything is working perfectly fine there, just fyi had the same probs with QT 3.3.2
Did this, still not working for me. It steams through all the waves it possibly can. Told it to stop after 5 waves but goes for grift 40 plus if I let it have its way.... any other solution?
Use my version. Enable and set Greater Rift level to 40. Then bot will keep the 40+ keys in your box, and only use these lvl 40 & 40- keys.
can you repost the hitpoints stuff, it looked like you had figured out how much the hitpoints are multiplied for each wave. I am thinking that you can target an exact key level by throttling how fast things are killed
Thank you for your attention. I'm just thinking if I can ask you some question I'm not so familar to DB API or Trinity. The problem is how to get the hitpoints or killed enemies. When I use ZetaDia.Actors.GetActorsOfType<DiaUnit>() to traverse enemits in QuestTools, It doesn't work. So I export a function from Trinity, and use TrinityApi to get it. Sometimes It works, it showes the right HP. But sometimes It will get a number like 278889.645. What's the correct way? /Plugins/Trinity/Combat/Abilities/CombatBase.cs /Plugins/QuestTools/Helpers/RiftTrial.cs: PulseRiftTrial()
In trial rift, max HP is different each type of monsters. so, my idea is pick up a few monsters name & HP each. There are few (less than 10) monsters type in trial rift. so, Maybe should get a unless 5 monster types are enough I think. It is just IDEA. I dunno How to write code xD
I have a semi-solution that I usually do. You can unequip some pieces of gear from your char so he cant effectively clear trials above a certain level. I usually do 100-200 trials this way so I can leave him farming GR's afk. Sometimes you might get a few lower keys, but you can have the bot upgrade them anyways so its more economic in terms of trial keys.
Does anyone have a new solution? I am using this profile, and i limit the trial to stop at Greater rift 25. However my bot goes ham anyway and just rapes everything and i die 30 times an hour. I really want it to stop combat at about 28. Does anyone have a solution?
