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

Trinity 1.9.2 & QuestTools 2.0.14

Status
Not open for further replies.
Oksehode said:
@rrrix:

Would it be possible for you to add like a priority backtracking system that prevents the bot from skipping loot It's suppose to pick up if it gets to far away from it? I see often the bot skip picking up gems.
Click to expand...

It would be easier to just rebuild the entire weighting logic, it should pick them up when it's close enough to.
 
rrrix said:
It would be easier to just rebuild the entire weighting logic, it should pick them up when it's close enough to.
Click to expand...

keyphrase being "close enough to". That's the problem, the bot prioritize doing stuff further away from the loot drops than picking it up sometimes. If the area is not clear for monster and the bot has already run to far away from the loot position, it doesn't run back. I have set the loot radius to 150 and either It's not working as intended or 150 is to far away for the bot to detect it.
 
@rrrix:

My wizard doesnt summon a new hydra after 12 seconds when i am using Ghom profile.
Also is it possible for people who has Serpent's Sparker(able to summon two hydras at the same time) to summon 2 hydras at once and re-summon 2 hydras after 12 seconds?
 
Oksehode said:
keyphrase being "close enough to". That's the problem, the bot prioritize doing stuff further away from the loot drops than picking it up sometimes. If the area is not clear for monster and the bot has already run to far away from the loot position, it doesn't run back. I have set the loot range to 150 and either It's not working as intended or 150 yards is to far away for the bot to detect it.
Click to expand...

It's not working as intended.
 
rrrix said:
Are you using protected slots?
Click to expand...

Yes i am, 18 protected slots for the matter, and coincidence enough, trinity is not using exactly 18 slots cuz it thinks they are being used. I just saw a bunch of ppl having the same issue as me on the thread pointed out by Erxxlu.

It seems trinity is counting the protected slots twice (once for being a protected slot, a second time for the actual item in it). Two different temporary fixes were posted and both are effective, a few other guys confirmed it's been fixed, i can't confirm the fix now, but i will try it later tonight tho it's pretty much been confirmed.

I would still like to hear your thoughts on it tho.

code fix = https://www.assembla.com/code/ury00...mmit/2cc238e40be8d70efac0b7fcc0515142d0e0d2fd

thread pointed out by erxxlu = http://www.thebuddyforum.com/demonbuddy-forum/plugins/trinity/162209-bag-slots.html

btw here's the log you've requested
View attachment 14696 2014-05-09 06.42.txt
 
Last edited:
@rrrix, you remember my case right?

I have news, I believe the problem is the Demonbuddy. I'm doing some tests and I'll post the log up tomorrow.

I'm doing the following tests:

DB .359 + Trinity and QuestTools bundled (Trinity .28 and .52 QT)
DB .359 + Trinity .192 and QuestTools 2.0.14
DB Beta .406 + Trinity and QuestTools bundled (Trinity .28 and .52 QT)
DB Beta .406 + Trinity .192 and QuestTools 2.0.14

I'll warn you, with the DB Beta .406 the problem happens very early. So the problem must be Demonbuddy.


Another thing I almost forgot, DB .359 + Trinity .192 and QuestTools 2.0.14, is not picking up the legendaries, no one.
 
BlowMeDry said:
Hi rrrix, BOT did not prioritise picking Legs and gold. It just ran pass them and start killing mobs or starts to change another bounty.
Click to expand...

This does not help. You're not new here. By now you should know you need to attach a log, which profile you're using, what your settings are, etc. Anecdotal claims like these are ignored.
 
Using the bounty act 1 profiles. It was on the cave of the moon clan and it was just running around and around the map with everything dead. At least 20 mins and the gold timer was never tripped. I have it set to 200 seconds.

I even tried the temp fix that was posted a few days ago, and that doesn't seem to work anymore either.

Using a fresh install of the newest DB and then svn updated trinity and quest tools and armory.

Possibly work fine if i uncheck the "allow profile restarts" in the quest tools options ? I'm watching it right now just waiting for it to screw up a bounty.
 
Last edited:
Just wondering, is it normal that every time I open demonbuddy I get 1 opportunity to config trinity, if I attempt more than once it crashes out? I've had this with every trinity / db I've ever used, assumed it was normal but thought I'd ask just to confirm because it's a little annoying.
 
JoshE said:
Just wondering, is it normal that every time I open demonbuddy I get 1 opportunity to config trinity, if I attempt more than once it crashes out? I've had this with every trinity / db I've ever used, assumed it was normal but thought I'd ask just to confirm because it's a little annoying.
Click to expand...

You need to install .NET 4.5.1.
 
Completely fresh install of latest db beta, trinity/quest tools from this folder. DB still crashes if i try to access trinity settings a second time.


EDIT: Just read above, following those steps now.
 
Job2k9 said:
Confirmed works. What a massive pain it was running 9 bots with trinity crashing my DB's when I tried to config a second time.
Click to expand...

yeah wow i can't imagine your pain, 2 was too bad for me, this'll make for much better fine tuning though, seriously big thanks Oksehode.
 
Oksehode said:
Exactly. You just answered your own question.
It's missing from that topic.
You can find a link to it here.
Click to expand...

Thanks - updated both Demonbuddy download posts. Not sure why this is required actually...
 
rrrix said:
Thanks - updated both Demonbuddy download posts. Not sure why this is required actually...
Click to expand...


I'm not certain of this rrrix, but with Crusaders in town and steed charge - it would appear that it's causing an issue when the bot tries to take a waypoint. I have a profile that works flawlessly on Wizard, Monk & Barbarian but when it's run with my Crusader, it constantly gets held up and watching it - Steed charge is always triggered right as it tries to WP 95% of the time and then it causes the bot to read that if condition as a tag or causes it to loop.

Also, is there a way you can add that setting to Trinity that allows the bot to automatically talk to event npcs/quest givers that you had mentioned a few versions of trinity-ago? It was a very useful function!
 
Is anyone else still having the problem with it ignoring all gold piles?
 
i think a whole bunch of us are. i've had to increase gold inactivity to 300s to avoid getting d/c-ed out of a game.

hang in there, Rixx is working his magic!
 
Status
Not open for further replies.
Back
Top