I can not I can't find AdvancedSettings in Trinity。

[terrencechi]

I can not I can't find AdvancedSettings in Trinity。

 

[tCLOCK]

New version got rid of them. Supposed to make it easier.

 

[Zuzek]

bad idea

 

[tCLOCK]

bad idea

Why ??

 

[TwoCigars]

bad idea

Why ??

My inquiry is the same as tCLOCK. Why is this a bad idea Zuzek? What feature is missing that you need?


I think that there is a failure to comprehend the underlying infrastructure that makes DemonBuddy able to perform complex interactions without directly interfering with the game files. There are inherent limitations using such a method. A method specifically designed to keep accounts as safe as can be expected.


Since BETA releases started rolling out 4+ months ago with settings streamlined, this sentiment has been repeated over and over again:
"Where are all the options?"
xzjv always responds:
"What setting is missing and why is it necessary?"

The typical response is filled convoluted theories that are to be expected from people who have not gone through the structure of the bot on their own. It is not their fault that they do not have this knowledge, but forcing the subject while lacking information or specific need leads nowhere.

However, when a well formed thought is expressed on a specific feature backed by actual testing and not unfounded theory, it is tested and added.

The short version of why they were removed:

• You couldn't actually change some of them: Pick your favorite build. The META is to use certain gear and skills in a certain rotation for efficiency. Therefore it was imperative to hardcode the "best" settings for the bot on the META skills. Therefore the exact settings you wanted to modify were often the exact same skills that you couldn't change without modifying *.cs files. This lead to confusion and bug reports.
• Settings could break the bot: You have a one word description in a menu. Most of us have a layman understanding of how we think that setting should affect the bot performance. Without understanding all of the possible interactions of that setting with thousands of lines of code. Again, this lead to confusion and bad bug reports.
• Archival settings: Settings that had always been there so they were left in even if they performed no actual function.
• Ease of Use: When I started here, you had to spend days researching just to learn how to use it: what profiles and plugins interacted well with each other, checking daily for updates. Going through guides to get the right settings only to find out that only worked with X plugin while using Y profile. Then reading through hundreds of posts to see how these settings, profiles and plugins had to be amended on your own. Now it is done for you. Pick what you want to do. Hit start.
• Efficiency for bot Assistance and Development: Removing bogus settings and streamlining provides more time for actual improvements and fixes to actual bugs. 90% of the fixes provided for "broken bots" in the past were fresh installs. A fresh install just resets whatever the user had done to the bot. Coincidence? I think not.
• People who are testers and developers were polled. They agreed it was the overall best way to move DB into the future.

In summary:
Anything that was needed has been added over the last 4 months of development. Anything that is still needed can still be added back provided there is an actual benefit other than fondling a slider.
During that process, many settings that were removed because they were broken [but were needed] were actually fixed and re-introduced.
Now that we are all going to be using the same settings on the same gear with all of the crap removed, bugs are easily replicated and fixed quickly. Take a look at the BETA log in the Discord channel if you disagree.
The entire infrastructure of the routines has been redone from the ground up. This lead to a massive amount of fixes and simplification that would not have happened otherwise.
Routines and other hardcoded things are now easy to find, understand and modify via the *.cs files. People who have the knowledge to do so also typically understand the interaction of doing so. This leads to fruitful tinkering rather than lost newbies who can't figure out why it worked last week but not today.



I wrote some longer explanations Here:
https://www.thebuddyforum.com/demon...thumbs-2-55-243-trinity-guys.html#post2315133
and here:
https://www.thebuddyforum.com/demon...thumbs-2-55-243-trinity-guys.html#post2315261
...and many other places if you want to search my posts in the past 5 months.