Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
This was validated with LW2 (in principle, similar to "LWotoc" as well) way back in 2017 while considering the spawn process of custom "armors" as defined by *OUR* templates (MrShadow could explain in details).
If another mod interferes with activation of any suits, it has nothing to do with Vanilla or NOT! There are provisions already within the uc script(s) to hook Armors at common default assets when necessary.
Nothing stops users from just trying a quick install to verify.
Unsubscribe as you wish - i recommend the AML loader that can easily detect conflicts.