Jump to content

C3 Master, Slave, & Improved. . . What Roles Should These Computer Play In Mwo?


8 replies to this topic

#1 Hawk819

    Member

  • PipPipPipPipPipPipPipPip
  • Colonel
  • Colonel
  • 1,865 posts
  • Location666 Werewolf Lane. Transylvania, Romania Ph#: Transylvania 6-5000

Posted 03 November 2016 - 02:58 PM

What role should the C3 computer system play in MechWarrior Online?

For me, it has to play as intended, provide information for Inner Sphere Units. Just the way the game mechanics describe. It's probably why we don't have the Inner Sphere OmniMechs at this time. Cause Russ and Co., can't figure out how to utilize them, and how they should interact with such components like the Command Console and the Cyclops' Battle Computer.

I believe that once this is done, the Clans will lose the advantage that they now enjoy in Fatcion Warfare.

True. The Clans have the Targeting Computer, and I'm not sure how many Clan Players are using the computer at this time; I can only speculate. I do know that I'm using the TC with both Night Gyr C and the War Hawk variants that have the computer already in their builds. Possibly a few other Clan `Mechs.

However, here's the conundrum: Can Inner Sphere Targeting Computers, if applicable, be used with C3 Computers? Or should they each have separate values to the game?

IMHO, I say no. They should be separate entities. The C3 used for both quick targeting and weapon firing capabilities the same way as the Clan Targeting Computer is used, and improved target acquisition, just like the 360* Target retention Module and Seismic Sensor. When used with both modules, the C3 computer adds a % more to all electronic modules like the Retention and Seismic, etc.

Targeting Computers for the Inner Sphere, should act in the same manner as Clan Versions, but not give bonuses to modules. In this manner, one does better than the other. That way the roles will not be so confusing.

What does the community think?

Let the debate begin. <o

Edited by Hawk819, 03 November 2016 - 03:01 PM.


#2 The Zohan

    Member

  • PipPipPipPipPipPip
  • The Tracker
  • The Tracker
  • 408 posts

Posted 03 November 2016 - 03:09 PM

None. It should not be implemented. Same with the future weapons some ppl like to ask for. It'd bring nothing but additional balancing issues to the game.

#3 Hawk819

    Member

  • PipPipPipPipPipPipPipPip
  • Colonel
  • Colonel
  • 1,865 posts
  • Location666 Werewolf Lane. Transylvania, Romania Ph#: Transylvania 6-5000

Posted 03 November 2016 - 04:18 PM

This game will get balancing issues. . . .irregardless of the weapon system or module. I wager that the Tech Tree Re-vamp cause some balance issues as well.

And besides, the Target Computer for the Clans only caused a minor re-balance. I don't see how adding the C3 computers or the Inner Sphere Targeting Computer would cause a serious balancing issue. Which is why I'm saying that both equipment types should never be used together.

#4 Deathlike

    Member

  • PipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • Littlest Helper
  • Littlest Helper
  • 29,240 posts
  • Location#NOToTaterBalance #BadBalanceOverlordIsBad

Posted 03 November 2016 - 04:21 PM

Please check back with me when the Command Console isn't utter garbage...

#5 Mcgral18

    Member

  • PipPipPipPipPipPipPipPipPipPipPipPip
  • CS 2019 Top 8 Qualifier
  • CS 2019 Top 8 Qualifier
  • 17,987 posts
  • LocationSnow

Posted 03 November 2016 - 04:42 PM

They don't
They offered a better to hit chance in TT, which has absolutely no value in MWO, unless you wanted LRMs to fire at 500M/s if you have a spotter.


Spheroid Omnirobots will also be absolute trash without GodQuirks, because hardwired isXL


How about we just give Spheroid mechs the option to mount a TC of their own. They would be functionally identical, and all that needs to happen is switch a flag.

#6 Scyther

    Member

  • PipPipPipPipPipPipPipPip
  • 1,271 posts
  • LocationOntario, Canada

Posted 03 November 2016 - 04:47 PM

C3 has a few problems with MWO implementation. The first being no point in mounting them unless you think other people are going to drop with the matching parts. Second being that several of the TT C3 functions are irrelevant or already implemented in MWO. Third being that since it's mostly only useful to pre-made unit drops, it would make the FP/CW pug-vs-premade situation even worse. Fourth, more balancing problems.

If I was going to do anything with it, it would just be to increase the function of the current Command Console. For 3 tons as implemented I don't know anyone who actually uses the CC.

It could either:
-Give approximately the function of a Clan TC1 to the whole lance. This would make it functional and weight-effective in any drop as well as helping with Clan/IS balance while not being OP. Duplicate copies in the same lance would not provide extra benefit beyond redundancy.
-Add TAG function to the mech the CC-equipped mech is targeting. This would give TAG functionality to mechs without a spare Energy slot, but would be expensive for the weight.
-'Designate target' visibly for the team, perhaps making the target dorito a brighter/thicker/pulsing red.

For 3 tons and 1 crit slot, personally I think you could combine the Tag/Designate functions with the current CC functionality and it would be useful.

Edited by MadBadger, 03 November 2016 - 04:49 PM.


#7 Livewyr

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 6,733 posts
  • LocationWisconsin, USA

Posted 03 November 2016 - 04:57 PM

What they could be: in as short of explanation of steps as possible...

Step one: Implement weapon sway, possibly even bloom when maneuvering and/or hot. (Not instant pin perfect accuracy.)
Step two: Implement C3 Master/Slave. Master equipped mech(s) in group are automatically lance leaders. (C3 not available to solo pilot.)
Step three: Lance leader locks a target- while particular lance has target locked and looking at it; drastically improved weapon stability during movement.

Bam: viable, useful C3 system. (Obviously; details to sort, but I've already put more thought into than PGI ever would.)

What it will be: Wishful thinking. Like the vast majority of every other interesting and creative idea to grace these forums and PGI's eyes.

Edited by Livewyr, 03 November 2016 - 05:00 PM.


#8 Snowbluff

    Member

  • PipPipPipPipPipPipPipPipPip
  • Bad Company
  • 2,368 posts

Posted 03 November 2016 - 05:20 PM

IIRC, the lore give a Datalink style capability... which the mechs already have.

/thread. NEXT!

#9 EgoSlayer

    Member

  • PipPipPipPipPipPipPipPip
  • Wrath
  • Wrath
  • 1,909 posts
  • Location[REDACTED]

Posted 03 November 2016 - 08:19 PM

View PostMcgral18, on 03 November 2016 - 04:42 PM, said:

They don't
They offered a better to hit chance in TT, which has absolutely no value in MWO, unless you wanted LRMs to fire at 500M/s if you have a spotter.


Spheroid Omnirobots will also be absolute trash without GodQuirks, because hardwired isXL


How about we just give Spheroid mechs the option to mount a TC of their own. They would be functionally identical, and all that needs to happen is switch a flag.


There are ways to model improved hit chances in MWO just like the Clan TCs do now, like boosting projectile speeds. There are other things they could do as well like shorten laser duration which usually also translates into more damage done on a specific section.

C3 could be implemented to boost these values and/or decrease target info gathering, increase sensor range and so on. The questions would be what would be enough to make it worthwhile, without being unbalancing, and what happens if there is no C3-master/Command Console because slaves be wasted tonnage without one. Or they could just implement C3i but that is way down the timeline, same timeframe as the IS TCs.

Then of course there is the other question - are there any fan favorite chassis that we don't have that require the C3 systems for the stock builds?

Edited by EgoSlayer, 03 November 2016 - 08:21 PM.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users