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
Fixed.
I think a EngramOverride would work just fine, we would just need the engramentry name. :)
Mod config options go in GameUserSettings.ini and those are mod implemented.
And outside of \Mods is all the vanilla assets that can be referenced for spawn commands or overrides etc. Overrides just usually use the asset name as the "class name" suffixed with _C.
For instance if you look in this mod's folder under \Items you will find an asset file called "UMD_Item_DinoUpgrade_Plus_One_Random" so its class as you have in that override is "UMD_Item_DinoUpgrade_Plus_One_Random_C". And then the craft requirements are specified similarly using class names.. if you dig down into vanilla assets I believe somewhere like \PrimalEarth\CoreBlueprints\Resources you will find PrimalItemResource_Hide asset file so its class is PrimalItemResource_Hide_C.
Anyway, way more than you probably wanted but maybe it will help somebody. I used to use this info before I started writing mods, to determine spawns or overrides myself for mods whose authors couldnt be bothered to provide them. :D