Grid Sage Forums
Cogmind => Ideas => Topic started by: DDarkray on November 22, 2017, 07:36:51 AM
-
One of the nasty things about playing with combat build is that a squad of enemies can spread information to another nearby squad, resulting in even more enemies marching toward your position. This is one of the most difficult parts of combat because you won't know if more robots will be coming your way or not, unless you have a way to detect enemies via sensor array, etc. This mechanic is also difficult for new players because without prior warning, loads of enemies appear to come "out of nowhere". With no knowledge of additional incoming forces, players will feel overwhelmed almost instantly, which may appear to feel "unfair".
So what I'm proposing is that when an enemy combative squad is signaling to another enemy squad, a log message should appear to say it. As of now, no message appears.
Visible signs of incoming enemies have shown to be useful, alerting players ahead of time and thus, allowing you to prepare yourself before the army comes. For example, watchers and operators give off distress signals when a squad is close by. Alarm traps, machines tracing you, blowing up garrisons, etc. also give off alert signal so that players will always have time to prepare themselves. They won't have to guess if more enemies are coming or not.
Would it be a problem to have a similar log message in combative squad-to-squad signaling case? From a stealthy flight build standpoint, your sensor array already gives you enough information about the surround robots, so the impact is minimum. Therefore, it's only a real benefit for combat build.
Transmission jammer also feels a bit more useful because in this case, you can actually see if it's jamming the squad-to-squad communication signal or not. However, its actual effect isn't changed at all.
-
It would probably spam the log a lot. I think that was one of the reasons why it wasn't done like that.
Perhaps a visual indicator on the map could be added? Something subtle? Maybe a sound too.
-
I can see it end up being spammy, but we can always revisit this after I implement the already-discussed visible distress signals.
-
That's fine, just throwing the idea up here. ;D