Settings for monster density and such

[freddieheh]

Hey! I'm a returning botter, but I havent botted in 3 seasons or so. Last time I botted I had to use adventurer coupled with trinity. Do I not have to do that any longer?

And i'm also trying to find settings for the bot to ignore non elites, the way you could back in the days. The bot would attack clusters of like 8 or so mobs, the settings look way different atm. Any ideas? Or am I just being stupid?

 

[tCLOCK]

Nope thats the new improved Trinity. Its garbage. More then likley your gonna have to edit the routine file. Keep searching for your class maybe someone has edited the files.

 

[TwoCigars]

Hey! I'm a returning botter, but I havent botted in 3 seasons or so. Last time I botted I had to use adventurer coupled with trinity. Do I not have to do that any longer?

And i'm also trying to find settings for the bot to ignore non elites, the way you could back in the days. The bot would attack clusters of like 8 or so mobs, the settings look way different atm. Any ideas? Or am I just being stupid?

There is an option in the GENERAL tab for TRASH MONSTERS. You can tell it to Attack or Ignore.

Adventurer is now included and maintained by the same developer as Trinity (xzjv). All things needed for them both to function are included. He has also removed the need for QuestTools for most current profiles by including the important parts in Trinity.

Settings for your specific build are found in the Routine tab of the Trinity configuration. These are the combat specific options that you can control.

If there is an option that is really slowing you down, please make a request with a proper explanation of why it's needed... Or specifically what the bot isn't doing right.

While the bot has been streamlined for ease of use, many people think they have lost tons of options. Realistically, many of the options were either: breaking builds, breaking bot logic, causing stuck issues, not working properly or were overridden by the combat routine so changing them actually did nothing. All of that lead to massive bug reports that were the result of tinkering with too many settings.

When the bot was streamlined, every single build was recoded and tested. The settings that are hardcoded are what was best for the META builds based on the bot's capability and logic.

Again, changes are still being made, and requests are welcome... But useless features and settings are not being added back wholesale just for the sake of having knobs to twist.

Let the Devs know what you need. :thumbsup:

Nope thats the new improved Trinity. Its garbage. More then likely your gonna have to edit the routine file. Keep searching for your class maybe someone has edited the files.

I have been in the tester group for awhile. Streamlined BETAs started for us nearly 5 months ago. The current hardcoded settings are the results of countless hours of research, coding, testing, suggestions and further testing.

As I have said repeatedly: If there is a specific setting or feature that's required for a class or build that will actually make it perform better, changes will be made.

As an example, "Elites Only" was removed initially from the BETAs. It was causing way more issues then it was worth. After testing and looking into requests, some classes do need an "Elite Only" setting (like LoNBomb), so you will now find those in the options for those builds. In short, many times the "elite only" option that used to be "available" in settings was overridden by the combat routine anyways. In other cases, it was just dumb to use it for some builds... The fact that the slider is only available in scenarios where it will actually function is a benefit to users. And where it's available it has been tested to ensure it's working appropriately with that particular combat routine.

When any specific setting is available (In Trinity config > Routine tab), you know that the bot is specifically programmed and tested for that feature to properly perform.

Sorry if this is an issue for you, but it's a bit petty to just say "It's Garbage" without any specific direction as to why you do not like it, or what specific changes are needed to make it better.

Afterall, there are over 800 files across 100+ folders in just the Trinity Plugin. The 60+ files in the Trinity > Routines folder were written from scratch just to make the user experience better in this streamlined version of Trinity. Be specific about needs or they will never be addressed.

 

[tCLOCK]

Ok so lvl 1550 LONsader on .237 would do gr70's anywhere from 3.5 to 4 minutes for speed exp. Could do gr85 all day even did a couple 87. Granted it wasn't perfect. When it did about 30 runs or so it would start acting stupid, getting stuck, getting to the end and doubling back..etc. But for the most part it did it's job.
Now same sader with no change in gear. Lvl is 1553, had to drop down to gr64 to complete in same amount of time. The thing I did notice is that it does alot of studdering when moving. Like very small back and forth jerky movements. When I try and push the higher rifts it just dies. Like there is no avoidence. When it does die, say from a sentry. It respawns and runs right back to where it died and dies again. I have gone over the settings and double checked. It does this for all classes. I started a new firebat WD and same thing. Dies respawns runs back dies again. Jerky movements, getting stuck which is mainly due to the pets getting in the way.

