My first thought - and I posted this on their suggestion site - is that I love the automation stuff, but I want early-game automation to just be “beavers who’s job it is to sit and monitor a condition and then go do the thing they’re assigned to do when conditions are met”
You’d have to be strategic about the path from, say, a watchtower to the floodgates that need to be closed. You’d need to plan for staff for your infrastructure. If it don’t work well, you’d need to optimize for efficiency.
Little beavers doing semaphore or sounding horns to warn others to take action. Little bureaucrat beavers at the District Center turning on breeding pods when needed.
I think later on when you have stuff like bots, perhaps the beavers have scienced enough to have wifi floodgates. Feel like this was a missed opportunity for a more unique mechanic.
But hey the YouTube videos with the first “CPU in Timberborn” might be cool I guess
My first thought - and I posted this on their suggestion site - is that I love the automation stuff, but I want early-game automation to just be “beavers who’s job it is to sit and monitor a condition and then go do the thing they’re assigned to do when conditions are met”
You’d have to be strategic about the path from, say, a watchtower to the floodgates that need to be closed. You’d need to plan for staff for your infrastructure. If it don’t work well, you’d need to optimize for efficiency.
Little beavers doing semaphore or sounding horns to warn others to take action. Little bureaucrat beavers at the District Center turning on breeding pods when needed.
I think later on when you have stuff like bots, perhaps the beavers have scienced enough to have wifi floodgates. Feel like this was a missed opportunity for a more unique mechanic.
But hey the YouTube videos with the first “CPU in Timberborn” might be cool I guess
Perfect secondary function for foresters in their little towers.
Also, this suddenly gave me the idea of having wildfires during droughts.