Grid Sage Forums

Cogmind => Ideas => Topic started by: Joshua on November 15, 2017, 05:44:14 PM

Title: Disable non-stacking utilities
Post by: Joshua on November 15, 2017, 05:44:14 PM
eg., if I have two core analyzers equipped, disable one when I activate the other one so it's clearer they will not both have an effect at the same time. (I know I could just read the description more carefully, too.)

There could also be a warning when equipping the second one that it will be useless, if it's not a higher / better level than the already equipped one.
Title: Re: Disable non-stacking utilities
Post by: DDarkray on November 15, 2017, 07:06:22 PM
I would like this feature too. It doesn't make sense to have multiple <no_stack> utilities at the same time, and it becomes a disadvantage if they happened to be energy-hungry utilities (e.g. multiple focal shields).
Title: Re: Disable non-stacking utilities
Post by: zxc on November 15, 2017, 11:55:37 PM
Decent idea. And ensure that the highest level one is the active one unless manually adjusted.

I guess one downside is that if the active one gets shot off, you need to activate the other.
Title: Re: Disable non-stacking utilities
Post by: DDarkray on November 16, 2017, 10:25:40 AM
Non-toggleable processor like Target Analyzer could automatically activate the next one in your equipment. Toggleable utilities could remain inactive, although there could be an option that can let you toggle it automatically.

My only concern is that new players may find it confusing at first until they realize that some parts are <no_stack>. One idea is that such information could be relayed through tutorial message.
Title: Re: Disable non-stacking utilities
Post by: Kyzrati on November 19, 2017, 04:22:13 AM
It's possible but I don't know if it'd be worth the work to implement something like this as it's mainly a teaching tool. Once you have an idea of what doesn't stack, it's unlikely you'll be wasting multiple slots on duplicate non-stackable utilities...

I mean yeah we can add another tutorial message when two stackables are equipped and active at the same time, but I don't think it needs to be a whole new automated management feature.