Trinity 2.55.666 Beta - Crusader is weaker now compared to live trinity

[boynextdoor]

Great job simplifying the overall trinity experience for new comers.

However, in simplifying the user experience for new users you have gimped the experience of hardcore botters.

You no longer have the option to tell trinity to ignore all trash and just kill elites.

Since xp was moved to the close of the rift it is no longer beneficial to sit in a rift killing trash as long as possible, that was good season 6 but won't be good anymore now and going forward.

With the new beta I went from 2.5-3 minute 74s in season play to 5-6 minute clears because I can no longer tell the bot to just kill the elites and ignore the trash. Pretty awful really.

Feature request: How about an option to wait for coe only on the greater rift guardian? The guardian is the only mob that wont die in one bombard rotation off coe. Everything else does if you're botting properly.

 

[boynextdoor]

Also the item pick up rules arent as effective either.

There was something special about saying only pick up yellow rings or blue amulets. Reason being maybe you were down on certain mats, wanted to pick them up but didnt want to stop every single time a yellow or blue hit the ground. You would tell the bot to pick up the jewelry since jewelry doesnt drop as often. You still get the benefit of increased mats but you dont have to deal with the bot stuffing the stash too early and having to leave a rift to port to town.

 

[ysj1995]

Great job simplifying the overall trinity experience for new comers.

However, in simplifying the user experience for new users you have gimped the experience of hardcore botters.

You no longer have the option to tell trinity to ignore all trash and just kill elites.

Since xp was moved to the close of the rift it is no longer beneficial to sit in a rift killing trash as long as possible, that was good season 6 but won't be good anymore now and going forward.

With the new beta I went from 2.5-3 minute 74s in season play to 5-6 minute clears because I can no longer tell the bot to just kill the elites and ignore the trash. Pretty awful really.

Feature request: How about an option to wait for coe only on the greater rift guardian? The guardian is the only mob that wont die in one bombard rotation off coe. Everything else does if you're botting properly.

I also think alike.
This is big problem for firebird achon build.
Despite set the cluster size to 25 bots always try to kill high hitpoint trash mobs.

 

[TwoCigars]

Also the item pick up rules arent as effective either.

There was something special about saying only pick up yellow rings or blue amulets. Reason being maybe you were down on certain mats, wanted to pick them up but didnt want to stop every single time a yellow or blue hit the ground. You would tell the bot to pick up the jewelry since jewelry doesnt drop as often. You still get the benefit of increased mats but you dont have to deal with the bot stuffing the stash too early and having to leave a rift to port to town.

I had posted previously and spoke with xzjv about the usage of jewelry only for pickup options. I mainly wanted it to keep the bot from making too many town runs.

xzjv might add back in a selection for jewelry only if there is enough need for it, but I think there are many valid solutions in it's current iteration that negate that want.

However, this was done for a reason. When you start to look at all of the options that were available in the old settings, you see a trend. Many options were added over time to appease requests and to allow for testing.

As time went on and builds changed, many of these options were either:

• Not working as people assumed (lack of understanding how the settings affect bot behavior),
• not serving any useful purpose and weren't worth the time of changing and testing,
• or flat out didn't work because your specific build had special hardcoded settings which would override your configuration of certain settings.

At some point, a cleanup was needed. Get rid of everything, hardcode the best settings to prevent issues and make the user experience streamlined.

Honestly I don't want to type a novel here, but you can get the idea by reading my reply here:
https://www.thebuddyforum.com/demon...thumbs-2-55-243-trinity-guys.html#post2315133

In short, limited configuration means less time trying to track down how someone set their bot up wrong vs. dealing with actual global issues.



In response to how to deal with it in the current bot iteration...

How about just determining if your objective is

• speed runs to get DB or upgrade gems faster and turn off all basic item pickup
• material farming and have all the item settings on, turn on the material conversion to convert yellow material to white and blue.
• seasonal journey speed runs [T13 rift in under 4 minutes] and turn all items off until you get the achievement

I think those are all valid solutions that I have been using since testing the new .6xx BETAs.

 

[boynextdoor]

thats all well and good. but doubling the amount of time it takes to do a run just to make the bot easier defeats the whole point of using this bot. double the time is half the xp, half the loot and half the shards. A stickied post with a set of xml files for each and every build as well as a corresponding link to a diablofans and d3planner link would do the same thing the devs are trying to accomplish.

have someone copy a build, see how the gear is rolled, set their character up and then use the import function for a min / maxed bot is still better than having it be plug and play but you lose half your botting efficiency.

 

[TwoCigars]

thats all well and good. but doubling the amount of time it takes to do a run just to make the bot easier defeats the whole point of using this bot. double the time is half the xp, half the loot and half the shards. A stickied post with a set of xml files for each and every build as well as a corresponding link to a diablofans and d3planner link would do the same thing the devs are trying to accomplish.

have someone copy a build, see how the gear is rolled, set their character up and then use the import function for a min / maxed bot is still better than having it be plug and play but you lose half your botting efficiency.

