Installa Steam
Accedi
|
Lingua
简体中文 (cinese semplificato)
繁體中文 (cinese tradizionale)
日本語 (giapponese)
한국어 (coreano)
ไทย (tailandese)
Български (bulgaro)
Čeština (ceco)
Dansk (danese)
Deutsch (tedesco)
English (inglese)
Español - España (spagnolo - Spagna)
Español - Latinoamérica (spagnolo dell'America Latina)
Ελληνικά (greco)
Français (francese)
Indonesiano
Magyar (ungherese)
Nederlands (olandese)
Norsk (norvegese)
Polski (polacco)
Português (portoghese - Portogallo)
Português - Brasil (portoghese brasiliano)
Română (rumeno)
Русский (russo)
Suomi (finlandese)
Svenska (svedese)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraino)
Segnala un problema nella traduzione
Making "just a skin mod" is actually harder than it should be in Sandstorm since you technically have to enable that skin blueprint as a weapon upgrade
...And to enable those weapon upgrade to be used, you have to list them on the theater files and so on and on
Well if you really want to make your own theater I guess copy how a theater replacement mutator work? Eg. FullyLoaded (Where it replaces the default theater w/ override) then make your custom mutator refer to a copied default theater
Then start tweaking that default theater you copied, add new upgrades, make rifleman use advisors' primaries, etc.
DagZede:
Should be the same as the mutator blueprint inside the \Mutators\ folder of your mod file
Divine Lotus: my case was not "Mutator_Divine_Collection_Skins" but "DivineCollection" (Was actually "Divine Collection" ... Use the mutator's display name, inside the Mutator you created.
Note from DagZede:
You can name them however you want really, but yeah custom skins that we make for our own will clash with another custom theaters like ISMC cause they edit the "game's theater" and you can't have two at the same time