0
Summary
This post is about the Inner Sphere Command Console and how it can possibly be implemented in a C3-like manner in Mechwarrior Online (MWO). In Battletech, the C3 computer allowed target sharing between linked mechs and this proposal attempts to replicate that functionality within the scope of what can be done within MWO.
Preface
Let me preface by sounding out my disappointment that while the Command Console and C3-slave units were available for the longest time in MWO they never actually saw any implementation until recently. When functionality was finally added to the Command Console it simply became a much heavier Beagle Active Probe (BAP) and never actually became anything like the C3 computer in the Battletech Lore (and the C3-slave unit has since disappeared from the inventory section). Below I will present my case for how Command Consoles could operate in a manner that makes them useful in MWO, without unbalancing the game too much, and without adding too many additional features into the game itself.
What It Would Do
At present, when a pilot's mech is capable of targeting an enemy mech, an empty red triangle appears over that target. These targets appear on the minimap and HUD of ONLY the mech that can 'see' them. It is only when the pilot presses the Target button (default: R) that the enemy mech is locked on to and a bold red triangle appears over the target. Such targets will then also appear on the minimap for all friendly mechs and are likewise targetable by those mechs despite being unable to 'see' them. The targeting is, in effect, 'shared'.
This is where the crux of this idea comes into play. Using a Command Console Datalink, members of a Lance will not only share information about actively target locked mechs (bold red triangle) but also share targeting information of untargeted mechs (empty red triangle) through what I shall call a Datalinked Network.
These empty red triangles will appear on the HUD and minimap of ALL Datalinked mechs, not just the mech with active line-of-sight. Thereafter any of the Datalinked Mechs can actively target lock (bold red triangle) any of the targets provided that at least one other mech in the Datalink Network is capable of detecting that target.
It is as if all the mechs in the Datalinked Network are sharing their 'eyes'.
In the above diagram the right most mech spots 3 enemy mechs. It actively locks on to Target C. In normal gameplay now all friendly mechs will 'see' Target C on their battlegrid, minimap, and HUD. With the Command Console Datalink however all the friendly mechs would be able to 'see' all three targets and is able to target lock any of them, provided the spotter maintains detection of the target(s).
Required Items
Two items would be required for the Datalink Network to work: -
i) The Command Console Master Unit (3 tons, 1 space, head only, *select mechs only)
ii) The Command Console Slave Unit (1 ton, 1 space, head only, any battlemech)
Once there is a Command Console Master Unit in any mech within a Lance, that lance can now benefit from Datalink Target Sharing. Slave units work in concert with the Master unit, but not in concert with other Slave units.
Several Conditions must be met for the Datalink Network's Target Sharing to work: -
i) At least one Command Console Master must be available and functioning within that Lance.
ii) Command Console Masters provide a Datalink Network for all units in the Same Lance provided those units either have a Command Console Slave Unit or a Command Console Master Unit.
* iii) Command Console Master units provide a Datalink Network connection for all other Command Console Master units in the Team (other Lances).
iv) Slave units do NOT share any Datalink with any other Slave unit when no Master unit is present.
v) Slave or Master units in mechs being distrupted by enemy ECM (low signal) no longer function as part of the Datalink.
* vi) Slave or Master units can be distrupted by PPC hits, in exactly the same way that ECM can be disabled.
In this diagram, the Master unit in Bravo Lance is not functioning, whether from battle damage or from being blocked by ECM. As such none of the units in Bravo Lance will benefit from Datalink priviledges, though Alpha and Charlie lance still do as their Master units are still working.
What It Would Not Do
Target Sharing Datalink does not benefit from any modules nor devices on linked mechs (BAP, ECM, Target Info Gathering, etc.) in any way. Any benefit from it is only derived if the spotter mech has those items/modules and is actively targeting the unit--as per normal gameplay. The one exception from this is the ability to spot shutdown mechs within range of a BAP, in that the group can 'see' any shutdown mech that a BAP equipped spotter detects.
Additional Effects
In addition to the above mentioned networking benefits, the Command Console Master Units also function as a TAG, and as a result are a selectable 'weapon' that can be 'fired'. Slave units do NOT function as TAG.
Final Words
I sincerely hope that this idea for the functioning of a C3 network within MWO is explored, and hopefully adopted. I think it adds a positive passive benefit for teams and players willing to sacrifice the tonnage required to activate the network. Additionally I feel there are sufficient ways to disable the network by taking out key enemy mechs, or removing the effect from play via ECM, PPC strikes or good old fashioned destruction.
This has been a rather long post, but I hope the idea is clear enough to understand and I thank you for taking the time to read it.
* - optional feature
Edited by Rawrshuga, 12 October 2020 - 06:55 AM.
