72 replies to this topic

[Stugg]

They are currently bugged.

Each time you save the load out it lowers your max armor by 7 in the CT and 5 on the ST.

Haven't checked to see if this is the case with stalkers, cicadas, and jagermechs.

[Athom83]

Um... did you not see the patch notes?

[Haipyng]

Structure / Max - Armor Redistribution:

The following 'Mechs have had some of their Arm Structure and Max Armor Points re-distributed from their Arm Locations into their Torso locations:

• Jenner
  
• Jenner IIC
  
• Cicada
  
• Jagermech
  
• Stalker

All 'Mechs in a player's inventory affected by this change will have their armor re-set to the stock values.[/color]

Edited by Haipyng, 15 May 2018 - 11:14 AM.

[suffocater]

Two answer and none of you understood the problem. If you change the armor back to correct states, change the mech and then back, the full armor got reduced. Saving doesn't work as intended.

[Nightbird]

That's not what the OP is complaining about.

[MechaBattler]

It lowers the CT max armor? So the opposite of what they'd said it would do?

[process]

Apparently I don't even understand what the patch notes are talking about. Is this quirk migration, or the actual base mech struct/armor being reallocated? If the latter, that's kind of unprecedented.

[Haipyng]

process, on 15 May 2018 - 11:55 AM, said:

Apparently I don't even understand what the patch notes are talking about. Is this quirk migration, or the actual base mech struct/armor being reallocated? If the latter, that's kind of unprecedented.

The patch notes never deliver enough information, so who knows? It sounds like armor being reallocated. Just have to surprise us when we get in to check it out.

[Chris Lowrey]

MechaBattler, on 15 May 2018 - 11:35 AM, said:

It lowers the CT max armor? So the opposite of what they'd said it would do?

Max CT armor on standard 35 tonners with no quirks: 44

Max CT armor on the Jenner with the recent changes: 52

Appears correctly on the Jenners I've been testing.

[Elizander]

Stugg, on 15 May 2018 - 11:09 AM, said:

They are currently bugged.

Each time you save the load out it lowers your max armor by 7 in the CT and 5 on the ST.

Haven't checked to see if this is the case with stalkers, cicadas, and jagermechs.

I just bought a Stalker.

[suffocater]

Chris Lowrey, on 15 May 2018 - 12:05 PM, said:

Max CT armor on standard 35 tonners with no quirks: 44

Max CT armor on the Jenner with the recent changes: 52

Appears correctly on the Jenners I've been testing.

It looks correct the moment you save it. If you change the mech and then go to the previous mech, the armor got reduced a few points. I see that on all the chassis that got changed, except the stalkers.

[Chris Lowrey]

So as stated in the patch notes:

All 'Mechs in a player's inventory affected by this change will have their armor re-set to the stock values.

In the event that the stock armor values would render the 'Mech invalid, the 'Mech will be labeled as such. Readjusting the armor to the desired amount should correct this and it should be fine once you have set your armor values to your desired amount.

[Alexander of Macedon]

I've tested every possible thing I can think of to try to replicate this on my Stalkers and Cicadas. Everything operating normally. Until someone can independently confirm this on Jenners I'm assuming OP just skimmed the patchnotes.

[Vanguard836]

For some reason I can't save with max CT or side torso armor as well with available tonnage. It defaults back to 1 available point each ST and 3 available in the CT.

[Chris Lowrey]

Vanguard836, on 15 May 2018 - 12:37 PM, said:

For some reason I can't save with max CT or side torso armor as well with available tonnage. It defaults back to 1 available point each ST and 3 available in the CT.

hmm....

Can you try stripping the armor off and seeing if the problem persists? Also, what variant are you looking at?

[Vanguard836]

Chris Lowrey, on 15 May 2018 - 12:41 PM, said:

hmm....

Can you try stripping the armor off and seeing if the problem persists? Also, what variant are you looking at?

The Founders Jenner D and one moment will try !

Edit : Yes it's still occurring Chris.
Stripped the armor, saved, reapplied the armor and saved again, selected another mech and came back, same issue.

Edited by Vanguard836, 15 May 2018 - 12:45 PM.

[kailii]

My JM6-S shows an "Alert: Invalid Loadout".

Workaround:
Lowering the armour in EACH location by one point makes the error disappear.
It can then be restored without recreating the error.

Note:
My armour is now maxed as it should be (except head). This was not the case when i first checked the Mech.
So it seems the displayed armour values are wrong right after patching.

***EDIT:
Took the Jager to Testing Grounds and back to Mechlab, all fine.
(Just reporting this anomoly because others can't seem to fix their Mechs)

Edited by kailii, 15 May 2018 - 12:50 PM.

[Vanguard836]

kailii, on 15 May 2018 - 12:46 PM, said:

My JM6-S shows an "Alert: Invalid Loadout".

Workaround:
Lowering the armour in EACH location by one point makes the error disappear.
It can then be restored without recreating the error.

Note:
My armour is now maxed as it should be (except head). This was not the case when i first checked the Mech.
So it seems the displayed armour values are wrong right after patching.

Pretty sure that's as indicated in the patch notes ; we have to go in and double check the mechs' armor values

[Chris Lowrey]

Vanguard836, on 15 May 2018 - 12:42 PM, said:

The Founders Jenner D and one moment will try !

Edit : Yes it's still occurring Chris.
Stripped the armor, saved, reapplied the armor and saved again, selected another mech and came back, same issue.

How much structure is the 'Mech lab showing?

Possibly restart the client see if the problem still persists.

I'm looking at the Founders Jenner files and its looks like everything is in order. Not discounting the possible bug, but just need further info to investigate.

[Vanguard836]

Chris Lowrey, on 15 May 2018 - 12:52 PM, said:

How much structure is the 'Mech lab showing?

Possibly restart the client see if the problem still persists.

I'm looking at the Founders Jenner files and its looks like everything is in order. Not discounting the possible bug, but just need further info to investigate.

Restarting does not appear to resolve the issue.
So far.

Edited by Vanguard836, 15 May 2018 - 12:56 PM.