I know, but can you imagine the QQ as a BoomJager dumps 40 PPFLD into a Madcat from 500m away? Or better yet, a GooseJager doing 30 PPFLD at 1200m, just because that crazy Locust Pilot is sitting on your Backside. Although, to be fair, the Locust would need to strip down to a Single Medium Laser to mount the C3, and you'd need a Chain of C3 running back to the Sniper, because I believe C3 was 800m range? Wait, just read that it has no Maximum Range. But sensors have a (base) range of 800m, so that could balance it, I suppose.
2
C3. We Don't Have It!
Started by Thunder Child, Jul 16 2015 12:17 PM
45 replies to this topic
#41
Posted 26 July 2015 - 03:42 PM
#42
Posted 26 July 2015 - 07:45 PM
I like this idea, I like it a lot. Combine it with the Command Console and I think the C3 Master would be a great piece of equipment. Personally I think the C3 Master unit should be treated like ECM, JJ, and now MASK, where only specific mechs can equip it but any IS mech can equip a C3 Slave.
Perhaps reduce the Master units buff radius from the TT standard of, what was it? 800m? To something like, say 400-500m, perhaps a bit more? I don't know, Just spit balling.
Perhaps reduce the Master units buff radius from the TT standard of, what was it? 800m? To something like, say 400-500m, perhaps a bit more? I don't know, Just spit balling.
Edited by Coralld, 26 July 2015 - 07:45 PM.
#43
Posted 26 July 2015 - 07:53 PM
Well, what they could do is have it only network the three nearest Slave Units. Because not everyone in a Lance will run it. Or, they could have it only network to people in your Lance (if equipped). The idea is that having a Master is a Huge investment in Tonnage and Crits, but you know for a fact your gonna get a Buff from it. The Slaves don't do anything by themselves, so if you run one and no one brings a Master, you've wasted a ton and a crit slot (not ALWAYS a big deal, but some builds would hurt). Command Mechs would suddenly be a thing though (and a priority target for the enemy team).
I like the idea of Master Units being a Hardpoint. In that case, I would actually be okay with them linking up with an Unlimited Number of Slaves, within say, 500m. ECM would counter C3 though.
I like the idea of Master Units being a Hardpoint. In that case, I would actually be okay with them linking up with an Unlimited Number of Slaves, within say, 500m. ECM would counter C3 though.
#44
Posted 26 July 2015 - 07:57 PM
Another fabulous mechanic or feature that COULD be in this game if its development wasn't firmly seated in incompetence.
#45
Posted 26 July 2015 - 08:00 PM
You must forgive the majority of MechWarrior players. They are used to the other MechWarrior games that implemented C3 strictly as a way of sharing targeting info, so their only experience with it is in that context, which is why you see folks saying we already have C3 in the game.
But this isn't, "BattleTech: Online." It's cool you know all the stuff down to where you can point out inaccuracies in Sarna, but no other MW game has implemented C3 in the way it is in TT, and it has always been about the shared targeting data in MW games.
So for all intents and purposes, when it comes to previous MW games that didn't have shared targeting, and implemented the C3 masters and slaves as a way of gaining access to shared targeting, I think it's a perfectly reasonable argument in the context of this being MechWarrior (not Tabletop), to say that we have C3 in MWO.
But this isn't, "BattleTech: Online." It's cool you know all the stuff down to where you can point out inaccuracies in Sarna, but no other MW game has implemented C3 in the way it is in TT, and it has always been about the shared targeting data in MW games.
So for all intents and purposes, when it comes to previous MW games that didn't have shared targeting, and implemented the C3 masters and slaves as a way of gaining access to shared targeting, I think it's a perfectly reasonable argument in the context of this being MechWarrior (not Tabletop), to say that we have C3 in MWO.
#46
Posted 26 July 2015 - 08:02 PM
Thunder Child, on 26 July 2015 - 07:53 PM, said:
Well, what they could do is have it only network the three nearest Slave Units. Because not everyone in a Lance will run it. Or, they could have it only network to people in your Lance (if equipped). The idea is that having a Master is a Huge investment in Tonnage and Crits, but you know for a fact your gonna get a Buff from it. The Slaves don't do anything by themselves, so if you run one and no one brings a Master, you've wasted a ton and a crit slot (not ALWAYS a big deal, but some builds would hurt). Command Mechs would suddenly be a thing though (and a priority target for the enemy team).
I like the idea of Master Units being a Hardpoint. In that case, I would actually be okay with them linking up with an Unlimited Number of Slaves, within say, 500m. ECM would counter C3 though.
I like the idea of Master Units being a Hardpoint. In that case, I would actually be okay with them linking up with an Unlimited Number of Slaves, within say, 500m. ECM would counter C3 though.
I think it should buff everyone with a C3 Slave. As you said, someone with a Master unit would be a prime target so its best to get the most bang for your buck if you can connect as many people in as possible. Needless to say, the C3 network would be most seen in group drops and CW and not so much in PuG Landia but I'm ok with that.
As for enemy ECM being an issue, well, make sure you have guys on your team with ECM of your own and BAP.
As for my 500m effective range for C3 suggestion, well, as I said, if 500m is to short, increasing it wouldn't be to much of an issue. Thats assuming if the base TT range of 800m is to much.
Edited by Coralld, 26 July 2015 - 08:21 PM.
3 user(s) are reading this topic
0 members, 3 guests, 0 anonymous users