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

Trinity 1.7.3.7

Status
Not open for further replies.
Kevin Spacey said:
RRRIX, forgot to show you my profile

Code: 
 <!-- ********************* -->
    <!-- The Forgotten Ruins -->
    <If condition="CurrentLevelAreaId == 61632">
      <TrinityOffsetMove questId="1" stepId="1" offsetX="-40" offsetY="-30" offsetZ="-5" pathPrecision="5" statusText="Dodge Pillar"/>
      <TrinityExploreDungeon questId="1" stepId="1" until="ObjectFound" actorId="179951" boxSize="10" boxTolerance=".20" townPortalOnTimeout="true" statusText="Searching for way back to Oasis">
        <IgnoreScenes>
          <IgnoreScene sceneName="Entrance" />
        </IgnoreScenes>
        <AlternateActors>
          <AlternateActor actorId="135248" objectDistance="200" />
        </AlternateActors>
      </TrinityExploreDungeon>

       <WaitTimer questId="1" waitTime="1000" />
      <UseObject questId="1" stepId="1" actorId="135248" isPortal="True" destinationWorldId="70885" interactRange="30"/>
      <!--UsePortal questId="1" stepId="1" portalMarkerHash="-2108639540" destinationWorldId="70885" interactRange="25" /-->
      <AcceptConfirmation questId="1" pauseTime="1000" />
      <LoadProfile profile="Oasis+FR_WC+EC_Storm_Hall_v0.1.xml" nodelay="true" />
    </If>
Click to expand...

use a WaitTimer tag. Added it for you. WaitTimer will force Trinity to clear the area of all monsters, including elites and stragglers. It does not "override" the blacklist however.
 
Nazair said:
SafeMoveTo tag is not implemented in Trinity.
You need QuestTools plugin to support this "command". You can download it in any thread with Rrrix's profile.
Click to expand...


Thank you - i was beginning to wonder what i was doing wrong - I must have forgot to do the fresh install of QuestTools plugin along with the new installs.
 
My WD does not attack elites. I think many other people also meet such problem. "Ignore Elite" is not checked and "Skip Elites with 5 NV" is not checked either.
And it seems my WD does not know how to use plague of toads.
 
hey guys, using 1.7.3.8 and the witch doctor problem has not been fixed. sometimes the WD just buffs up then stands there next to a mob and gets wiped out. just another guys point of view! thanks
 
Vamp2613 said:
hey guys, using 1.7.3.8 and the witch doctor problem has not been fixed. sometimes the WD just buffs up then stands there next to a mob and gets wiped out. just another guys point of view! thanks
Click to expand...


1.7.3.8 in beta, wait final version
 
Anyone know inform what the trinity more stable lately? I'm using Monk, tempest rush build, TR movement only..
 
WackJagon said:
FIRST and foremost, thanks to rrix and ALL the other who have contributed over time to make this what it is. Know that there are MANY who TRULY appreciate everything you all do!

I did want to mention an issue that I saw with both 1.7.3.6 and 1.7.3.7, my bots will fail to repair, gear turns red and then the game will just emergency exit over and over and never repair. I am glad I caught it before it went on too long. I went back to 1.7.3.5 and all is well again.

Could I just be missing a setting somewhere perhaps?
Thanks in advance!
Click to expand...

Didn't get a response lol. I know I am "new' here but been "reading" for months just didn't have any questions or issues or anything to contribute lol..

I continue to have this error, or a flavor of. If I use 1.7.3.5 I do not have either issue. I have tried using the latest DB Beta and that does not seem to help.

[Problem first noticed with 1.7.3.6) = I was getting "emergency exits" when gear durability was low and bot would not repair. I see RRIX noted a fix for that.

[Current problem with 1.7.3.7) = Bot goes to town when durability is low but doesn't repair, just stands there. If I restart bot still doesn't repair.
If I manually repair the bot wakes right up and continues on as if nothing happened :)

Plugins:
Quest Tools 1.3.8
Trinity 1.7.3.7

DB version 1.0.1446.317

The profile I am using shouldn't matter for this type of issue right?

Thanks in advance for any advice :)
 
