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
2. in the editor export the loadout asset to json
3. copypaste the changed loadout from InstantAction.json into the newly exported editor loadout json
4. import it back to the editor loadout asset
OH wow ok.
So they are not attached internally then?
I thought the mods had to be attached at a mod level.
Had no idea it worked this way.
So nee mod cannot connect and read resources from the other mod within the editor then?
Or is your method just quicker and easier?
Once it is imported will i have to create entries in mechhealth and the other mech file for the new variant, and will i have access to the mda/loadout/etc files so i can set year availability and weapon tiers etc?
Mech loadout / MDA / Unitcard mods can be packed without the referenced assets existing in the editor.
I am trying to use that function. Just so i can make an aux mech variant pack that uses weapons and what it from my existing mod.
Can the mods be internally tied together so that i can pull from my source mods resources?
If yes, what are the steps as that is the end goal?
THANKS.