As far as crashing goes. It usually crashes during town runs or when it gets stuck and tries to restart a game. Sometimes it starts gets past the login screen then shuts down. Then when I try and restart I get the "max login try again in 30 sec" in a loop. I have done multiple uninstalls, re-installs. Completely removed .net framework and re-installed. Just short of a complete new Win 10 install or using another computer what else is there to do??

I know that going this route of making the interface simplier and using certain/same options for each class was or will be easier to trouble shoot but it almost seems by doing that, it made it harder to use. The default settings/gear might be great for you but what If I want to use some different combo of item/skills in my build?

 

[TwoCigars]

Ok so lvl 1550 LONsader on .237 would do gr70's anywhere from 3.5 to 4 minutes for speed exp. Could do gr85 all day even did a couple 87. Granted it wasn't perfect. When it did about 30 runs or so it would start acting stupid, getting stuck, getting to the end and doubling back..etc. But for the most part it did it's job.
Now same sader with no change in gear. Lvl is 1553, had to drop down to gr64 to complete in same amount of time. The thing I did notice is that it does alot of studdering when moving. Like very small back and forth jerky movements. When I try and push the higher rifts it just dies. Like there is no avoidence. When it does die, say from a sentry. It respawns and runs right back to where it died and dies again. I have gone over the settings and double checked. It does this for all classes. I started a new firebat WD and same thing. Dies respawns runs back dies again. Jerky movements, getting stuck which is mainly due to the pets getting in the way.

I haven't noticed a ton of jerkiness in my sader, but I am running other bots and don't always catch all of the problems when they happen. It's around 2k paragon, 300k thorns, toughness is a little weak. It speed runs through 75s with a couple deaths at most (not wearing illusory boots tends to be the issue). I would love for you to spend some time babysitting the bot to see where the shortcomings lie.

There has to be something causing the stuttering. I would assume its an issue with pathing, weighting, or avoidance. Pathing would be caused by it trying to get to somewhere it can't reach or trying to get to two exploration nodes at the same time. Weighting would be caused by two objects it's trying to reach that are equally weighted in the bot logic causing it to bounce back and forth. Avoidance would be sometime on screen that it causing the bot to avoid an area, with something inside of the affix or beyond the affix that the bot is trying to reach.

Weighting and Pathing issues are not as easy to diagnose without watching a lot. You can go to the Trinity tab on the DemonBuddy window and open the Visualizer to see what the bot is trying to do. It's pretty cool to watch, basically looking at what the bot is seeing and trying to do. An advanced, visual version of the log if you will.

In terms of avoidance, you can turn off all avoidance in the Trinity configuration and see if the stuttering goes away. It's important to know that all builds have an emergency health percentage that's around 40% health which may take over trying to keep you alive.

Another thing to keep an eye out for is your CoE rotation and see if the bot logic is keeping t around until that hits to kill a group of mobs that it should otherwise skip.

As far as crashing goes. It usually crashes during town runs or when it gets stuck and tries to restart a game. Sometimes it starts gets past the login screen then shuts down. Then when I try and restart I get the "max login try again in 30 sec" in a loop. I have done multiple uninstalls, re-installs. Completely removed .net framework and re-installed. Just short of a complete new Win 10 install or using another computer what else is there to do??

When you do a fresh install, does it work better on the maiden voyage? In terms of crashing and such?

You can alleviate the max login issue by closing your session manually at the BuddyAuth link on the top of the forum. Just login and close the session that is running.

This typically only happens when you're manually forcing the bot to close by ending the task or ending the process.

I know that going this route of making the interface simplier and using certain/same options for each class was or will be easier to trouble shoot but it almost seems by doing that, it made it harder to use. The default settings/gear might be great for you but what If I want to use some different combo of item/skills in my build?

I see where you're coming from as someone who has spent hundreds of hours testing and making mental notes of what worked best as well as what didn't work at all. After a long time doing this, I would read build guides with settings posted... Noticing that many posting setting modifications that actually changed nothing. People would go through 20 settings throughout Trinity, and there were really only 3 or 4 that made a difference. This wholesale misunderstanding lead to massive false reports. In the end, everyone being on the same settings will allow us to fix actual builds and hardcoded settings for the entire community.

I figure you have seen me post all of that before, but there is another option for you.

It's just a BETA at this point, but you can go to the Routine tab in Trinity. Choose Force routine. Select the Mr. Robot routine. It will give you access to pretty much everything.


Again, check on the stuttering problem and see what you can find out. Your findings might lead to fixes for the whole community. And thanks for taking the time to reply, feedback is important!