安装 Steam						
					
				
				
									登录
											 | 
						语言
						
																																															繁體中文(繁体中文)
																													日本語(日语)
																													한국어(韩语)
																													ไทย(泰语)
																													български(保加利亚语)
																													Čeština(捷克语)
																													Dansk(丹麦语)
																													Deutsch(德语)
																													English(英语)
																													Español-España(西班牙语 - 西班牙)
																													Español - Latinoamérica(西班牙语 - 拉丁美洲)
																													Ελληνικά(希腊语)
																													Français(法语)
																													Italiano(意大利语)
																													Bahasa Indonesia(印度尼西亚语)
																													Magyar(匈牙利语)
																													Nederlands(荷兰语)
																													Norsk(挪威语)
																													Polski(波兰语)
																													Português(葡萄牙语 - 葡萄牙)
																													Português-Brasil(葡萄牙语 - 巴西)
																													Română(罗马尼亚语)
																													Русский(俄语)
																													Suomi(芬兰语)
																													Svenska(瑞典语)
																													Türkçe(土耳其语)
																													Tiếng Việt(越南语)
																													Українська(乌克兰语)
																									报告翻译问题
							
						
 
											 
													







<!-- Locust Armor -->
<Operation Class="PatchOperationAdd">
<xpath>Defs/ThingDef[defName="Apparel_ArmorLocust"]/apparel</xpath>
<value>
<layers Inherit="False">
<li>Middle</li>
<li>Shell</li>
</layers>
</value>
</Operation>
Inherit="False" in the <layers> element tells it no to inherit any the value for <layers> from it's parent.
Play as conservatively as you wish.
Sounds OP if you can or does the mod prevent it somehow?
So if I set base to skin/middle and then set locust armor to middle/outer via PatchOperationAdd, locust armor will then attain all three layers: skin/middle/outer.
There must be good reason you went through the trouble of deleting layers from the parent def and then patching them back in for the individual armor & prestige version?
Y'know, for armour stat trolling purposes.
If anything maybe.. you could make a separate armor instead of a replacement?
just gotta wait for a Medieval Overhaul version where my fancy moral guide can have armor and style
Great mod, just have one quick question. On start-up I get a duplicate XML error for recon, prestige recon and locus. Doesn't seem to be causing problems but the error persists on a fresh install where this is the only mod. Any idea whats causing the error?
But I feel many people probably just assume that things like dusters provide negligible armor when that isn't true, and if they want to stick close to vanilla balance they should be aware of what they're installing and how it can completely shift balance to make recon armor objectively superior to marine armor rather than a tradeoff. I'm merely pointing out that the fact you can't do this in vanilla isn't an oversight, its a conscious balance decision, and that this mod is more than cosmetic.
A normal quality set of recon armor and a normal quality devilstrand duster will provide superior protection compared to same quality marine armor. If that marine armor is worn over a devilstrand shirt and pants then the upper body protection will be the same, except for heat which recon + duster protects from better, or WORSE on the lower body.
Obviously mod the game however you like, just be aware that combining recon armor with outer apparel can be a bit overpowered, and if that bothers you maybe reconsider using this.