What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

To fix rrrix's R-Rift wave bug -- Use mob's top hitpoints instead of wave

W

wPrince

Community Developer
Joined
Feb 27, 2015
Messages
38
Last edited:
does this acutally work?

a side from that, rolling back to QuestTools 3.3.1 fixed any trial wave probs for me so far
 
pretty good idea really. i will look into it.
 
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
 
Last edited:
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
 
wPrince said:
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.
Click to expand...


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?
 
Tumzie said:
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?
Click to expand...
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
 
xzjv said:
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
Click to expand...

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
public static double theBigBoss
{
get
{
double maxHP = 0f;
foreach (TrinityCacheObject u in Trinity.ObjectCache)
{
if (u.IsUnit && u.CommonDataIsValid && u.HitPoints / u.HitPointsPct > maxHP)
maxHP = u.HitPoints / u.HitPointsPct;
}
return maxHP;
}
}
Click to expand...

/Plugins/QuestTools/Helpers/RiftTrial.cs: PulseRiftTrial()
object maxHP = null;
const double limitedHP = 845678900;
if (TrinityApi.GetProperty("Trinity.Combat.Abilities.CombatBase","theBigBoss", out maxHP))
{
if (QuestTools.bigbossHP < (double)maxHP)
{
QuestTools.bigbossHP = (double)maxHP;
Logger.Raw("The big boss's Max HP is :{0} ,{1:P}%\n", QuestTools.bigbossHP, QuestTools.bigbossHP/limitedHP);
}
}
Click to expand...
 
Last edited:
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?
 
violentpasta said:
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?
Click to expand...

try the normal one

limit it to 5-7

works for me i get around 22-28 grifts with it.
 
Last edited:
violentpasta said:
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?
Click to expand...

Set the normal QuestTools to 7-8 WAVES and adjust upwards accordingly.
 
You must log in or register to reply here.
Back
Top