Jump to content

Mad Cat Mk Ii, The Big Cat (Or Big Alpha Wolf?). `mech Discussion

BattleMechs

704 replies to this topic

#261 ScarecrowES

    Member

  • PipPipPipPipPipPipPipPipPip
  • Knight Errant
  • Knight Errant
  • 2,812 posts
  • LocationDefending the Cordon, Arc-Royal

Posted 19 March 2016 - 11:02 PM

View PostCK16, on 19 March 2016 - 10:13 PM, said:

We seem to disagree on what we consider Clan and Inner Sphere...the Game is pretty Black and White on this matter, so is much of lore on this, even Wolf in Exile is still considered a clan, they follow clan traditions they might ally with some of the House factions from time to time, but they don't share their mechs with them, quiaff?


You keep arguing a losing point... and this one paragraph ALONE makes it clear you have literally no idea what you're talking about.

Since you've shown yourself to be on the new side when it comes to your history with Mechwarrior, and even more novice with lore, I suggest wholeheartedly that you learn and then come back to the argument.

You can start, perhaps, with Wolf-in-Exile. With Wolf's trajectory from chosen of Kerensky, to delayer of Invasion, to conquerer of the Sphere, to honorer of truces, and to shield of the Sphere.

Maybe find out what happens to WiE when they leave the Clans. What do they immediately do once they get to Arc-Royal? Your entire characterization of WiE's involvement with the Sphere shows a severe lack of understanding. Of what makes WiE, NC, GB different from other Clans.

You're holding onto a straw here... a small and insignificant straw. And you're holding on so tightly that logic obviously cannot be governing that. I see Ghost Bear next to your name. Do you know what their trajectory is? They move to the Inner Sphere long before that MkII is released.

You don't seem to read what I write. You don't seem to understand the position here. You keep arguing against what the source says... on which you're wrong. You keep trying to say PGI won't follow lore, even though all indication is that they do. And on that point you're, again, wrong. You keep trying to say what PGI will or won't do... even though they've either been specific against doing what you want, or haven't said at all.

You have a clear bias. You WANT the MkII, and you WANT it as Clan, no matter what the facts or PGI have to say on the matter. And as you've made clear... you don't care what anyone has to say, not even PGI... about if or when it's going to be released... how, to what faction, into what game environment - you're going to continue to believe what you want.

Here's the thing... what mechs and tech are on what side of a conflict in Battletech is ALWAYS black and white. Thankfully it's all written down for us so we always know. And another thing... it's always changing too. MWO? PGI has always intended for the state of the game to reflect the state of the Inner Sphere. It's supposed to be a changing environment, just as the galaxy changed from year to year. PGI is following lore... not your particular opinion of what makes what faction what. I'm telling you, in a million different ways, WHAT Battletech has to say on the matter.

You can choose, as you have been, to ignore what the source says. You can stamp your feet and go "No, No, No!" It's a child's tantrum, nothing more. But PGI? Given the scope of the game, they've done a bang-up job sticking to source so far. Perfect, no. But close enough.

What they do about the MkII depends on what they want to do about lore, and whether or not they want their game around in 5 years. The MkII presents a series of problems that have to be addressed sooner or later. I'd rather them be addressed sooner. It seems a lot of folks would agree. But we're not children throwing a hissy fit.

#262 CK16

    Member

  • PipPipPipPipPipPipPipPipPip
  • The Cub
  • The Cub
  • 3,031 posts
  • LocationAlshain V

Posted 19 March 2016 - 11:05 PM

No it is you who is grasping at straws....

This is a pointless arguement, I find it funny no one agree's they will be an inner sphere mech;s as you claim, no they will be clan, or at best open to both, as Inner Sphere open to the current Inner Sphere houses no, it will not be. I find it funny you feel this and claim others agree, no one here has agree'ed with you, we all point out your wrong with a few points that are facts yes but logically no, you are wrong once again.

Edited by CK16, 19 March 2016 - 11:11 PM.


#263 ScarecrowES

    Member

  • PipPipPipPipPipPipPipPipPip
  • Knight Errant
  • Knight Errant
  • 2,812 posts
  • LocationDefending the Cordon, Arc-Royal

Posted 19 March 2016 - 11:23 PM

View PostCK16, on 19 March 2016 - 11:05 PM, said:

No it is you who is grasping at straws....

This is a pointless arguement, I find it funny no one agree's they will be an inner sphere mech;s as you claim, no they will be clan, or at best open to both, as Inner Sphere open to the current Inner Sphere houses no, it will not be. I find it funny you feel this and claim others agree, no one here has agree'ed with you, we all point out your wrong with a few points that are facts yes but logically no, you are wrong once again.


You haven't been reading your own topic there, bud. You're in the minority now. The only ones standing on your side are your "MkII in 2016!!!" buddies. You guys have an unhealthy emotional investment in this... you know that right? And literally noone, I think in this thread or any other is saying that it WILL be released as an Inner Sphere mech. Who knows what PGI will end up doing. The argument is that it IS an Inner Sphere mech, and noone knows how PGI wil rectify that. I think most of the folks that were struggling with this have gotten it now. What the source says. What it means for the future of MWO. But you persist.

I mean, come on. The sources, you can read them as well as anyone. And literally NOONE but you is arguing against what the sources say. Not even your buddies. Some people will put their focus on certain facts above others and draw a different distinction based on how MWO handles things differently than TT, but noone is patently arguing against the source but you. Your buddies? If you pay attention, all they say is that PGI will probably just ignore lore and throw mechs like the MkII onto the Clan side because keeping clan tech aligned with Clan factions is the lazier way to introduce the mech. And to that, I fully admit it's a possibility. PGI just might do that. Or they might not.

Hell, this is a company that makes balancing their game a nightmare because they refuse to change stats on weapons from what is explicitly called out in the source material. It is a company that sticks so closely to the source art for its mechs that some of them end up looking every bit as ridiculous as the originals. Its a company which has included every single planet in the galaxy into their CW mode, even if you can't fight over every one. It's a company that is so OCD about lore that they refuse to sell one of the most potentially profitable mechs they have available simply because they have a particular vision for the lore they want their game to adhere to, and that mech doesn't sit inside that vision. They make everything they do harder because they want this to be a game that is true to the source material. And you think they'd suddenly start ignoring that for a mech that you really really really want?

PGI makes a lot of bad decisions, so it's possible, right?

I figure, if you really want this mech as much as you say you do, you'll care if the game does right by the lore surrounding it. That you don't want it THIS badly just because it appeared in MW4 and couldn't give a crap less how it's implemented.

Edited by ScarecrowES, 19 March 2016 - 11:31 PM.


#264 Y E O N N E

    Member

  • PipPipPipPipPipPipPipPipPipPipPipPip
  • The Nimble
  • The Nimble
  • 16,810 posts

Posted 20 March 2016 - 02:07 AM

This debate is more ridiculous than the XL debate.

Congratulations!

#265 Metus regem

    Member

  • PipPipPipPipPipPipPipPipPipPipPip
  • The Sureshot
  • The Sureshot
  • 10,282 posts
  • LocationNAIS College of Military Science OCS courses

Posted 20 March 2016 - 06:35 AM

View PostCK16, on 19 March 2016 - 10:13 PM, said:

Who built the Mad Cat Mk.II? Who was it intended for?

Who built the Nova Cat? Who was it intended for?

The answer is a simple and straight forward for both, Clan....



But it's not that straight forward, the Lore for the silly thing all but states it was intended to be sold to the IS, that Diamond Shark wanted it rejected by the two most likely of buyers (Clan Wolf and Clan Jade Falcon). We see this reflected in the Mk III, when the IS send special forces to get information on it, only to get an elaborate sales demonstration.


Scarecrow, the Timber Wolf is listed in the master unit files as Clan General, it is available in all Clan unit lists during the invasion era, most common in Clan Wolf.

#266 Imperius

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • The God
  • The God
  • 5,747 posts
  • LocationOn Reddit and Twitter

Posted 20 March 2016 - 07:57 AM

View PostMetus regem, on 20 March 2016 - 06:35 AM, said:


But it's not that straight forward, the Lore for the silly thing all but states it was intended to be sold to the IS, that Diamond Shark wanted it rejected by the two most likely of buyers (Clan Wolf and Clan Jade Falcon). We see this reflected in the Mk III, when the IS send special forces to get information on it, only to get an elaborate sales demonstration.


Scarecrow, the Timber Wolf is listed in the master unit files as Clan General, it is available in all Clan unit lists during the invasion era, most common in Clan Wolf.


It is strait forward, it's under Clan Battlemech in the 3067 TRO table of contents. Issue solved like 5 pages ago, but that's none of my business.

#267 Metus regem

    Member

  • PipPipPipPipPipPipPipPipPipPipPip
  • The Sureshot
  • The Sureshot
  • 10,282 posts
  • LocationNAIS College of Military Science OCS courses

Posted 20 March 2016 - 09:36 AM

View PostImperius, on 20 March 2016 - 07:57 AM, said:


It is strait forward, it's under Clan Battlemech in the 3067 TRO table of contents. Issue solved like 5 pages ago, but that's none of my business.


But shows up on the random Mech assignment tables for House Steiner, House Davion and House Katura. That is the issue that we are trying to address with where it will sit for CW, as those are the only factions currently in CW that use the mech., that is why I see the Mk II as problematic, for CW.

#268 Imperius

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • The God
  • The God
  • 5,747 posts
  • LocationOn Reddit and Twitter

Posted 20 March 2016 - 10:10 AM

View PostMetus regem, on 20 March 2016 - 09:36 AM, said:


But shows up on the random Mech assignment tables for House Steiner, House Davion and House Katura. That is the issue that we are trying to address with where it will sit for CW, as those are the only factions currently in CW that use the mech., that is why I see the Mk II as problematic, for CW.


Until there is talk about CW actually moving out of 3051-3053 this is a non-issue. Technically CW would be in permanent cease fire ;) and somehow we fought for Tukayyad and forgot, then fought for it again. CW and Tukayyad is like the movie Ground Hog Day.

Edited by Imperius, 20 March 2016 - 10:12 AM.


#269 ScarecrowES

    Member

  • PipPipPipPipPipPipPipPipPip
  • Knight Errant
  • Knight Errant
  • 2,812 posts
  • LocationDefending the Cordon, Arc-Royal

Posted 20 March 2016 - 11:10 AM

View PostImperius, on 20 March 2016 - 07:57 AM, said:

It is strait forward, it's under Clan Battlemech in the 3067 TRO table of contents. Issue solved like 5 pages ago, but that's none of my business.


In TROs mechs are divided by tech base... not faction. The TROs are telling you which construction rules you have to follow when you're building with that mech. The Faction Availability tables, as you'll see in the Battletech Master Unit List, tell you which mechs belong to which faction. I know it's not very straight forward, but that's how the source works. "Clan" in the TRO doesn't mean it's a mech that is used only by Clans.

For instance, in TRO 3060, the Kell Hounds and Clan Wolf-in-Exile actually belong to the same faction... the Arc-Royal Defense Cordon - an Inner Sphere-aligned faction. And in 3059, they both produce mechs that they've built jointly. The Kell Hounds produce the Arctic Fox omnimech, and the Wolves build the Arctic Wolf battlemech. They're both built in the same factory in what used to be Steiner space. But the Fox is listed as Inner Sphere because it is built on an IS tech base, and the Wolf is Clan because it's on clan tech. But both mechs fight against the Clans on behalf of the Inner Sphere.

Battletech doesn't draw a distinction over what mechs and tech a player is allowed to use. Even if you follow the strictest rulesets, you're allowed to use anything you want as long as you follow construction rules. However, you can only START with tech and equipment native to your chosen faction. You have to EARN the right to use anything else through role-playing.

MWO makes a distinction that Battletech doesn't because it's trying to simplify the rules to streamline its game system. Buuuuut, as we've seen, it causes a lot of problems that just wouldn't exist if those special distinctions didn't exist.

And if you remember how the MkII was first introduced, you understand why the lore has to specify how the mech ended up in the hands of so many IS factions, despite having clan space origins. the MkII was introduced in MW4, which is an apocryphal product (meaning it's not canon). However, the MkII and some other stuff introduced in MW4 were so popular that WizKids (who owned the rights to Battletech) at the time decided to capitalize on that popularity and include the MkII in the official product line.

The problem was, now Wizkids had to explain how a clan-tech assault mech had permeated through the Inner Sphere Houses so quickly after it had been introduced (it was everywhere in FedCom space not even one year after being made available) - and why it had an Inner Sphere name and not a Clan one. Remember that the theater of war in MW4 was the Inner Sphere late in the FedCom Civil War, but the MkII came out in TRO 3067 - so it wasn't an Invasion-era mech - and thus had to be produced either by IS clans or in clan space. They chose the latter to coincide with the Clan/IS narrative that was going on at the time to illustrate a shift in relations between the two factions - and to put the mech firmly in the Inner Sphere for Dark Age.

So the MkII being aligned with the Sphere is very purposeful, and you really have MW4 to blame for that, ultimately.

#270 LastKhan

    Defender of Star League

  • PipPipPipPipPipPipPipPip
  • The Vicious
  • The Vicious
  • 1,346 posts
  • Twitter: Link
  • LocationIn Dropship DogeCafe

Posted 20 March 2016 - 11:14 AM

View PostImperius, on 20 March 2016 - 10:10 AM, said:

Until there is talk about CW actually moving out of 3051-3053 this is a non-issue. Technically CW would be in permanent cease fire Posted Image and somehow we fought for Tukayyad and forgot, then fought for it again. CW and Tukayyad is like the movie Ground Hog Day.


It kinda is in scarecrow's terms, that means the MK2 cant really be in the game since its shared by both the innersphere and the Clans during its timeframe. but this is in his view of course and it has a fraction of a point.

Edited by LastKhan, 20 March 2016 - 11:18 AM.


#271 Andi Nagasia

    Volunteer Moderator

  • PipPipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 5,982 posts

Posted 20 March 2016 - 11:16 AM

View PostImperius, on 20 March 2016 - 10:10 AM, said:

Until there is talk about CW actually moving out of 3051-3053 this is a non-issue. Technically CW would be in permanent cease fire Posted Image and somehow we fought for Tukayyad and forgot, then fought for it again. CW and Tukayyad is like the movie Ground Hog Day.

Had a solution to this problem, but im not ganna post it here as i dont what to Derail the Topic,
i would love to see the TBR-MK2(2) in MWO, 2E 2B 4M, 3JJ, would be amazing, DWF-C would be as well,

#272 CK16

    Member

  • PipPipPipPipPipPipPipPipPip
  • The Cub
  • The Cub
  • 3,031 posts
  • LocationAlshain V

Posted 20 March 2016 - 11:21 AM

View PostLastKhan, on 20 March 2016 - 11:14 AM, said:


It kinda is in scarecrow's terms, that means the MK2 cant really be in the game since its shared by both the innersphere and the Clans during its timeframe. but this in his view of course and it has a fraction of a point.



Yes but if it came down a simple 1 faction to get it, it should and would land as a Clan mech. Its a long shot but possible they could make it one of the first to be open to both Clan and IS...but as strickly an IS only mech? No, that won't happen and it makes no sense to have it as IS only, no matter what factions are in or not in this game...Many players who claim Nova Cat still play as clan.....If they added more faction camo's, would you say Nova Cat Camo should be for IS mechs? or Clan mechs? Clan of course CNC didnt use Dragon's or Atlas, plus it would make many current players who run as CNC be very confused as to why they could paint in IS mech in their stars but no a Shadowcat, you know a mech THEY made?

#273 LastKhan

    Defender of Star League

  • PipPipPipPipPipPipPipPip
  • The Vicious
  • The Vicious
  • 1,346 posts
  • Twitter: Link
  • LocationIn Dropship DogeCafe

Posted 20 March 2016 - 11:23 AM

View PostScarecrowES, on 20 March 2016 - 11:10 AM, said:


And if you remember how the MkII was first introduced, you understand why the lore has to specify how the mech ended up in the hands of so many IS factions, despite having clan space origins. the MkII was introduced in MW4, which is an apocryphal product (meaning it's not canon). However, the MkII and some other stuff introduced in MW4 were so popular that WizKids (who owned the rights to Battletech) at the time decided to capitalize on that popularity and include the MkII in the official product line.

The problem was, now Wizkids had to explain how a clan-tech assault mech had permeated through the Inner Sphere Houses so quickly after it had been introduced (it was everywhere in FedCom space not even one year after being made available) - and why it had an Inner Sphere name and not a Clan one. Remember that the theater of war in MW4 was the Inner Sphere late in the FedCom Civil War, but the MkII came out in TRO 3067 - so it wasn't an Invasion-era mech - and thus had to be produced either by IS clans or in clan space. They chose the latter to coincide with the Clan/IS narrative that was going on at the time to illustrate a shift in relations between the two factions - and to put the mech firmly in the Inner Sphere for Dark Age.

So the MkII being aligned with the Sphere is very purposeful, and you really have MW4 to blame for that, ultimately.



Whats funny I have played the DA clicks game many years back and the MK2 was never in it. just its picture in the logo. The only thing semi related was MadCat II which wasnt the same.

#274 ScarecrowES

    Member

  • PipPipPipPipPipPipPipPipPip
  • Knight Errant
  • Knight Errant
  • 2,812 posts
  • LocationDefending the Cordon, Arc-Royal

Posted 20 March 2016 - 11:23 AM

View PostLastKhan, on 20 March 2016 - 11:14 AM, said:


It kinda is in scarecrow's terms, that means the MK2 cant really be in the game since its shared by both the innersphere and the Clans during its timeframe. but this in his view of course and it has a fraction of a point.


I haven't ever said the MkII can't be in the game. Just that putting the MkII in is problematic. And it's not specifically the MkII, it's more or less anything that comes in during the post-3058 timeframe. You can't really just plop post-3058 mechs into an early 3050's timeline. With all the faction changes after 3058, there is a problem of getting the mechs on the right side of the conflict in a way that won't cause more issues later. The timeline being stuck is a problem.

The game was never intended to just float in the early Clan Invasion period. It was supposed to flow out to later parts of the conflict. So when new mechs and tech was introduced, the map was supposed to reflect the environment into which those mechs were introduced. The problem is, the state of the game is not keeping pace with mech releases. And this is fine as long as we stay on this side of 3058. Afterward though, it's an issue. A lot of mechs players want are icons from a later time. MkII, Nova Cat, Uziel, etc.

We know PGI intends to update CW over the next few years and we'll eventually make the leap forward. I personally say we should just move right to 3059 NOW, update the map, tune the game for that environment, and avoid all these problems. The map in 3067 is pretty much exactly the same as it is in 3059. There is little real difference, aside from some of the faction labels changing slightly.

So much good can be done to the game simply by moving the clock forward. It's gonna happen sooner or later... why not sooner?

#275 LastKhan

    Defender of Star League

  • PipPipPipPipPipPipPipPip
  • The Vicious
  • The Vicious
  • 1,346 posts
  • Twitter: Link
  • LocationIn Dropship DogeCafe

Posted 20 March 2016 - 11:28 AM

View PostScarecrowES, on 20 March 2016 - 11:23 AM, said:


I haven't ever said the MkII can't be in the game. Just that putting the MkII in is problematic. And it's not specifically the MkII, it's more or less anything that comes in during the post-3058 timeframe. You can't really just plop post-3058 mechs into an early 3050's timeline. With all the faction changes after 3058, there is a problem of getting the mechs on the right side of the conflict in a way that won't cause more issues later. The timeline being stuck is a problem.

The game was never intended to just float in the early Clan Invasion period. It was supposed to flow out to later parts of the conflict. So when new mechs and tech was introduced, the map was supposed to reflect the environment into which those mechs were introduced. The problem is, the state of the game is not keeping pace with mech releases. And this is fine as long as we stay on this side of 3058. Afterward though, it's an issue. A lot of mechs players want are icons from a later time. MkII, Nova Cat, Uziel, etc.

We know PGI intends to update CW over the next few years and we'll eventually make the leap forward. I personally say we should just move right to 3059 NOW, update the map, tune the game for that environment, and avoid all these problems. The map in 3067 is pretty much exactly the same as it is in 3059. There is little real difference, aside from some of the faction labels changing slightly.

So much good can be done to the game simply by moving the clock forward. It's gonna happen sooner or later... why not sooner?


But bro, CW phase 3 praise be upon it.

#276 Imperius

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • The God
  • The God
  • 5,747 posts
  • LocationOn Reddit and Twitter

Posted 20 March 2016 - 11:28 AM

View PostLastKhan, on 20 March 2016 - 11:14 AM, said:


It kinda is in scarecrow's terms, that means the MK2 cant really be in the game since its shared by both the innersphere and the Clans during its timeframe. but this is in his view of course and it has a fraction of a point.


Yes, because pug matches are ALWAYS 12 clan vs 12 IS right? Right?

You all can quit grasping at straws trying to keep my mech out of the game for whatever your reasons are.

Here are the things that don't matter in MWO. Lore, timeline, and faction specific mechs. Russ has stated his position many times on the matter that he will not limit the mechs people buy and play. The prime variant is a Battlemech with clan tech in it, with a TRO saying its clan. It's a non-issue and has been.

#277 ScarecrowES

    Member

  • PipPipPipPipPipPipPipPipPip
  • Knight Errant
  • Knight Errant
  • 2,812 posts
  • LocationDefending the Cordon, Arc-Royal

Posted 20 March 2016 - 11:28 AM

View PostLastKhan, on 20 March 2016 - 11:23 AM, said:

Whats funny I have played the DA clicks game many years back and the MK2 was never in it. just its picture in the logo. The only thing semi related was MadCat II which wasnt the same.


Right? What a weird bit of marketing THAT was! The MkII was introduced for Dark Age, but never actually used in that version of Battletech. They put it on the Logo for the game and everything, but then actually used the Mad Cat II instead? I don't remember what the story was on how that happened. I remember it was a mess.

#278 ScarecrowES

    Member

  • PipPipPipPipPipPipPipPipPip
  • Knight Errant
  • Knight Errant
  • 2,812 posts
  • LocationDefending the Cordon, Arc-Royal

Posted 20 March 2016 - 11:32 AM

View PostLastKhan, on 20 March 2016 - 11:28 AM, said:

But bro, CW phase 3 praise be upon it.


Indeed. With the new systems in place, changing dates should be easier than ever. I kinda wish they'd just update the map before CW3 drops and start the new mode in 3059 from the get-go. PGI has never actually said what the state of the game will be in CW3 so, there's a 0.637% chance they could have put some effort in and will surprise us with a timeline jump.

#279 CK16

    Member

  • PipPipPipPipPipPipPipPipPip
  • The Cub
  • The Cub
  • 3,031 posts
  • LocationAlshain V

Posted 20 March 2016 - 11:32 AM

If we are going to pull MW4 into this....

Spoiler


see a pattern here? plus are we really going to use Mw4 here?

#280 LastKhan

    Defender of Star League

  • PipPipPipPipPipPipPipPip
  • The Vicious
  • The Vicious
  • 1,346 posts
  • Twitter: Link
  • LocationIn Dropship DogeCafe

Posted 20 March 2016 - 11:33 AM

View PostScarecrowES, on 20 March 2016 - 11:28 AM, said:


Right? What a weird bit of marketing THAT was! The MkII was introduced for Dark Age, but never actually used in that version of Battletech. They put it on the Logo for the game and everything, but then actually used the Mad Cat II instead? I don't remember what the story was on how that happened. I remember it was a mess.


Yea ive always wondered that even back then i would ask people why it wasnt in but never got a good answer cause alot didnt know. I still have my custom painted Spirit Cats MadCat II on my self from doing like big city fights and Solaris. Miss playing that game.





2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users