Its already out, you need to search for you, the links is also in the mod descs.

are we getting a 4.0+??

@Battlespark you are using a old version of this mod. The link is in the desc for the latest one.

i cant seem to get this one to work. It just immediately crashes on creating a universe.

3.4

what version of the game is this for?

The armor value fix will not be given to V3.4, mainly because this bug only really exist if you attempt to play the mod with 3.6.

I've finished updating and uploading, it contains the fix to the armor value issue too.
https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=2928282382

I need people to test to see if it works, it works for me, but it is a good idea for me to get feedback from everyone else.

@Maelstrom Vortex That kind of is the plan, but it hasn't worked.

@Guluere I'd suggest copying the text data from your page detalis.. yank the mod.. and then reupload it entirely, see if that helps.

The Stellaris launcher aren't able to upload it, might try it on a different pc to see if it persist.

I am actually having trouble updating and uploading my mod, I am not sure what is causing it. I have tried a few things to resolve it, but nothing have worked...

@aarnold If only steam wouldn't correct it every time you had to verify files. *sigh*

@Guluere Sent you a couple bucks to try to stir you to update and fix this basic bug to make your mod workable again.

@Guluere The fixes the others found, any possibility you could take a couple minutes to integrate them and re-upload? I know a lot of us would be incredibly appreciative.

OMG thank you! it totally worked!
the file is located here:
steam\steamapps\workshop\content\281990\2809238516\common\scripted_variables

the file is called:
02_scripted_variables_component_cost.txt
you merely have to change it to this:
02_scripted_variables_component_cost_UL.txt

its that simple

@Swaze21 how do you do that fix btw

@swaze21 you mean *.txt_UL or *._UL or *_UL.txt?

Just a PSA for anyone who wnats to play the mod this is how to fix it

A guy on the 3.0 version of the mod said he found a way to fix the no armor value. He renamed 02_scripted_variables_component_cost.txt in common/scripted_variables and put _UL at the end. As long as you rename something and put _UL at the end it will add the armor values back tot he game. I just did it and it works for this version 2. Until theres an update this is the best way to remedy this issue.

JFC I spent -hours- looking for the culprit of the armor-0 problem. Please just de-list this til you fix it. Ugh.

So THIS is the mod that makes armor have no value...hoping for a fix soon cuz I love spicing up the endgame

I really like your mod, I think it's essential, so I hope you will resolve the armor issue soon.
Renaming the 02_scripted_variables_component_cost file doesn't helped.

BTW. launcher shows 3.0+ as v3.6 compatible, but the 3.4+ shows as for v3.4

Yes, I know, the fix will be either on 3.6 or 3.7.

this also affects hull btw

Soon-ish.

what will the ETA be on the update roughly?

Because armor value was the only one that was actually flipped incorrectly. It's almost like an OCD thing.

Oh, I found the issue.
In 2.6, they silently rewrote the defines, flipping the [Number][Size] to [Size][Number] for specifically armor values only.

Will this mod get an update to fix the armor define issue?

Might be 3.7, I am still finishing the last my semester's assignments, which is eating into the time of my sem break. I already formed a basic idea of what direction I will be pushing toward for Starcore and Illunia.

will be 3.6 version ?
Mod is superior :D

Shout out to @Silos for the fix

A guy on the 3.0 version of the mod said he found a way to fix the no armor value. He renamed 02_scripted_variables_component_cost.txt in common/scripted_variables and put _UL at the end. As long as you rename something and put _UL at the end it will add the armor values back tot he game. I just did it and it works for this version 2. Until theres an update this is the best way to remedy this issue.

@Guluere sadly not, I have a 75 mod long playlist put this one top and the armor values were still zero

What mod is it so I download it

The issue probably is fixed if you have another mod that fixes it in the load order after my mod. Since that mod will replace my 02_scripted_variables_component_cost changes instead, if theirs is fixed, it will also fix this one.

My armor values are fine

not just armor but hull too. i let him know through NSC2's discord. just be patient everyone. Guluere, keep up the good work. o7

There is a high chance this is due to the fact that my mod has new defines for the values of the cost and stats. As part of the purpose was to rescale the vanilla value into something much nicer.

This is not something I am not aware of, I have not gotten the time to go into fixing the issue, but there is a lot of available patches out there already. Since there is a good amount of other mods also having this problem.

armour removal is due to the change in file "02_scripted_variables_component_cost" , as there's no armour values there. had someone track it down. it is definitely this mod.

Seems to work with 3.6, but as mentioned, armor value is always zero.
Its the same for the AI empires, but not the fallen empires

With the Orion update, this mod somehow removes armor from all fleets in the galaxy. I can add all the armor I want, but the value remains zero no matter what. Disabling the mod immediately fixed the issue.

Do any mods require this one? Game is crashing when this mod gets disabled?

Definitely breaking things in 3.6

WHEN???

Still busy with college, I will be getting a longer break soon.

UPDATE WHEN???????

@Guluere - Hi there. Love this mod. Just curious if you are still working on it or if you moved on to other things. Thanks.

Because the numbers don't match. That is the reason. Mismatching numbers is a mistake, and mistake is always bad. Besides, these yellow things look ugly.
Do not criticize those who use the system properly.

\/ seems like most people see a version mismatch and automatically assume it's completely incompatible