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

Trinity 2.1.21 and QuestTools 2.1.38

Status
Not open for further replies.
I got problem with QuestTools 2.1.40+ (updated via svn with EZupdater), the bot ran r-rift profile didn't upgrade gem but it upgraded keystone instead (although Upgrade Gem option was chosen), and if it can't upgrade keystone (timer run out) it stucked at gem upgrade UI, all my gems are rank 40+, not sure if this caused conflict.
Reverted back to QT 2.1.38 and everything works fine.
 
Last edited:

That is NOT my github.

Someone cloned the Unified trinity git and made their own fork.

Beware of this, i do not in any way endorse, review, or support this. I encourage you to review and diff this software before installing, it could harbor any number of bad things in it.

Just because it's called "trinity" does not mean it's actually Trinity.
 
I got problem with QuestTools 2.1.40+ (updated via svn), the bot ran r-rift profile didn't upgrade gem but it upgraded keystone instead (although Upgrade Gem option was chosen), and if it can't upgrade keystone (timer run out) it stucked at gem upgrade UI.

2.1.40 ? :S Latest version is 2.1.38
 
the bot does recognize spark now and multi casts hydra but problem is its spam casting.... is there anyway to build into the bot that after 2 casts within say 1500ms it triggers the 12000 ms cooldown on recast cause the spam casting obviously is an issue
 
why those updates not pushing to svn?

Because... while we try to make sure we don't check in bad code, often the git version is buggy, you should definitely consider it beta. We have to put the code on GIT first so that we can collaborate and so more people than just the author can test it. If you want it pushed to SVN, then download it from the GIT and help test it so we know its stable.
 
Because... while we try to make sure we don't check in bad code, often the git version is buggy, you should definitely consider it beta. We have to put the code on GIT first so that we can collaborate and so more people than just the author can test it. If you want it pushed to SVN, then download it from the GIT and help test it so we know its stable.
ok got it. thx
 
That is NOT my github.

Someone cloned the Unified trinity git and made their own fork.

Beware of this, i do not in any way endorse, review, or support this. I encourage you to review and diff this software before installing, it could harbor any number of bad things in it.

Just because it's called "trinity" does not mean it's actually Trinity.

The utter fuck? That IS my github...

And I also do not in any way endorse or support this. I encourage you to review and diff this software before installing, that is my PERSONAL version of Trinity which has my modifications... this is not for public usage
 
I have a problem with trials.
My bot doesn't stop fighting after certain wave...Yes i know how it works, it's waves complete not wave number.
what happens is, I have bot set up to fight 6 waves....after 6th wave bot is trying to tp, but get's interrupted by mobs, he stand still for few seconds and then starts fighting (WTF?!)...then he fights as long as he can complete thus receving highest possible key :(

i guess part of the code responsible for interruption during tp makes bot fight in this situation but i don't know how to handle this...

i have
trinity 2.1.21
qt 2.1.40
 
Last edited:
I have a problem with trials.
My bot doesn't stop fighting after certain wave...Yes i know how it works, it's waves complete not wave number.
what happens is, I have bot set up to fight 6 waves....after 6th wave bot is trying to tp, but get's interrupted by mobs, he stand still for few seconds and then starts fighting (WTF?!)...then he fights as long as he can complete thus receving highest possible key :(

i guess part of the code responsible for interruption during tp makes bot fight in this situation but i don't know how to handle this...

i have
trinity 2.1.21
qt 2.1.40

Mine will TP out no problem on the correct wave, but then re-enter the portal after a few seconds in town. Sometimes this results in finishing that wave and it will then keep going until time eventually runs out or a death occurs.
 
How can I stop the bot from backtracking? Wasting alot of time in grifts...
 
You could change the "exploration" mode, test them one by one and see what's happening.


Done that, they all are as bad as each other. Seems to have a fascination with health globes half a map away, it will back track to get a health globe.Maybe there can be some limit placed on distance away before it goes back tracking, maybe 50 yds ? This should stop the aimless wandering maybe ?

G
 
Status
Not open for further replies.
Back
Top