The idea of getting everything streamlined so we are all using the same settings was introduced so that the community could diagnose issues and global fixes could be put into place.

As I was testing and made suggestions or reported issues, they were quickly fixed and that is the goal.

Is "Elite Only" the only feature that is missing and causing this lag in efficiency? Can you babysit the bot and make sure there is also not something else going awry? Might as well find all of the kinks and fix them.
IE: CoE rotation on Elites only? RG Only? Ignore all trash when steed charge is off cooldown? etc.


If you would like to tinker with other settings, go take a look at the cusader combatbase and the bombardment build:
DB > Plugins > Trinity > Routines > Crusader

 

[xzjv]

I am reluctant to add an ignore trash setting globally because most of the time for most users it will cause problems in the form of getting stuck. You need either illusory boots or a skill equipped that allows you to walk through mobs (or charge/dash/teleport with very high frequency) and a routine that uses them for movement. So the default of attack trash up to cluster size except when blocked and a few other special situations i think makes the most sense.

You seem to be using LoN Bombardment so i will add the boss CoE option and a weighting bypass for trash specifically for that routine.

 

[ysj1995]

I am reluctant to add an ignore trash setting globally because most of the time for most users it will cause problems in the form of getting stuck. You need either illusory boots or a skill equipped that allows you to walk through mobs (or charge/dash/teleport with very high frequency) and a routine that uses them for movement. So the default of attack trash up to cluster size except when blocked and a few other special situations i think makes the most sense.

You seem to be using LoN Bombardment so i will add the boss CoE option and a weighting bypass for trash specifically for that routine.

I am a manager of Autufollow users blog .
Most of blog members still use Trinity 237.
We know Trinty 667 is very good but 667 zDPS monk spend many time to kill high hitpoint trash mob.
(We set cluster size to 25)
Would you add weighting bypss option for zDPS monk, please.
We always thank for your effort.

 

[boynextdoor]

I am reluctant to add an ignore trash setting globally because most of the time for most users it will cause problems in the form of getting stuck. You need either illusory boots or a skill equipped that allows you to walk through mobs (or charge/dash/teleport with very high frequency) and a routine that uses them for movement. So the default of attack trash up to cluster size except when blocked and a few other special situations i think makes the most sense.

You seem to be using LoN Bombardment so i will add the boss CoE option and a weighting bypass for trash specifically for that routine.

Nice, I'll have to reinstall the beta trinity and give it a shot.

Which LoN sader profile should I be using going forward, I just defaulted to phelon's because that was the only one I recognized.

 

[xzjv]

Nice, I'll have to reinstall the beta trinity and give it a shot.

Which LoN sader profile should I be using going forward, I just defaulted to phelon's because that was the only one I recognized.

The one you're using, adapted from Phelons code, is the only one available specifically for LoN Crusader right now.

If people make new routines i am happy to include them with the official package. In that situation you could use the 'Force Specific Routine' option to select them.

 

[Cheeseburgerz]

I dunno what to say even with the latest beta builds, My LoN sader has gone from stomping GR 80's in 6 mins with the bot in live to not even being able to complete GR 77's in time... even dying to t13 Belial when Live stomps him in seconds... dafaq

I do GR 85's sub 7 mins self play so it's not My toon. and the build seemed to always work well with the bot before.... i dunno sad panda....

Me in the same room with bot running

 

[boynextdoor]

I dunno what to say even with the latest beta builds, My LoN sader has gone from stomping GR 80's in 6 mins with the bot in live to not even being able to complete GR 77's in time... even dying to t13 Belial when Live stomps him in seconds... dafaq

I do GR 85's sub 7 mins self play so it's not My toon. and the build seemed to always work well with the bot before.... i dunno sad panda....

Me in the same room with bot running

yeah just stick with Trinity Version: 2.50.237

Next season im gonna try the ros bot lon monk. those guys in nonseason are getting 350b/hr at paragon 3k. Had some clan mates run it late last season and were getting 250/hr. So roughly equivalent to sader but its something different and it also farms you gear for zmonk and 4 man dps monk as well as solo monk and solo lon DH.

 

[xzjv]

My LoN sader has gone from stomping GR 80's in 6 mins with the bot in live to not even being able to complete GR 77's in time...

Would you mind running some comparisons for me; run some grifts on release Trinity, and do the same test on latest beta (currently .669). And post the logs, your settings exports, rift stats, maybe a video or watch them and see if you can identify any difference. (with targeting, and avoidance logging enabled in trinity advanced settings). I'm on discord all the time, feel free to contact me there.

 

[Cheeseburgerz]

Would you mind running some comparisons for me; run some grifts on release Trinity, and do the same test on latest beta (currently .669). And post the logs, your settings exports, rift stats, maybe a video or watch them and see if you can identify any difference. (with targeting, and avoidance logging enabled in trinity advanced settings). I'm on discord all the time, feel free to contact me there.

