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

Limit Greater Rift level : modified QuestTools 3.3.2

W

wPrince

Community Developer
Joined
Feb 27, 2015
Messages
38
Reaction score
1
questools.webp

Usage:
1. delete /Plugins/QuestTools/
2. delete /settings/<youname>/QuestTools/QuestToolsSettings.xml
3. unzip questtools3.3.2.2.zip to /plugins/
4. run DemonBuddy.exe and setup QuestTools.
For example , Trial rift wave number to 9 and set Greater rift level to 34, for my monk.

modified files:
/QuestToolsSettings.cs
/UI/ConfigWindow.xaml
/ProfileTags/QTOpenRiftWrapperTag.cs


14.03.2015:
modify /ProfileTags/GetItemFromStashTag.cs
Update the logic mentioned on 07.03.2015
Now, if you set "Highest First" and set limit level, bot works well.

BTW: If you update QT from svn, maybe you need update GetItemFromStashTag.cs if you want use "Highest First".
I am not sure. I haven't tested the branch on svn.
 

Attachments

Last edited:
For example, When you set wave number to 9 in Trial Rift, the key will be able to level 27-40. But level 35-40 is too hard, so we need to limit bot farming only in Greater Rift less than level 35.
This is the solution. Bot will keep level35+ keys in box, and only use level 34 or lower keys.
 
Very nice, will be very useful for those gearing and wanting to level gems.
 
Dude, this is awesome. It works prefect for me.
Thank you for your hard work!
 
xzjv said:
I like this, added it to next version https://www.assembla.com/code/questtools/git/commit/8b67680efd41cf17dcc36ed96c72715364cbac00
Click to expand...

I'm so glad to hear that!

For release version, there are some codes to be modified, if user set Highest First and limit rift level .
/ProfileTags/GetItemFromStashTag.cs:
private Func<ACDItem, bool> ItemMatcherFunc
{
get
{
return i => i.IsValid && (
i.GameBalanceId == GameBalanceId ||
i.ActorSNO == ActorId ||
(GreaterRiftKey && i.GetAttribute<int>(ActorAttributeType.TieredLootRunKeyLevel) > 0 &&
(!QuestToolsSettings.Instance.EnableLimitRiftLevel || i.GetAttribute<int>(ActorAttributeType.TieredLootRunKeyLevel)<=QuestToolsSettings.Instance.LimitRiftLevel))
);
}
}
Click to expand...
 
wPrince said:
View attachment 170600View attachment 170601

Usage:
1. delete /Plugins/QuestTools/
2. delete /settings/<youname>/QuestTools/QuestToolsSettings.xml
3. unzip questtools3.3.2.1.zip to /plugins/
4. run DemonBuddy.exe and setup QuestTools.
For example , Trial rift wave number to 9 and set Greater rift level to 34, for my monk.


modified files:
/QuestToolsSettings.cs
/UI/ConfigWindow.xaml
/ProfileTags/QTOpenRiftWrapperTag.cs
Click to expand...


I guess we need to set "STOP Wave" at 7 or 8, For example, My DH very an very good gear, So I can kill mobs very easily. if I set "stop wave at 9" , then I will never got the grift key less than 35. so maybe we need to set the "stop wave" based on our DPS... etc. So I suggest just do a TEST, then decide what wave you want to do.
 
FYI, it DB completely disregards the entire ''stop attacking after X wave''. And I have already done the 4 ''usage steps''.
 
For me it is working great, set it to level 9, bots get 37-39 keys and gets the rift done in time.
Btw it's a dh.
 
It worked nice for me 1 trial when i did disable after wave 2 (just to try if i did after 2 waves) and that was fine ,but now i try wave 5,6,7 etc it just keeps doing vault around dosnt attack anything very wierd imo :)
 
Is anyone else experiencing a problem where "stop at wave" feature only works 50% of the time? I have it set to 8 and half the time it keeps going until wave 12-13. I have several dozen keys for lvls 40-47 now as a result and it just slows down the entire process, its like the function that stops combat and makes him go TP just doesn't work sometimes.
 
I'm using the lastest QuestTools from SVN with the new feature, and it's working marvellous.

Thanks wPrince and xzjv!
 
db user said:
Would you be able to add the min gem % to upgrade on in there as well?

Like this:
https://www.thebuddyforum.com/demon...205469-chance-increasing-legendary-stone.html
Click to expand...


Yes, it's usable. But there are too many branch versions, so maybe I modify QT after next release version.
You can modify code like I am doing.

/Plugins/QuestTools/ProfileTags/CompleteFreaterRiftTag.cs : line 233 in QT3.2.2
if (delta <= -7) return 0f; //Diablo3 disables upgrades for -15 levels difference
Click to expand...
modify -7 to -1, then Bot will only upgrade gem with 30%+ rate.
 
You must log in or register to reply here.
Back
Top