Original Post — Direct link

Hello all.
As the title says, my Dev Kit is freezing for infinity, when i'm trying to do 'anything' with the PrimalGameData_BP file.
Im trying to copy it, to make a 'New Dino' mod.

Anyone know how to fix it?
Thanks

External link →
over 5 years ago - /u/ZenRowe - Direct link

A couple bits of information here

1) Make a child of the PrimalGameData_BP not a copy. In fact you should do this for any files unless you have a specific reason to make something a copy.

2) When you load a file (Copying, deleting, and even just right clicking one causes it to be loaded) all of the files it references also get loaded, and in turn all of the files those reference get loaded. In order for the devkit to load many types of files a relevant DDC file must be generated first (These files are needed when actually cooking the mod)
When you load a PGD you actually end up loading most of the game into memory. This is a long process, especially the very first time you are doing it after installing the devkit.

While it's doing this it will appear as if the devkit has locked up. Depending on how much RAM and CPU you have I have heard of it taking up to 40 minutes the first time (and a few out of memory errors from compiling the DDC as of late due to content expansions). You can launch the devkit from the ARKDevKit.bat (in your installation root) which will load the devkit with a secondary log window. The log will continue to feed information even while the devkit looks like it's locked up, allowing you to see what it's doing.

over 5 years ago - /u/ZenRowe - Direct link

Originally posted by Brainzaw

Aha! I understand now, Thanks! But what exactly is the difference on a daughter and a copy? And how do i make a daughter?

The difference is in what is inherited.A copy does not inherit the data from the blueprint you copied from, it creates duplicates, which in turn mean that the duplicated data will not be recognized as the same as the original. any changes to the original class will also not be inherited.

I child inherits the functions and data from the parent you made it from. think of it like you make a child of the the "Meat" class, and call it "Steak". "Steak" would inherit all of the properties of meat, it would also qualify as "meat" when doing a test for the kind of class something is. If you had made a copy then "Steak" would not also qualify at "Meat" in code.

To make a child you can drag a blueprint into your mod folder, and from the options you want to select the one for "Child" or you can right click a blueprint and select "Make Child" and then just move the newly created blueprint to your mod folder.