rrrix can you look at this please?
im testing my profile now (signature) with QT .11 and trinity 1.7.3.8 beta
and often i can see when bot enter to the firt channel he just stand at one place without any mooves
in log i can see loop message
Code: 
questing=False level=60
[22:45:43.603 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:43.968 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:43.968 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:44.372 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:44.372 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:44.686 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:44.686 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:45.046 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:45.046 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:45.374 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:45.374 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:45.733 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:45.733 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:46.134 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:46.134 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:46.532 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:46.532 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:46.919 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:46.919 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:47.309 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:47.309 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:47.618 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:47.618 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:47.980 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:47.980 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:48.372 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:48.372 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:48.773 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:48.773 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:49.173 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:49.173 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:49.572 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:49.573 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:49.961 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:49.961 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:50.284 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:50.284 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:50.649 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:50.649 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:51.054 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:51.054 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596 
[22:45:51.443 D] [Trinity][Weight] Starting weights: packSize=8 packRadius=20 MovementSpeed=0 Elites=0 AoEs=0 disableIgnoreTag=False closeRangePriority=True townRun=False forceClear=False questing=False level=60
[22:45:51.443 D] [Trinity][Weight] Weight=0 name=Barbarian_Male sno=3301 type=Player R-Dist=1 IsElite=False RAGuid=-1341849596
 
WackJagon said:
Didn't get a response lol. I know I am "new' here but been "reading" for months just didn't have any questions or issues or anything to contribute lol..

I continue to have this error, or a flavor of. If I use 1.7.3.5 I do not have either issue. I have tried using the latest DB Beta and that does not seem to help.

[Problem first noticed with 1.7.3.6) = I was getting "emergency exits" when gear durability was low and bot would not repair. I see RRIX noted a fix for that.

[Current problem with 1.7.3.7) = Bot goes to town when durability is low but doesn't repair, just stands there. If I restart bot still doesn't repair.
If I manually repair the bot wakes right up and continues on as if nothing happened :)

Plugins:
Quest Tools 1.3.8
Trinity 1.7.3.7

DB version 1.0.1446.317

The profile I am using shouldn't matter for this type of issue right?

Thanks in advance for any advice :)
Click to expand...

Well I first wanted to tell you, how to fix the code yourself(If I was able to find that place again) but it's much easier to point you at https://www.assembla.com/code/unifiedtrinity/git/nodes/master/Sources
There you can download the Trinity 1.7.3.8 (beta) and the Townrunissue should be fixed there. But I think rrrix stated somewhere that he'll probably release the .8 version officially soon. So You just might want to wait.

If you want to do it yourself either way, you can look up bandaid fixes in the Trinity 1.7.3.6 thread: http://www.thebuddyforum.com/demonbuddy-forum/plugins/trinity/131768-trinity-1-7-3-6-a.html

Also you should use the newer Quest Tools 1.3.11 ( http://www.thebuddyforum.com/demonb...4-full-questing-all-acts-complete-tested.html )
 
rrrix please fix HealthWell pls... can we just blacklist all of them?

and avoidance from savage beast charge dont work in 1.7.3.7
 
Kevin Spacey said:
rrrix please fix HealthWell pls... can we just blacklist all of them?

and avoidance from savage beast charge dont work in 1.7.3.7
Click to expand...
You can cancel the horrible Well-handling yourself by commenting out the whole procedure in Weighting.cs.
Just Ctrl-F "HealthWell" and comment out the whole paragaph.The bot will then ignore those.


?dit: rrrix explained it here:
http://www.thebuddyforum.com/demonb...y/133782-trinity-1-7-3-7-a-6.html#post1286007

(though the "!" fix does not work too well... :D deleting the whole thing does it best for me ;) )
 
zorked said:
Well I first wanted to tell you, how to fix the code yourself(If I was able to find that place again) but it's much easier to point you at https://www.assembla.com/code/unifiedtrinity/git/nodes/master/Sources
There you can download the Trinity 1.7.3.8 (beta) and the Townrunissue should be fixed there. But I think rrrix stated somewhere that he'll probably release the .8 version officially soon. So You just might want to wait.

If you want to do it yourself either way, you can look up bandaid fixes in the Trinity 1.7.3.6 thread: http://www.thebuddyforum.com/demonbuddy-forum/plugins/trinity/131768-trinity-1-7-3-6-a.html

Also you should use the newer Quest Tools 1.3.11 ( http://www.thebuddyforum.com/demonb...4-full-questing-all-acts-complete-tested.html )
Click to expand...

Thank you! This was very helpful. Thanks also for pointing out the latest QT. :)
 
FourOne said:
My usual Build for example isn't working, but only for Championpacks.
Click to expand...

I am sure this info is nothing new to all reading, but I wanted to hone in on a specific detail here. There is a synergy between locust swarm and bats... Locust Swarm will draw the mobs in and the kills will re-generate the mana needed to sustain the bat channeling (using both together is almost mandatory). The biggest problem I saw anyway was what everyone else saw, the WD will go OOM quickly because it doesn't understand the initial (huge) mana cost, times when it makes more sense to just "stay put and continue channeling". The logic to program here would need to determine if monsters are not only moving, but specifically moving towards the WD. So if the monsters are in range and moving towards the WD, keep channeling. The goal is for the WD to actually re-position him/her self as few times as possible, meaning the use of locust and deciding where to start channeling bats is probably the most tricky to program. Allowing the bats to continue channeling when not hitting anything, IF there are more monsters "on the way" heading directly to the WD, it is more efficient in many cases to just keep channeling and wait a few seconds than to stop and re-start channeling. If the bot was aware that monsters were specifically walking directly towards itself, it would result in a lot less initial mana costs for bats and more channel costs instead which is the issue.

