suggestions

Just a QoL improvement, possibly.

Just have noticed a clan that has all its bots not gaining energy and thought "too much of a hassle."

Personally, I'd probably still never use the option... but seems like if it's a feature in game to allow bots to not gain energy then it would make sense for you to just flip that switch for a whole clan.

+1

Nice option to have if you want to put a clan dormant or whatever instead of declanning it or having to toggle every bot individually.

At the same time I'd really like the accept all button to be implemented. Screw having to accept 20+ bots ONE BY GOD DAMN ONE. Hurry it up Ender. Just add the dang check box so we can do it.

I like both ideas, Zal & Mal. Let’s get it crackinnnnnnn

Bumping to add my +1

All the ideas in this thread would be big wins for everyone :)

+1

tl;dr: No plans to add clan-wide settings that override bot-specific settings, but long-term there may end up being bulk bot setting management tools.

Something like this makes sense from the perspective of "I own many bots and want to manage them centrally rather than logging into each of them individually to change a setting". The common case is probably something like a dumper clan where all the bots are owned by the same person/entity and you want to be able to toggle energy generation for the entire clan more easily than you currently clan.

I think where it gets tricky is when you have a clan where the bots are owned by different people, i.e. a "real" clan. In that case, should the clan-wide setting always take precedence over the bot-specific setting? Who should be able to change the clan-wide setting, only the clan owner? Or a configurable rank via the permission matrix? Or should individual bots/players retain the ability to manage their own bot's setting independent of the clan-wide setting? My point isn't that these questions can't be answered (they can) - in my day job, I work in enterprise software and these are the kinds of considerations you end up having to work through with complex permission structures and hierarchical relationships of settings where one value can override another, but only in the certain cases, and in a different way in other cases, etc. Although each individual knob may seem reasonable on its own, in aggregate these kinds of setups can quickly get complex and difficult to understand from a user-facing perspective, so I'm hesistant to go down this path.

All that said, the core need ("I manage many bots and don't want to log into each individual to perform some action") still makes sense to me and the good news is that I think I see an alternative path forward (albeit longer-term) that is probably ultimately better in the end. Some of you may remember the Soliciting input: Managing many bots thread from (exactly, interestingly) 6 months ago. I think this kind of functionality would best fit into this new account structure. As I mentioned though in the recent Clan competition changes for June + looking ahead thread, my current focus is mainly on the clan competition, and the account structure changes (if they happen), would be quite complex and so could take awhile to land. That's still the rough direction I have in mind for some point down the road, so stay tuned - but I want to manage expectations on that front.