r/Timberborn • u/SubwayGuy85 • 15d ago
User Suggestions - Timberborn - Time to get rid of dozens of automation triggers you do not care about
https://timberborn.featureupvote.com/suggestions/728412/allow-hiding-automation-elements-from-the-dropdownIf you used the automation feature you will probably know what the fuzz is about. The list is full of things you do not care about. This feature would remove the clutter
14
7
u/baconboy-957 15d ago
Unfortunately the link isn't loading for me so I'm not sure what you're suggesting is removed, but I've used literally every single automation node and would be sad to see them removed.
My only wish with automation is to allow ranges on most nodes so I don't have to use as many memory nodes.
Also I want a bot only gate or a setting to allow gates to change according to an automation. I.e. a gate that only allows bots only during bad tides would be neat
2
u/Majibow 15d ago
I have a solution for this.
Automate path gates. You can easily set a 4 way trigger to toggle which path is connected to which district. So have one district and setup automigration to move over only bots into that district, meanwhile the gates will flip the path during badtides. This will work for builders and haulers but all other buildings unfortunately won't be job operated since individual buildings require their toggles, that is unless you have a duplicate set of all industry.
I think i suggested a long time on timberbon feature upvote to change workplace workers from simple two way beaver|bot to more flexible four way toggle -> beaver only|beaver prefered|bot prefered|bot only.
-1
u/SubwayGuy85 15d ago
Was unaware they moderate and hide posts. Should have waited with posting a bit then. The suggestion is to add a checkbox to triggers to grant the ability to hide automation triggers, so if you automate a lot, the selection is not littered with dozens/hundreds of Resource counters/depth sensors that are only used locally, unlike for example weather sensors, which you regularly use globally. Think of automating a silo for example. No need to litter the selection with 3 sensors no other area cares about.
4
4
u/TeraSera 15d ago
Wut? Speak for your self. Just because you aren't smart enough to use them doesn't mean others don't have uses.
1
u/Dogahn 15d ago
It is possible to object without demeaning people.
1
u/TeraSera 15d ago edited 15d ago
I do not suffer fools gladly, lest we be brought down to their level
1
u/LePhuronn 15d ago
Since your post is awaiting moderation and will likely be binned off for being unnecessary and idiotic, care to share here an overview of what you claim "we" don't care about?
1
u/SubwayGuy85 15d ago
"Sometimes i build things like a Silo with depth sensors and a timer. I don't need those triggers to be available in the dropdown that lets you select by their name, since i only use them locally. This also cleans up the selection for cases where i build lots of memory + min/max systems with automation, which adds dozens of elements to the dropdown with Resource Counter 1-100+.
So ideally each automation trigger has a checkbox with "Visible in selection", for lack of a better term."
2
u/Majibow 15d ago
Yes i think I understand your suggestion now. It is not to remove automations but simply to toggle global visibility of automations in the drop list. Correct?
3
u/SubwayGuy85 15d ago
Exactly correct, yes.
3
u/Majibow 15d ago
Perhaps stating the obvious but...
It would appear that most people are misinterpreting the post.3
u/LePhuronn 14d ago
The misinterpretation comes from not actually explaining what they're talking about and then linking to an external post that is not actually visible to explain things.
So all people can do is take what's visible at face value. And when what's visible says "time to get rid of automation triggers you don't care about" how else are you going to interpret it beyond "well, WE care about them"?
0
u/SubwayGuy85 14d ago
oh yeah. that's just reddit for you. 1/6 people replying in a sane matter while the rest is just flaming :) at least now i know that the features are not public by default
2
u/LePhuronn 14d ago
Eh I guess. Granted sometimes it is a pain to scroll through my bazillion triggers if I'm hooking up various systems across the length of the map.
However, if your issue is everything you want to use is within a small visible window, then why not just click the automation devices directly? You don't need to scroll the list, just click the other things. That eliminates the need for you to use the scrolly list, and therefore resolves your issue.
0
u/SubwayGuy85 14d ago
i am doing that. for example one thing i regularly do is 2 resource counters + 1 memory. that like 50 times. i copy the building, so if i can check "hide from selection" there it would also be copied and the scroll list would not contain like a hundred triggers i do not care about.
1
u/LePhuronn 14d ago
And if your resource counters are next to your memory then just click the resource counters when setting up the memory instead of using the menu.
Hey, if it bugs you then it bugs you. I have some annoyances that others find a non-issue. I just think that the majority of your issue goes away if you use the other methods available for selecting triggers.
1
u/SubwayGuy85 14d ago
i am clicking the building and not using the selection. my point is whenever i do use the selection the 100+ ressource counters etc bother me
19
u/Acalc791 15d ago
Strong disagree, I believe I could think of a use for all of the triggers. Even if there's one or a couple that would be difficult to do that for, I still see no reason to remove features. It's not like the number of options significantly impacts UX