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

Trinity 2.2.0 and QuestTools 3.0.5

Status
Not open for further replies.
I don't want upgrade my old trinity(since did a lot of my own changes), but QuestTools v2.1.38 have a lot of issues so i decide to upgrade it, but bot become super stupid.

Trinity v2.1.21 + QuestTools 3.0.5 : Ticks ~6
Trinity v2.1.21 + QuestTools 2.1.38 : Ticks ~8

Difference in ticks not a huge, but on practice QT 3.0.5 making bot like 5x time more dumb. This is with your bounty profile: act1.xml.

So QT3.0.5 is not compatible with Trinity v2.1.21?
 
Last edited:
errol said:
mhhhh, i have set the bot to keep legendary item unidentified, but the bot will try its best everytime it picks up one to indentify it, i have no clue why
Click to expand...
Are you by any chance using Armory plugin?
 
Seems to run well except ticks/s seem lower, need to increase d3 fps to 100+ in order to get over 10t/s.
Another thing is am being randomly spammed by this error:
Exception during bot tick.System.NullReferenceException: Object reference not set to an instance of an object.
at QuestTools.ProfileTags.ExploreDungeonTag.FindPrioritySceneTarget() in e:\bottar2\Plugins\QuestTools\ProfileTags\ExploreDungeonTag.cs:line 1216
at QuestTools.ProfileTags.ExploreDungeonTag.<PrioritySceneCheck>b__b2(Object ret) in e:\bottar2\Plugins\QuestTools\ProfileTags\ExploreDungeonTag.cs:line 1124
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Sequence..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.DecoratorContinue..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Sequence..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Decorator..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Sequence..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Common.HookExecutor.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Common.HookExecutor.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Bot.BotMain.()
 
Bulleye1234 said:
I don't want upgrade my old trinity(since did a lot of my own changes), but QuestTools v2.1.38 have a lot of issues so i decide to upgrade it, but bot become super stupid.

Trinity v2.1.21 + QuestTools 3.0.5 : Ticks ~6
Trinity v2.1.21 + QuestTools 2.1.38 : Ticks ~8

Difference in ticks not a huge, but on practice QT 3.0.5 making bot like 5x time more dumb. This is with your bounty profile: act1.xml.

So QT3.0.5 is not compatible with Trinity v2.1.21?
Click to expand...

Try complete fresh install. I am doing act 1 bounties with latest trinity and qt. It was never great before like that

P.S: my ticks doesnt changed. still playing with 15.
 
replace all your changes to the newest trinity and you will be fine
 
There are HUGE TPSGATE on newest Trinity&QT. what's wrong with me.
 
I am having big problems trying to update Trinity and questools.

Haven't updated in a while since the bot was working well enough for me, so I thought it was about time.
Unfortunately, on a completely fresh install with new DB beta (492) , new Trinity and new Questools (as of download link on 1st post), for whatever reason kiting doesn't seems to work and neither does avoidance. At least properly. And the bot just limits to set sentries, and then just do nothing. Doesn't kite, doesn't go out from avoidance, doesn't even use another shooting skills.

I'm quite sure it is an error on my side somehow. If someone could point me to where it is, that would be great.

Btw, did not copy settings from previous installations. It is a clean install from scratch. And I'm using the new R-Rift as profile.
 

Attachments

Last edited:
rrrix: you are amazing, appreciate every bit of your work, THANKS!
xzjv and jubisman: you guys are doing a incredible job contributing to this project, keep it up, THANKS!
 
pathfinding Seems a little bit broke.
With Riftbot (riftbot full) (newest version) kills the riftboss and find the riftstone. bot runs back and forth through the whole map.
 

Attachments

Kevin Spacey said:
replace all your changes to the newest trinity and you will be fine
Click to expand...

To much changes, not worth the time, especially if new QT have same old issues with Bounties, like stuck on dead body of Bounty target, or infinity explore of map after all Bounty objective is finished.
 
Thanks for your support rrrix, I keep donating 10 dollars for every official Trinity/QT release and will continue doing this as long as you continue to update your work. I just have one small question, it might not be related to your work but.....

Bug Report form:
------------------------
What's the problem?
Low EXP pr hour on all my 5 bots when looking at the EXP/Hour tab in demonbuddy.

What steps will reproduce the problem?
Running 2.1.22 and QT3.0.5

What is the expected result?
On Trinity 2.1.21 and QT 3.0.0 (Stable 383) running RiftBot 432 I was making up to 3 billion pr hour the past week on my DH bots.

What happens instead?
Went over to 2.2.0 and 3.0.5 (Beta 492) with the same trinity settings I had before and been running RiftBot 432 today for around 4-5 hours and my EXP is barely over 1,5 billion pr hour on my DH bots.


This is the case on all my bots, both my DHx2, Barb, Wiz and WD are getting very low EXP in T6 rift now but eem like my bots are backtracking alot.

EDIT: It can be that there have been some update to deamonbuddy itself, I have asked in their thread.
 
Last edited:
But, I'm getting problem that my DH don't wanna maintain the minimum Kite range, it just stands still and shoots mobs while they walk again him and dont try to kite/vault away.
 
Last edited:
Arotished said:
But, I'm getting problem that my DH don't wanna maintain the minimum Kite range, it just stands still and shoots mobs while they walk again him and dont try to kite/vault away.
Click to expand...
Can you attach a log?
 
Only issue i noticed with DH is that he is using cluster arrow or basic attacks. Even if he is at half hatred bot waits till full hatred then starts spamming 2 - 3 clusters till he reaches minimum hatred to sentry. Kinda waste of potential if he cant use elemental arrow which costs 10 hatred. Also lil suggestion: some tweaking with disabling combat while playing dh and doing trials. Even if you put grift level 30 to stop your sentries will stay up for next 2 - 3 waves so basically instead of finishing with ~30 level key you finish with 35+.
 
Last edited:
feifei said:
i have two problem for this new QT and trinity:

1、r-rix cannot run ,it only run normal rift
2、 when i start the db,it only run one time, then it will stop run..
Click to expand...

Actually it will begin the next run after long times waiting, also can't do common rift run even I have chosen it, it will explore every corner of the map after the boss is killed. Please help fix that problem.

DB Trinity2.2.0 Questtools 3.0.5 are updated to latest.
 
Damn, really low TPS (1-4) when limiting my ingame FPS at the usual 20 or 30. Setting the fps limiter off really makes d3 use a lot more processing power. Also ignoring elites alot of the time. Seems like the bot gets obsessed with trying to get somewhere and if surrounded just stands there.
 
Last edited:
low tps also game keeps dropping not sure if d3 servers are acting up or what... its failed in 4 GR so far game just losses connection
 
Status
Not open for further replies.
Back
Top