As far as champion packs, elites and key warden, depending on what they have for elite affixes going OOM is probably just going to happen, there is not much you can do about it because they move so frequently and/or move you so frequently. The problem with that build you linked is that if the WD is OOM, there is no other usable offense. You might want to try adding Firebomb/Ghostbomb instead of BBV with the idea that when OOM there is still a way to attack (and generate life).
 
WackJagon said:
I am sure this info is nothing new to all reading, but I wanted to hone in on a specific detail here. There is a synergy between locust swarm and bats... Locust Swarm will draw the mobs in and the kills will re-generate the mana needed to sustain the bat channeling (using both together is almost mandatory). The biggest problem I saw anyway was what everyone else saw, the WD will go OOM quickly because it doesn't understand the initial (huge) mana cost, times when it makes more sense to just "stay put and continue channeling". The logic to program here would need to determine if monsters are not only moving, but specifically moving towards the WD. So if the monsters are in range and moving towards the WD, keep channeling. The goal is for the WD to actually re-position him/her self as few times as possible, meaning the use of locust and deciding where to start channeling bats is probably the most tricky to program. Allowing the bats to continue channeling when not hitting anything, IF there are more monsters "on the way" heading directly to the WD, it is more efficient in many cases to just keep channeling and wait a few seconds than to stop and re-start channeling. If the bot was aware that monsters were specifically walking directly towards itself, it would result in a lot less initial mana costs for bats and more channel costs instead which is the issue.

As far as champion packs, elites and key warden, depending on what they have for elite affixes going OOM is probably just going to happen, there is not much you can do about it because they move so frequently and/or move you so frequently. The problem with that build you linked is that if the WD is OOM, there is no other usable offense. You might want to try adding Firebomb/Ghostbomb instead of BBV with the idea that when OOM there is still a way to attack (and generate life).
Click to expand...

Its working for trash, but on Championpacks the bot just buffs himself and run a bit - I know its not the best build for botting...
 
WackJagon said:
I am sure this info is nothing new to all reading, but I wanted to hone in on a specific detail here. There is a synergy between locust swarm and bats... Locust Swarm will draw the mobs in and the kills will re-generate the mana needed to sustain the bat channeling (using both together is almost mandatory). The biggest problem I saw anyway was what everyone else saw, the WD will go OOM quickly because it doesn't understand the initial (huge) mana cost, times when it makes more sense to just "stay put and continue channeling". The logic to program here would need to determine if monsters are not only moving, but specifically moving towards the WD. So if the monsters are in range and moving towards the WD, keep channeling. The goal is for the WD to actually re-position him/her self as few times as possible, meaning the use of locust and deciding where to start channeling bats is probably the most tricky to program. Allowing the bats to continue channeling when not hitting anything, IF there are more monsters "on the way" heading directly to the WD, it is more efficient in many cases to just keep channeling and wait a few seconds than to stop and re-start channeling. If the bot was aware that monsters were specifically walking directly towards itself, it would result in a lot less initial mana costs for bats and more channel costs instead which is the issue.

As far as champion packs, elites and key warden, depending on what they have for elite affixes going OOM is probably just going to happen, there is not much you can do about it because they move so frequently and/or move you so frequently. The problem with that build you linked is that if the WD is OOM, there is no other usable offense. You might want to try adding Firebomb/Ghostbomb instead of BBV with the idea that when OOM there is still a way to attack (and generate life).
Click to expand...

Great summary - this gives me an idea on how to "fix" this. Feel free to keep typing and put into plain english for builds that the bot is currently retarded at. :)

WackJagon said:
Allowing the bats to continue channeling when not hitting anything, IF there are more monsters "on the way" heading directly to the WD, it is more efficient in many cases to just keep channeling and wait a few seconds than to stop and re-start channeling.
Click to expand...

This can be done... i'll dig.
 
I have a small suggestion for the next trinity

I keep getting random deaths in the start of the map, before my barb is able to buff battle rage and get enough fury to rend. I could increase the potion% but then he will just use way too much during the game so its a waste. I'm sure I'm not the only one who gets these but I think an easy fix would be to have a higher temporary potion% (lets say 80) but only for the first minute of the game. Or even 30 seconds if there isn't a town run that needs to be done.

It should be easy to do but I don't know how or where to add that.
 
or tp to the start on other location first and kill some destructible envirinments with simple attack

but i dint sure bot can this
 
Status
Not open for further replies.
Back
Top