Ultimatum X, on 25 September 2014 - 01:51 AM, said:
We can argue however that taking a risky engine is a choice you get to make.
Or you can choose to use a STD engine for more survivability.
This choice, and many others are forbidden to clan mechs.
There is no option in a DWF to take the safer engine, ever.
These are mechs with locked structure and locked armor, and locked DHS that are also locked into locations.
You don't get to choose any of that.
You also do not get to choose your engine size.
These are the penalties that justify benefits like Clan XL - except now that Clan XL is getting nerfed will we see any of that alleviated?
We should, but I doubt it will happen.
I'd love 35+ tons of free pod space for my Timber Wolf, or to take Endo on my WHK and drop Ferro.
I can never do these things, but I accept that because I get benefits from omni-pods and Clan XL.
So what is the tipping point where the restrictions on all things clan become enough to where locked items can be loosened?
The trade off for superior engine that is locked, with gear that is locked is being broken as this engine is being nerfed/downgraded - which will hurt the Clan Assaults by quite a lot.
In the face of upcoming IS mechs like the King Crab, these nerfs might even be jumping the gun. Or is it OK to have a dual gauss toting 100T assault mech with a STD engine, Endo, and as many or as few DHS as the build actually needs instead of having 10 of them strapped on whether you want them or not?
Is it OK for the King Crab to have all of that "because IS"?
I think you misunderstood my post, mainly because you sound like you're disagreeing with me, but you and I are actually on the same page.
I was saying that IS XLs are working fine, and as intended, however clan XLs aren't since they still don't have the debuff installed. My problem was with the guy I was responding to, who wanted IS mechs to be locked out of use for several weeks while changing engines.
Also, locked clan engines is a detriment, it's just not big enough to actually bring them close to balance against IS engines.
Clan XLs should be somewhere between IS STDs, and IS XLs. Not above them. IS STD gives max survivability for a weight cost, while saving slots. Clan XLs should give better weight savings, for a slot cost, and risk when losing a Side Torso, and death when losing both. So it's less survivable than IS STD, but better than IS XL. While IS XLs give the most weight savings for IS mechs, for 2 more slots than Clan XLs, and the risk of death when losing a side torso.
Daneiel, on 25 September 2014 - 04:05 AM, said:
One more IS mechs don't operate exactly as the lore - the reason of that is that key elements was rermoved of the game other was never implemented - The IS XL engines work according the lore only to the point where you need to get out your wallet and spend insane amount of c-bills for customisation - now did you get what mean "slap the engine -> the cost of the engine + manipulation cost " - in the lore customisation is rare because of the cost and logistic problems (feel free to correct me here). And here is - you can not call for full lore implementation of the clan XL engines without call for changes where IS restrictions are placed - money and logistic ( lockdown period) , now i think you will understand me - i am all for lore implementation , but it needs to be done right , not lets go full lore restrictions for the clans but not for the IS and please understand me right - i care for IS mechs as much as the Clan ones - i am disgusted from the abominations created via that mechlab.
Ok, seriously. What are you talking about? First off, customization wasn't done in 3025 because the materials weren't there, and it was expensive. Second of all, We're asking for the implementation of lore as far as clan XL engines' debuff when they lose a side torso. If we go by your "insanely twisted" logic, then you don't get your clan mech until 3 months after you pay for it, and if you get destroyed in a match, wait another 2 months before the engine is fixed, then another month before pods are installed.
Again: your argument is in the bat-****-insane section. Right now here's how it stands: IS - decent lore implementation for the engines. Clan- NO, NONE, ZIP, ZILCH, lore implementation on their engines.
Unless you can understand that much, we really shouldn't be arguing/debating this. I don't have the time to explain the same point 5 different ways.
By the way. IS mechs do operate according to lore. If you have the money you can customize them. Which we have, and do. You're talking about the standard military guys. Yes, the never customized their mechs, because they are not allowed to, and don't usually get paid enough to do so.
However, the independent guys, they customized their mechs whenever they could. Look at Kai-Allard Liao, he removed the AC 20 from his YLW and slapped a Gauss rifle instead. That's ONE example, there are many where the mech was fully gutted, and rebuilt from the ground up.
Don't use some insane lore restrictions as a shield to hide behind, especially not when you're missing the scope or scale of the argument.
Or maybe you want to lose all your mechs, and only pilot one randomly assigned clan mech for the entirety of your MW:O career? I mean, if you want to go crazy with the lore. Let's go all the way, right? Are you seeing how flawed, and mistaken that application of lore is?
Here's reasonable application of the lore:
Hey, clan XLs aren't fully implemented yet, how about we wrap that up. Now we have IS STDs for most survival, IS XLs for maximum weight saving with a high risk of destruction. Clan XLs for best weight saving and better survivability than IS XLs. However, when you lose a side torso, you lose some benefits.
This makes the engine hierarchy go like this: STD>C-XL>IS XL. Instead of C-XL>IS STD>IS XL. This makes Clan XLs balanced, instead of absolutely a step up from IS engines in every single way possible.
Everything else you are talking about, is unrelated to the actual discussion about the engines. Focus on that aspect please.
Yes, I understand that locked engines are a downside, and I firmly believe that. However, that's no excuse to keep something broken/not fully implemented.
And this is a pointer to help with future discussion: Please use paragraphs, and break the text from one giant wall, into smaller, easier to read sections. It makes a huge difference.
Edited by IraqiWalker, 25 September 2014 - 08:47 AM.