Yeah best kind, I'll do so fresh runs tomorrow after work , watch on both, maybe do a video and give you the logs and stuff.

Running .669 for a few hours today and does seem to be doing better however.

For LoN saders specifically, Is there anyway to get the bot to burn iron skin and bombardment every time CoE is up on physical regardless of what it's doing while it's running from champ pack/elites/? I think this would greatly speed up up clear times as one bombardment usually flattens a entire screen of trash mobs when it's up which is worth a fair bit of progress xp at most times(2-6%) as there's plenty of times while the bot is skipping trash CoE is up on phy and bombardment and iron skin as well. shame to waste it when it's up seeing how it can clear a entire screen of trash on the way to the next pack/shrine if thats possible. I find Myself using both iron skin and manually as the bot is running when CoE is up like this greatly speeds up the grift. so might as well be dropping bombs... not to mention the times this would save wasting a CoE rotation when the bot is avoiding sometimes as well.

edit: also anyway the bots OCD behavior with straight up abandoning elite packs in favor of opening doors be toned down? seen this thing get a pack down to almost the kill shot and then just run off opening doors ,then just forgetting about the pack carrying on with the rift too many times to count. i partly blame the saders insane speed.. but I digress.. elites above all.. never mind the doors.. open them when the killins done...

also the wait time on champ/elite grotesques need to be bumped smidgen as most times it won't wait long enough to get the orbs and move on. once again I partly blame the saders speed..

 

[Angusm]

Dont know if that would be a good Idea Cheese ... Cause i can see you getting to an Elite pack while Bombardment is on CD ... Therefore slowing a lot your progress
Not worth it to spend it on Trash i think

 

[boynextdoor]

Latest beta trinity has finally beaten out the older trinity by ~5 bn/hr

Big thanks to the DB team for continuing to work on crusader and listening to our feedback.


[Adventurer][Rift] Runs count: 113
[Adventurer][Rift] This run time: 0:05:14
[Adventurer][Rift] Average run time: 0:05:33
[Adventurer][Rift] Best run time: 0:03:19
[Adventurer][Rift] Worse run time: 0:08:51
[Adventurer][Rift] This run XP Gained: 24,925,329,847
[Adventurer][Rift] This run / Hour: 285,168,676,078
[Adventurer][Rift] Total XP Gained: 2,363,229,063,462
[Adventurer][Rift] Total XP / Hour: 225,795,583,189
[Adventurer][Rift] Best XP / Hour (single run): 471,439,930,837
[Adventurer][Rift] Worse XP / Hour (single run): 17,407,038,444
[Adventurer][Rift] Best XP / Single run: 28,883,091,567
[Adventurer][Rift] Worse XP / Single run: 1,725,746,277

 

[Cheeseburgerz]

Dont know if that would be a good Idea Cheese ... Cause i can see you getting to an Elite pack while Bombardment is on CD ... Therefore slowing a lot your progress
Not worth it to spend it on Trash i think

That would be impossible with LoN To not have the cooldown up. Currently when played right Lon sader should always wait for Coe to be up before casting bombardment and iron skin to maximize damage:. The bot currenlty does this anyway When Getting to a elite pack if the bot is set to wait for coe like it should...

What I'm suggesting is the bot always hit bombardment and iron skin while its moving only when Coe is ready for phy as to not interrupt the cycle.. This would Just take advandge of the free kills it offers when it is up... cause its up a lot in between packs on Coe physical .This will not result it in ever not being ready because your sader should have at least a cdr of 62% to have bombardment synced with phy on Coe.. The only thing it's doing now is wasting output...

What I'm saying here is the bot should be dropping bombs like its fighting a lite pack all the time but only when Coe is on phy.

 

[boynextdoor]

That would be impossible with LoN To not have the cooldown up. Currently when played right Lon sader should always wait for Coe to be up before casting bombardment and iron skin to maximize damage:. The bot currenlty does this anyway When Getting to a elite pack if the bot is set to wait for coe like it should...

What I'm suggesting is the bot always hit bombarmnet and iron skin even while its moving when only Coe is ready as to not interrupt the cycle.. Just still take advandge of the free kills it offers when it is up... cause its up a lot in between packs....This will not result it in ever not being ready because your sader should have at least a cdr of 62% to have bombardment synced with phy on Coe.. The only thing it's doing now is wasting output...

Youre correct. However, the current nerfs to xp gain make it so your best xp/hr come from closing rifts as fast as you can as opposed to waiting in them as long as you can. What you're suggesting is a good idea, however if you're in a rift for more than 3-5 minutes you're getting less xp than you could be if you just blasted elites only and kept moving as fast as you can (I.E. not waiting for coe except for rift guardian and playing a rift level where you can one shot elites off coe).

 

[Cheeseburgerz]

Well see that's why I want it as a option simple as wait or not wait for Coe... Not when it's off and your doing speed runs. I'm not talking about xp....I'm about Clear times when wait for Coe is on when pushing higher rifts. Lol sure this isn't going help if you haven't got wait for Coe on...