https://wiki.arkmodding.net/api.php?action=feedcontributions&user=Woeful+Macabre&feedformat=atomARK Modding Wiki - User contributions [en]2024-03-28T17:17:40ZUser contributionsMediaWiki 1.33.0https://wiki.arkmodding.net/index.php?title=FAQ&diff=46617FAQ2020-07-10T19:17:49Z<p>Woeful Macabre: </p>
<hr />
<div>[[Category:Modding]]<br />
__FORCETOC__<br />
= '''GENERAL''' =<br />
<br />
== How do I get the ARK Devkit? ==<br />
The only way for the initial download of the ARK Devkit is through the Epic Games Launcher.<br />
<br />
== How do I move the Editor to a new folder/drive? ==<br />
The Launcher currently lacks the ability to do this natively, but it can be done still either by "tricking" it or moving it and forcing it to verify the existing files. The simplest route is using a directory junction(aka [https://docs.microsoft.com/en-us/windows/desktop/fileio/symbolic-links Symbolic Link]) pointing from the old location to the new location.<br />
<br />
=== Using a Symbolic Link ===<br />
To do this make sure you've exited the launcher, then navigate to the folder that contains the Editor installation(for example '''C:\Program Files\Epic Games\''') and you will want to either copy then delete, or just outright move the '''ARKDevKit''' folder to your desired location. <br />
<br />
Once this is done, you will need to open Command Prompt as Admin(really just to prevent folder permission errors) and use the '''MKLINK''' command. The syntax of the command is important here, using the aforementioned path as an example, the command will look as follows(adapt to your specifics):<br />
<br />
'''MKLINK /J "C:\Program Files\Epic Games\ARKDevKit" "H:\ARKDevKit"'''<br />
<br />
If the link was successful, you will get a message stating as much and you're done. You can verify this by running the Epic Launcher and launching the Editor.<br />
<br />
'''NOTES:''' <br />
* The '''MKLINK''' command syntax requires arguments or switches first(the /J(Junction) switch) then it requires the '''link''' target - this is to be the folder that points to another location, after which comes the '''source''' target - this is the folder the '''link''' will point to.<br />
* This method is the simplest, requires no extra space, has some minor risk from incorrect command usage and day-to-day caveats but they're unlikely to be encountered in normal usage.<br />
<br />
=== Change the actual Installation ===<br />
If you would rather just prefer to move the folder to a new location and have it register then you can do the following.<br />
<br />
Before proceeding, you should - and actually must - back up your DevKit installation first. So wherever it is installed(eg: '''C:\Program Files\Epic Games\'''), you need to copy that elsewhere so you will need a decent chunk of free space to do this.<br />
<br />
After you've backed it up, '''uninstall''' the Editor from within the Launcher, when it is done I would recommend restarting your machine to be safe. When ready, '''install''' the Editor again at your desired location, let it go through the process of starting the download, preferably until it hits at least 1% to be safe.<br />
<br />
Once this happens, pause the install/download and kill the launcher in Task Manager, then either move or copy and paste the Editor backup to the new install location you chose when re-installing the Editor, start the launcher when it's done copying and let the launcher proceed to install - it may look like it's going to continue installing but it should eventually switch to '''Verifying'''.<br />
<br />
'''Epic' own guidance on this:''' [https://www.epicgames.com/help/en-US/epic-games-store-c73/launcher-support-c82/can-the-epic-games-launcher-detect-previously-installed-games-a3820 Epic Games Support]<br />
<br />
'''NOTES:''' <br />
* This has the chance to not work correctly and carries the highest risk, that is why it is recommended to copy instead of move files. This however necessitates many hundreds of gigabytes of free space to carry out the method, by way of copying the Editor twice, without the risk of being forced to completely re-download the Editor.<br />
* If you've reformatted onto a new drive, or have recently reinstalled the launcher for one reason or another and want to reconnect the Editor to the launcher, you can perform the same process as above for moving it, just start at the new install point for the launcher and proceed from there.<br />
<br />
== How do I test my mod? ==<br />
There are two ways you can do this. The first is to upload the mod to a second workshop entry and the second is to use the '''Test Mod Output Directory''' field.<br />
<br />
=== Using a second workshop item for testing ===<br />
The process for this is actually pretty simple, it only involves editing the '''Mods.db''' file in '''"..\ARKEditor\Projects\ShooterGame\Saved\.."'''.<br />
<br />
With the cook/upload window '''CLOSED''', open this file in a competent text editor, Notepad++ is a good choice. Do '''not''' use Windows Notepad, it cannot handle the format of the file properly and will either revert changes or invalidate it in the eyes of the Editor.<br />
<br />
Inside that file, you're going to look for the group pertaining to the mod you want to create a second entry for. A search(most likely '''CTRL + F''' in your text editor) for the name of the folder your mod is in will do this. From there you need to copy and paste the entire mod entry so you have a second entry - see [https://imgur.com/a/M9nrXIk here] for the expected final result.<br />
<br />
Once you have the second entry, in the second entry change the Title and Description values to something else and make the following changes '''"ChangeNotes": ""''' & '''"ItemSeamId": ""'''. Once you've done that, save the file and now you can open the cook/upload window in your Editor and the second entry should be visible in the list on the left. Make sure you setup the new entry as you normally would for an upload, then click Upload.<br />
<br />
=== Using "Test Mod Output Directory" for mod testing ===<br />
When you populate this field it's easier to use '''...\Mods''' in your ARK install, when you then start the Cook, the Editor will compile a Windows-only version of the mod much faster than a full cook(it will also include extraneous files but these can be ignored for the time being). This, in turn, will create a file called '''123456789.mod''' and a folder of the same name containing two "meta" data/info files. It will also create a folder that has the same name as the folder containing your Mod in the Editor - so for a folder in your Editor called '''MyMod''', there will be a folder of the same name in the directory you chose to cook too. The actual files for the mod are found here and must be moved into the aforementioned '''123456789''' folder. If you wish to test on a server, then you must copy/upload the '''123456789.mod''' and '''123456789''' folder to the server' '''...\Mods''' folder as well.<br />
<br />
'''NOTE:''' You '''must not''' have this field populated before cooking your mod if you wish to upload it. If you have cooked your mod with this field filled, clear it, and cook again before attempting to upload.<br />
<br />
== What files do I need for a mod? ==<br />
The minimal setup for a mod is:<br />
<br />
*'''PrimalGameData:''' - Create a child of PrimalGameDataBP<br />
*'''Level:''' - Create a new blank level file in your mod folder<br />
<br />
Open the level file(you will see a black screen, don't worry) and select the "World Settings" tab. If you don't have the tab up go to "Window" in the main menu bar and tick "World Settings".<br />
In the "World Settings" panel, look for the "PrimalGameData Override" and set it to the PrimalGameData in your mod folder. To get back to the TestMap, go to the '''Maps''' folder in the content browser and open it again, or go to File > Open Level... and find the TestMap in the same place.<br />
<br />
== How do I import the source files for a mod(tutorial, project take-over, etc.)? ==<br />
To import the source files of a mod - remember that you '''cannot''' import the cooked/compiled files for a mod - either copy the '''root/base''' folder for the mod, or extract the '''root/base''' folder if the mod was sourced via an archive of some form(.7z, .zip, .rar, etc.), to '''"..\ARKEditor\Projects\ShooterGame\Content\Mods\.."''' folder with the DevKit '''closed'''.<br />
<br />
'''NOTE:''' Do '''NOT''' change any file or folder names outside of the Editor - in Explorer for instance - as doing so will cause the files to lose their inheritance and reference paths when you load the DevKit next potentially making the mod unusable to you if you're unaware of what you're doing until you delete and re-do the copy/extraction process.<br />
<br />
= '''UE4 BLUEPRINT/VISUAL SCRIPT''' =<br />
<br />
== Epic Games Tutorials/References ==<br />
https://docs.unrealengine.com/en-US/Engine/Blueprints/index.html<br /><br />
https://www.unrealengine.com/en-US/blog/blueprint-basics<br />
<br />
== Third Party Tutorials/References ==<br />
[https://www.youtube.com/c/VirtusEdu/playlists DevSquad Learning Hub]<br />
<br />
== Community Tutorials/References ==<br />
[https://www.youtube.com/playlist?list=PL2o1TY9xh_JsmbgQfSCydfT-7OSdvxsVR Wildcard Workshop - ZenRowe]<br /><br />
[https://www.youtube.com/channel/UCotU5jcEtaTq2U-eJb0nczg/playlists Exilog]<br />
<br />
= '''MAPPING''' =<br />
<br />
== Why do I only see an ocean when I load up TheIsland? ==<br />
By default, the editor only loads the TheIsland persistent level to save resources. You need to load the sublevels you want to see/edit through the "Levels" tab.<br />
If you don't see the "Levels" tab go to "Window" in the main menu bar and tick "Levels". That should bring up the tab. You can then load the required sublevels by double-clicking on the name.<br />
<br />
== Troubleshooting ==</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=FAQ&diff=46616FAQ2020-07-10T19:16:52Z<p>Woeful Macabre: </p>
<hr />
<div>[[Category:Modding]]<br />
__FORCETOC__<br />
= '''GENERAL''' =<br />
<br />
== How do I get the ARK Devkit? ==<br />
The only way for the initial download of the ARK Devkit is through the Epic Games Launcher.<br />
<br />
== How do I move the Editor to a new folder/drive? ==<br />
The Launcher currently lacks the ability to do this natively, but it can be done still either by "tricking" it or moving it and forcing it to verify the existing files. The simplest route is using a directory junction(aka [https://docs.microsoft.com/en-us/windows/desktop/fileio/symbolic-links Symbolic Link]) pointing from the old location to the new location.<br />
<br />
=== Using a Symbolic Link ===<br />
To do this make sure you've exited the launcher, then navigate to the folder that contains the Editor installation(for example '''C:\Program Files\Epic Games\''') and you will want to either copy then delete, or just outright move the '''ARKDevKit''' folder to your desired location. <br />
<br />
Once this is done, you will need to open Command Prompt as Admin(really just to prevent folder permission errors) and use the '''MKLINK''' command. The syntax of the command is important here, using the aforementioned path as an example, the command will look as follows(adapt to your specifics):<br />
<br />
'''MKLINK /J "C:\Program Files\Epic Games\ARKDevKit" "H:\ARKDevKit"'''<br />
<br />
If the link was successful, you will get a message stating as much and you're done. You can verify this by running the Epic Launcher and launching the Editor.<br />
<br />
'''NOTES:''' <br />
* The '''MKLINK''' command syntax requires arguments or switches first(the /J(Junction) switch) then it requires the '''link''' target - this is to be the folder that points to another location, after which comes the '''source''' target - this is the folder the '''link''' will point to.<br />
* This method is the simplest, requires no extra space, has some minor risk from incorrect command usage and day-to-day caveats but they're unlikely to be encountered in normal usage.<br />
<br />
=== Change the actual Installation ===<br />
If you would rather just prefer to move the folder to a new location and have it register then you can do the following.<br />
<br />
Before proceeding, you should - and actually must - back up your DevKit installation first. So wherever it is installed(eg: '''C:\Program Files\Epic Games\'''), you need to copy that elsewhere so you will need a decent chunk of free space to do this.<br />
<br />
After you've backed it up, '''uninstall''' the Editor from within the Launcher, when it is done I would recommend restarting your machine to be safe. When ready, '''install''' the Editor again at your desired location, let it go through the process of starting the download, preferably until it hits at least 1% to be safe.<br />
<br />
Once this happens, pause the install/download and kill the launcher in Task Manager, then either move or copy and paste the Editor backup to the new install location you chose when re-installing the Editor, start the launcher when it's done copying and let the launcher proceed to install - it may look like it's going to continue installing but it should eventually switch to '''Verifying'''.<br />
<br />
'''Epic' own guidance on this:''' [https://www.epicgames.com/help/en-US/epic-games-store-c73/launcher-support-c82/can-the-epic-games-launcher-detect-previously-installed-games-a3820 Epic Games Support]<br />
<br />
'''NOTES:''' <br />
* This has the chance to not work correctly and carries the highest risk, that is why it is recommended to copy instead of move files. This however necessitates many hundreds of gigabytes of free space to carry out the method, by way of copying the Editor twice, without the risk of being forced to completely re-download the Editor.<br />
* If you've reformatted onto a new drive, or have recently reinstalled the launcher for one reason or another and want to reconnect the Editor to the launcher, you can perform the same process as above for moving it, just start at the new install point for the launcher and proceed from there.<br />
<br />
== How do I test my mod? ==<br />
There are two ways you can do this. The first is to upload the mod to a second workshop entry and the second is to use the '''Test Mod Output Directory''' field.<br />
<br />
=== Using a second workshop item for testing ===<br />
The process for this is actually pretty simple, it only involves editing the '''Mods.db''' file in '''"..\ARKEditor\Projects\ShooterGame\Saved\.."'''.<br />
<br />
With the cook/upload window '''CLOSED''', open this file in a competent text editor, Notepad++ is a good choice. Do '''not''' use Windows Notepad, it cannot handle the format of the file properly and will either revert changes or invalidate it in the eyes of the Editor.<br />
<br />
Inside that file, you're going to look for the group pertaining to the mod you want to create a second entry for. A search(most likely '''CTRL + F''' in your text editor) for the name of the folder your mod is in will do this. From there you need to copy and paste the entire mod entry so you have a second entry - see [https://imgur.com/a/M9nrXIk here] for the expected final result.<br />
<br />
Once you have the second entry, in the second entry change the Title and Description values to something else and make the following changes '''"ChangeNotes": ""''' & '''"ItemSeamId": ""'''. Once you've done that, save the file and now you can open the cook/upload window in your Editor and the second entry should be visible in the list on the left. Make sure you setup the new entry as you normally would for an upload, then click Upload.<br />
<br />
=== Using "Test Mod Output Directory" for mod testing ===<br />
When you populate this field it's easier to use '''...\Mods''' in your ARK install, when you then start the Cook, the Editor will compile a Windows-only version of the mod much faster than a full cook(it will also include extraneous files but these can be ignored for the time being). This, in turn, will create a file called '''123456789.mod''' and a folder of the same name containing two "meta" data/info files. It will also create a folder that has the same name as the folder containing your Mod in the Editor - so for a folder in your Editor called '''MyMod''', there will be a folder of the same name in the directory you chose to cook too. The actual files for the mod are found here and must be moved into the aforementioned '''123456789''' folder. If you wish to test on a server, then you must copy/upload the '''123456789.mod''' and '''123456789''' folder to the server' '''...\Mods''' folder as well.<br />
<br />
'''NOTE:''' You '''must not''' have this field populated before cooking your mod if you wish to upload it. If you have cooked your mod with this field filled, clear it, and cook again before attempting to upload.<br />
<br />
== What files do I need for a mod? ==<br />
The minimal setup for a mod is:<br />
<br />
*'''PrimalGameData:''' - Create a child of PrimalGameDataBP<br />
*'''Level:''' - Create a new blank level file in your mod folder<br />
<br />
Open the level file(you will see a black screen, don't worry) and select the "World Settings" tab. If you don't have the tab up go to "Window" in the main menu bar and tick "World Settings".<br />
In the "World Settings" panel, look for the "PrimalGameData Override" and set it to the PrimalGameData in your mod folder. To get back to the TestMap, go to the '''Maps''' folder in the content browser and open it again, or go to File > Open Level... and find the TestMap in the same place.<br />
<br />
== How do I import the source files for a mod(tutorial, project take-over, etc.)? ==<br />
To import the source files of a mod - remember that you '''cannot''' import the cooked/compiled files for a mod - either copy the '''root/base''' folder for the mod, or extract the '''root/base''' folder if the mod was sourced via an archive of some form(.7z, .zip, .rar, etc.), to '''"..\ARKEditor\Projects\ShooterGame\Content\Mods\.."''' folder with the DevKit '''closed'''.<br />
<br />
'''NOTE:''' Do '''NOT''' change any file or folder names outside of the Editor - in Explorer for instance - as doing so will cause the files to lose their inheritance and reference paths when you load the DevKit next potentially making the mod unusable to you if you're unaware of what you're doing until you delete and re-do the copy/extraction process.<br />
<br />
= '''UE4 BLUEPRINT/VISUAL SCRIPT''' =<br />
<br />
== Epic Games Tutorials/References ==<br />
https://docs.unrealengine.com/en-US/Engine/Blueprints/index.html<br />
https://www.unrealengine.com/en-US/blog/blueprint-basics<br />
<br />
== Third Party Tutorials/References ==<br />
[https://www.youtube.com/c/VirtusEdu/playlists DevSquad Learning Hub]<br />
<br />
== Community Tutorials/References ==<br />
[https://www.youtube.com/playlist?list=PL2o1TY9xh_JsmbgQfSCydfT-7OSdvxsVR Wildcard Workshop - ZenRowe]<br />
[https://www.youtube.com/channel/UCotU5jcEtaTq2U-eJb0nczg/playlists Exilog]<br />
<br />
= '''MAPPING''' =<br />
<br />
== Why do I only see an ocean when I load up TheIsland? ==<br />
By default, the editor only loads the TheIsland persistent level to save resources. You need to load the sublevels you want to see/edit through the "Levels" tab.<br />
If you don't see the "Levels" tab go to "Window" in the main menu bar and tick "Levels". That should bring up the tab. You can then load the required sublevels by double-clicking on the name.<br />
<br />
== Troubleshooting ==</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=FAQ&diff=3504FAQ2018-11-24T08:35:27Z<p>Woeful Macabre: Added Symbolic Link instructions, touched up and reformatted some manual relocation instructions.</p>
<hr />
<div>[[Category:Modding]]<br />
__FORCETOC__<br />
= '''GENERAL''' =<br />
<br />
== How do I get the ARK Devkit? ==<br />
The only way for the initial download of the ARK Devkit is through the Epic Games Launcher. If you see the ARK Dev Kit on Steam, do '''NOT''' download that version that, it is severely outdated and unusable!<br />
<br />
After the initial download, you can either keep it up to date through the Epic Games Launcher or manually through Github and content diff download.<br />
<br />
;Epic Games Launcher:<br />
:+ You are able to verify your devkit files in case you messed something up(much like verifying a game's files on steam).<br />
:+ Easy to use<br />
:- Every update requires you to have as much free disk space as a full install, this is only to start the download of the update regardless of the updates actual size. This can be impossible if you have limited disk space available.<br />
:- Updates usually take some time to arrive on the Epic Games Launcher.<br />
<br />
;Manual Updates:<br />
:+ Gets around the free disk space problem of the Epic Games Launcher.<br />
:+ Updates are available immediately.<br />
:- No verification of the files.<br />
<br />
== How do I move the Editor to a new folder/drive? ==<br />
The Launcher lacks the ability to do this natively, but it can be done still either by "tricking" it or moving it and forcing it to verify the existing files. The simplest route is using a directory junction(aka [https://docs.microsoft.com/en-us/windows/desktop/fileio/symbolic-links Symbolic Link]) pointing from the old location to the new location.<br />
<br />
<br />
===Using a Symbolic Link===<br />
<br />
To do this make sure you've exited the launcher, then navigate to the folder that contains the Editor installation(for example '''C:\Program Files\Epic Games\''') and you will want to either copy then delete, or just outright move the '''ARKDevKit''' folder to your desired location. <br />
<br />
Once this is done, you will need to open Command Prompt as Admin(really just to prevent folder permission errors) and use the '''MKLINK''' command. The syntax of the command is important here, using the aforementioned path as an example, the command will look as follows(adapt to your specifics):<br />
<br />
'''MKLINK /J "C:\Program Files\Epic Games\ARKDevKit" "H:\ARKDevKit"'''<br />
<br />
If the link was successful, you will get a message stating as much and you're done. You can verify this by running the Epic Launcher and launching the Editor.<br />
<br />
'''NOTES:''' <br />
* The '''MKLINK''' command syntax requires arguments or switches first(the /J(Junction) switch) then it requires the '''link''' target - this is to be the folder that points to another location, after which comes the '''source''' target - this is the folder the '''link''' will point to.<br />
* This method is the simplest, requires no extra space, has some minor risk from incorrect command usage and day-to-day caveats but they're unlikely to be encountered in normal usage.<br />
<br />
<br />
===Change the actual Installation===<br />
<br />
If you would rather just prefer to move the folder to a new location and have it register then you can do the following.<br />
<br />
Before proceeding, you should - and actually must - back up your DevKit installation first. So wherever it is installed(eg: '''C:\Program Files\Epic Games\'''), you need to copy that elsewhere so you will need a decent chunk of free space to do this.<br />
<br />
After you've backed it up, '''uninstall''' the Editor from within the Launcher, when it is done I would recommend restarting your machine to be safe. When ready, '''install''' the Editor again at your desired location, let it go through the process of starting the download, preferably until it hits at least 1% to be safe.<br />
<br />
Once this happens, pause the install/download and kill the launcher in Task Manager, then either move or copy and paste the Editor backup to the new install location you chose when re-installing the Editor, start the launcher when it's done copying and let the launcher proceed to install - it may look like it's going to continue installing but it should eventually switch to '''Verifying'''.<br />
<br />
<br />
'''NOTES:''' <br />
* This has the chance to not work correctly and carries the highest risk, that is why it is recommended to copy instead of move files. This however necessitates many hundreds of gigabytes of free space to carry out the method, by way of copying the Editor twice, without the risk of being forced to completely redownload the Editor.<br />
* If you've reformatted onto a new drive, or have recently reinstalled the launcher for one reason or another and want to reconnect the Editor to the launcher, you can perform the same process as above for moving it, just start at the new install point for the launcher and proceed from there.<br />
<br />
== How do I apply the Devkit "beta" update releases(Google Drive Content Diff)? ==<br />
Such updates are provided first through a Google-drive hosted content diff archive and will be announced on the ARK Modding discord by Staff or an otherwise permitted User once the update has been vetted to be free of crash-inducing bugs. Once the update has been pushed to the Epic Launcher, the Google Drive link will be removed from the Unreal Engine forum thread.<br />
<br />
To download the Content-Diff, click the provided drive.google.com link, either in the announcement or dedicated Unreal Engine forum thread link(one or the other will be provided), and follow the prompts to download the archive. '''Warning:''' The size of this archive can range wildly in size, anywhere from 1GB or upwards of 10GB's.<br />
<br />
Once you have the Content diff, extract the archive over the root folder of your DevKit install (see image). When you extract, overwrite all files found in your install directory when prompted, then when complete you may launch the DevKit with the .bat file called '''ARKDevKit.bat''' and continue as normal.[[File:DevKit Root Install.png|thumb|right|View of DevKit install root, where archives get extracted.]]<br />
<br />
'''NOTE:''' The launch .bat is required because once you update manually, and once the update makes its way to the Launcher, the only option available to you in the Launcher will be '''Update''', you will not be able to launch it from there until you have updated via the launcher also.<br />
<br />
== How do I test my mod? ==<br />
There are two ways you can do this. The first is to upload the mod to a second workshop entry - a process which will be detailed at a later date, and the second is to use the '''Test Mod Output Directory''' field. This is the one detailed below.<br />
<br />
When you populate this field it's easier to use '''...\Mods''' in your ARK install, when you then start the Cook, the Editor will compile a Windows-only version of the mod much faster than a full cook(it will also include extraneous files but these can be ignored for the time being). This, in turn, will create a file called '''123456789.mod''' and a folder of the same name containing two "meta" data/info files. It will also create a folder that has the same name as the folder containing your Mod in the Editor - so for a folder in your Editor called '''MyMod''', there will be a folder of the same name in the directory you chose to cook too. The actual files for the mod are found here and must be moved into the aforementioned '''123456789''' folder. If you wish to test on a server, then you must copy/upload the '''123456789.mod''' and '''123456789''' folder to the server' '''...\Mods''' folder as well.<br />
<br />
'''NOTE:''' You '''must not''' have this field populated before cooking your mod if you wish to upload it. If you have cooked your mod with this field filled, clear it, and cook again before attempting to upload.<br />
<br />
== What files do I need for a mod? ==<br />
The minimal setup for a mod is:<br />
<br />
*'''PrimalGameData:''' - Create a child of PrimalGameDataBP<br />
*'''Level:''' - Create a new blank level file in your mod folder<br />
<br />
Open the level file(you will see a black screen, don't worry) and select the "World Settings" tab. If you don't have the tab up go to "Window" in the main menu bar and tick "World Settings".<br />
In the "World Settings" panel, look for the "PrimalGameData Override" and set it to the PrimalGameData in your mod folder. To get back to the TestMap, go to the '''Maps''' folder in the content browser and open it again, or go to File > Open Level... and find the TestMap in the same place.<br />
<br />
== How do I import the source files for a mod(tutorial, project take-over, etc.)? ==<br />
To import the source files of a mod - remember that you '''cannot''' import the cooked/compiled files for a mod - either copy the '''root/base''' folder for the mod, or extract the '''root/base''' folder if the mod was sourced via an archive of some form(.7z, .zip, .rar, etc.), to the '''...\Mods\''' folder of your DevKit install with the DevKit '''closed'''. For example, I would extract the '''root''' folder of a mod' source files to '''"I:\ARKDevKit\Projects\ShooterGame\Content\Mods\..."'''.<br />
<br />
'''NOTE:''' Do '''NOT''' change any file or folder names as doing so will cause the files to lose their inheritance and reference paths when you load the DevKit next potentially making the mod unusable to you if you're unaware of what you're doing until you delete and re-do the copy/extraction process.<br />
<br />
= '''SCRIPTING''' =<br />
<br />
== How do I get a "Cast" node? ==<br />
You need to drag from a blue/purple pin and have the "Context sensitive" checkbox ticked to get the cast to options to show up.<br />
<br />
= '''MAPPING''' =<br />
<br />
== Why do I only see an ocean when I load up TheIsland? ==<br />
By default, the editor only loads the TheIsland persistent level to save resources. You need to load the sublevels you want to see/edit through the "Levels" tab.<br />
If you don't see the "Levels" tab go to "Window" in the main menu bar and tick "Levels". That should bring up the tab. You can then load the required sublevels by double-clicking on the name.<br />
<br />
== Troubleshooting ==</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=FAQ&diff=2035FAQ2018-08-23T00:42:11Z<p>Woeful Macabre: </p>
<hr />
<div>[[Category:Modding]]<br />
__FORCETOC__<br />
= '''GENERAL''' =<br />
<br />
== How do I get the ARK Devkit? ==<br />
The only way for the initial download of the ARK Devkit is through the Epic Games Launcher. If you see the ARK Dev Kit on Steam, do '''NOT''' download that version that, it is severely outdated and unusable!<br />
<br />
After the initial download, you can either keep it up to date through the Epic Games Launcher or manually through Github and content diff download.<br />
<br />
;Epic Games Launcher:<br />
:+ You are able to verify your devkit files in case you messed something up(much like verifying a game's files on steam).<br />
:+ Easy to use<br />
:- Every update requires you to have as much free disk space as a full install, this is only to start the download of the update regardless of the updates actual size. This can be impossible if you have limited disk space available.<br />
:- Updates usually take some time to arrive on the Epic Games Launcher.<br />
<br />
;Manual Updates:<br />
:+ Gets around the free disk space problem of the Epic Games Launcher.<br />
:+ Updates are available immediately.<br />
:- No verification of the files.<br />
<br />
== How do I move the Devkit? ==<br />
The Launcher lacks the ability to do this natively, but it can be done still by "tricking it". To do this you should back up your DevKit installation first. So wherever it is installed(eg: '''C:\Program Files\Epic Games\ARKDevKit\'''), you need to copy that elsewhere so you will need a decent chunk of free space to do this.<br />
<br />
After you've backed it up, '''uninstall''' the Editor from within the Launcher, when it is done I would recommend just restarting to be safe. When ready, '''install''' the Editor again at your desired location, let it go through the process of downloading until it hits at least 1% to be safe. <br />
Once this happens, kill the launcher in Task Manager, copy and paste the Editor backup where you made the new install location you chose when re-installing the Editor, start the launcher when it's done copying and let the launcher proceed to install - it may look like it's going to continue installing but it will eventually switch to '''Verifying'''.<br />
<br />
'''NOTES:''' <br />
* This has the chance to not work correctly so that is why it is recommended to copy instead of move files.<br />
* If you've reformatted onto a new drive, or have recently reinstalled the launcher for one reason or another and want to reconnect the Editor to the launcher, you can perform the same process as above for moving it, just start at the new install point for the launcher and proceed from there.<br />
* If you lack the free space to potentially have two copies of the entire Editor on your machine at once, then you can use a symbolic link instead. Refer to google on how to perform this action.<br />
<br />
== How do I apply the Devkit "beta" update releases(Google Drive Content Diff)? ==<br />
Such updates are provided first through a Google-drive hosted content diff archive and will be announced on the ARK Modding discord by Staff or an otherwise permitted User once the update has been vetted to be free of crash-inducing bugs. Once the update has been pushed to the Epic Launcher, the Google Drive link will be removed from the Unreal Engine forum thread.<br />
<br />
To download the Content-Diff, click the provided drive.google.com link, either in the announcement or dedicated Unreal Engine forum thread link(one or the other will be provided), and follow the prompts to download the archive. '''Warning:''' The size of this archive can range wildly in size, anywhere from 1GB or upwards of 10GB's.<br />
<br />
Once you have the Content diff, extract the archive over the root folder of your DevKit install (see image). When you extract, overwrite all files found in your install directory when prompted, then when complete you may launch the DevKit with the .bat file called '''ARKDevKit.bat''' and continue as normal.[[File:DevKit Root Install.png|thumb|right|View of DevKit install root, where archives get extracted.]]<br />
<br />
'''NOTE:''' The launch .bat is required because once you update manually, and once the update makes its way to the Launcher, the only option available to you in the Launcher will be '''Update''', you will not be able to launch it from there until you have updated via the launcher also.<br />
<br />
== How do I test my mod? ==<br />
There are two ways you can do this. The first is to upload the mod to a second workshop entry - a process which will be detailed at a later date, and the second is to use the '''Test Mod Output Directory''' field. This is the one detailed below.<br />
<br />
When you populate this field it's easier to use '''...\Mods''' in your ARK install, when you then start the Cook, the Editor will compile a Windows-only version of the mod much faster than a full cook(it will also include extraneous files but these can be ignored for the time being). This, in turn, will create a file called '''123456789.mod''' and a folder of the same name containing two "meta" data/info files. It will also create a folder that has the same name as the folder containing your Mod in the Editor - so for a folder in your Editor called '''MyMod''', there will be a folder of the same name in the directory you chose to cook too. The actual files for the mod are found here and must be moved into the aforementioned '''123456789''' folder. If you wish to test on a server, then you must copy/upload the '''123456789.mod''' and '''123456789''' folder to the server' '''...\Mods''' folder as well.<br />
<br />
'''NOTE:''' You '''must not''' have this field populated before cooking your mod if you wish to upload it. If you have cooked your mod with this field filled, clear it, and cook again before attempting to upload.<br />
<br />
== What files do I need for a mod? ==<br />
The minimal setup for a mod is:<br />
<br />
*'''PrimalGameData:''' - Create a child of PrimalGameDataBP<br />
*'''Level:''' - Create a new blank level file in your mod folder<br />
<br />
Open the level file(you will see a black screen, don't worry) and select the "World Settings" tab. If you don't have the tab up go to "Window" in the main menu bar and tick "World Settings".<br />
In the "World Settings" panel, look for the "PrimalGameData Override" and set it to the PrimalGameData in your mod folder. To get back to the TestMap, go to the '''Maps''' folder in the content browser and open it again, or go to File > Open Level... and find the TestMap in the same place.<br />
<br />
== How do I import the source files for a mod(tutorial, project take-over, etc.)? ==<br />
To import the source files of a mod - remember that you '''cannot''' import the cooked/compiled files for a mod - either copy the '''root/base''' folder for the mod, or extract the '''root/base''' folder if the mod was sourced via an archive of some form(.7z, .zip, .rar, etc.), to the '''...\Mods\''' folder of your DevKit install with the DevKit '''closed'''. For example, I would extract the '''root''' folder of a mod' source files to '''"I:\ARKDevKit\Projects\ShooterGame\Content\Mods\..."'''.<br />
<br />
'''NOTE:''' Do '''NOT''' change any file or folder names as doing so will cause the files to lose their inheritance and reference paths when you load the DevKit next potentially making the mod unusable to you if you're unaware of what you're doing until you delete and re-do the copy/extraction process.<br />
<br />
= '''SCRIPTING''' =<br />
<br />
== How do I get a "Cast" node? ==<br />
You need to drag from a blue/purple pin and have the "Context sensitive" checkbox ticked to get the cast to options to show up.<br />
<br />
= '''MAPPING''' =<br />
<br />
== Why do I only see an ocean when I load up TheIsland? ==<br />
By default, the editor only loads the TheIsland persistent level to save resources. You need to load the sublevels you want to see/edit through the "Levels" tab.<br />
If you don't see the "Levels" tab go to "Window" in the main menu bar and tick "Levels". That should bring up the tab. You can then load the required sublevels by double-clicking on the name.<br />
<br />
== Troubleshooting ==</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=FAQ&diff=2034FAQ2018-08-23T00:41:45Z<p>Woeful Macabre: Some formatting, grammar fixes, restructuring of text, etc.</p>
<hr />
<div>[[Category:Modding]]<br />
__FORCETOC__<br />
= '''GENERAL''' =<br />
<br />
== How do I get the ARK Devkit? ==<br />
The only way for the initial download of the ARK Devkit is through the Epic Games Launcher. If you see the ARK Dev Kit on Steam, do '''NOT''' download that version that, it is severely outdated and unusable!<br />
<br />
After the initial download, you can either keep it up to date through the Epic Games Launcher or manually through Github and content diff download.<br />
<br />
;Epic Games Launcher:<br />
:+ You are able to verify your devkit files in case you messed something up(much like verifying a game's files on steam).<br />
:+ Easy to use<br />
:- Every update requires you to have as much free disk space as a full install, this is only to start the download of the update regardless of the updates actual size. This can be impossible if you have limited disk space available.<br />
:- Updates usually take some time to arrive on the Epic Games Launcher.<br />
<br />
;Manual Updates:<br />
:+ Gets around the free disk space problem of the Epic Games Launcher.<br />
:+ Updates are available immediately.<br />
:- No verification of the files.<br />
<br />
== # How do I move the Devkit? ==<br />
The Launcher lacks the ability to do this natively, but it can be done still by "tricking it". To do this you should back up your DevKit installation first. So wherever it is installed(eg: '''C:\Program Files\Epic Games\ARKDevKit\'''), you need to copy that elsewhere so you will need a decent chunk of free space to do this.<br />
<br />
After you've backed it up, '''uninstall''' the Editor from within the Launcher, when it is done I would recommend just restarting to be safe. When ready, '''install''' the Editor again at your desired location, let it go through the process of downloading until it hits at least 1% to be safe. <br />
Once this happens, kill the launcher in Task Manager, copy and paste the Editor backup where you made the new install location you chose when re-installing the Editor, start the launcher when it's done copying and let the launcher proceed to install - it may look like it's going to continue installing but it will eventually switch to '''Verifying'''.<br />
<br />
'''NOTES:''' <br />
* This has the chance to not work correctly so that is why it is recommended to copy instead of move files.<br />
* If you've reformatted onto a new drive, or have recently reinstalled the launcher for one reason or another and want to reconnect the Editor to the launcher, you can perform the same process as above for moving it, just start at the new install point for the launcher and proceed from there.<br />
* If you lack the free space to potentially have two copies of the entire Editor on your machine at once, then you can use a symbolic link instead. Refer to google on how to perform this action.<br />
<br />
== How do I apply the Devkit "beta" update releases(Google Drive Content Diff)? ==<br />
Such updates are provided first through a Google-drive hosted content diff archive and will be announced on the ARK Modding discord by Staff or an otherwise permitted User once the update has been vetted to be free of crash-inducing bugs. Once the update has been pushed to the Epic Launcher, the Google Drive link will be removed from the Unreal Engine forum thread.<br />
<br />
To download the Content-Diff, click the provided drive.google.com link, either in the announcement or dedicated Unreal Engine forum thread link(one or the other will be provided), and follow the prompts to download the archive. '''Warning:''' The size of this archive can range wildly in size, anywhere from 1GB or upwards of 10GB's.<br />
<br />
Once you have the Content diff, extract the archive over the root folder of your DevKit install (see image). When you extract, overwrite all files found in your install directory when prompted, then when complete you may launch the DevKit with the .bat file called '''ARKDevKit.bat''' and continue as normal.[[File:DevKit Root Install.png|thumb|right|View of DevKit install root, where archives get extracted.]]<br />
<br />
'''NOTE:''' The launch .bat is required because once you update manually, and once the update makes its way to the Launcher, the only option available to you in the Launcher will be '''Update''', you will not be able to launch it from there until you have updated via the launcher also.<br />
<br />
== How do I test my mod? ==<br />
There are two ways you can do this. The first is to upload the mod to a second workshop entry - a process which will be detailed at a later date, and the second is to use the '''Test Mod Output Directory''' field. This is the one detailed below.<br />
<br />
When you populate this field it's easier to use '''...\Mods''' in your ARK install, when you then start the Cook, the Editor will compile a Windows-only version of the mod much faster than a full cook(it will also include extraneous files but these can be ignored for the time being). This, in turn, will create a file called '''123456789.mod''' and a folder of the same name containing two "meta" data/info files. It will also create a folder that has the same name as the folder containing your Mod in the Editor - so for a folder in your Editor called '''MyMod''', there will be a folder of the same name in the directory you chose to cook too. The actual files for the mod are found here and must be moved into the aforementioned '''123456789''' folder. If you wish to test on a server, then you must copy/upload the '''123456789.mod''' and '''123456789''' folder to the server' '''...\Mods''' folder as well.<br />
<br />
'''NOTE:''' You '''must not''' have this field populated before cooking your mod if you wish to upload it. If you have cooked your mod with this field filled, clear it, and cook again before attempting to upload.<br />
<br />
== What files do I need for a mod? ==<br />
The minimal setup for a mod is:<br />
<br />
*'''PrimalGameData:''' - Create a child of PrimalGameDataBP<br />
*'''Level:''' - Create a new blank level file in your mod folder<br />
<br />
Open the level file(you will see a black screen, don't worry) and select the "World Settings" tab. If you don't have the tab up go to "Window" in the main menu bar and tick "World Settings".<br />
In the "World Settings" panel, look for the "PrimalGameData Override" and set it to the PrimalGameData in your mod folder. To get back to the TestMap, go to the '''Maps''' folder in the content browser and open it again, or go to File > Open Level... and find the TestMap in the same place.<br />
<br />
== How do I import the source files for a mod(tutorial, project take-over, etc.)? ==<br />
To import the source files of a mod - remember that you '''cannot''' import the cooked/compiled files for a mod - either copy the '''root/base''' folder for the mod, or extract the '''root/base''' folder if the mod was sourced via an archive of some form(.7z, .zip, .rar, etc.), to the '''...\Mods\''' folder of your DevKit install with the DevKit '''closed'''. For example, I would extract the '''root''' folder of a mod' source files to '''"I:\ARKDevKit\Projects\ShooterGame\Content\Mods\..."'''.<br />
<br />
'''NOTE:''' Do '''NOT''' change any file or folder names as doing so will cause the files to lose their inheritance and reference paths when you load the DevKit next potentially making the mod unusable to you if you're unaware of what you're doing until you delete and re-do the copy/extraction process.<br />
<br />
= '''SCRIPTING''' =<br />
<br />
== How do I get a "Cast" node? ==<br />
You need to drag from a blue/purple pin and have the "Context sensitive" checkbox ticked to get the cast to options to show up.<br />
<br />
= '''MAPPING''' =<br />
<br />
== Why do I only see an ocean when I load up TheIsland? ==<br />
By default, the editor only loads the TheIsland persistent level to save resources. You need to load the sublevels you want to see/edit through the "Levels" tab.<br />
If you don't see the "Levels" tab go to "Window" in the main menu bar and tick "Levels". That should bring up the tab. You can then load the required sublevels by double-clicking on the name.<br />
<br />
== Troubleshooting ==</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=User:Woeful_Macabre&diff=2033User:Woeful Macabre2018-08-23T00:11:27Z<p>Woeful Macabre: Nop.</p>
<hr />
<div>The beginning and the end of all.</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=FAQ&diff=1790FAQ2018-06-23T19:37:06Z<p>Woeful Macabre: /* How do I move the Devkit? */</p>
<hr />
<div>[[Category:Modding]]<br />
__FORCETOC__<br />
==General==<br />
<br />
===How do I get the ARK Devkit?===<br />
The only way for the initial download of the ARK Devkit is through the Epic Games Launcher. Do '''NOT''' download the version that is on Steam, it is severely outdated and unusable!<br />
After the initial download, you can either keep it up to date through the Epic Games Launcher or manually through Github and content diff download.<br />
<br />
;Epic Games Launcher:<br />
:+ You are able to verify your devkit files in case you messed something up(much like verifying a game's files on steam).<br />
:+ Easy to use<br />
:- Every update requires you to have as much free disk space as a full install, this is only to start the download of the update regardless of the updates actual size. This can be impossible if you have limited disk space available.<br />
:- Devkit Updates usually take longer until they are available on the Epic Games Launcher.<br />
<br />
;Manual Updates:<br />
:+ Gets around the free diskspace problem of the Epic Games Launcher.<br />
:+ Updates are available faster.<br />
:- No verification of the files.<br />
<br />
===How do I move the Devkit?===<br />
The Launcher lacks the ability to do this natively, but it can be done still by "tricking it". To do this you need to backup your DevKit installation. So wherever it is installed(eg: '''C:\Program Files\Epic Games\ARKDevKit\'''), you need to copy that elsewhere so you will need a decent chunk of free space to do this.<br />
<br />
After you've backed it up, '''uninstall''' the Editor from within the Launcher, when it is done I would recommend just restarting to be safe. When ready, '''install''' the Editor again at your desired location, let it go through the process of downloading until it hits at least 1% to be safe. <br />
Once this happens, kill the launcher in Task Manager, copy and paste the Editor backup where you made the new install location you chose when re-installing the Editor, start the launcher when it's done copying and let the launcher proceed to install - it may look like it's going to continue installing but it will eventually switch to '''Verifying'''.<br />
<br />
'''NOTE:''' This has the chance to not work correctly so that is why it is recommended to copy instead of move files. <br />'''NOTE 2:''' If you've reformatted onto a new drive, or have recently reinstalled the launcher for one reason or another and want to reconnect the Editor to the launcher, you can perform the same process as above for moving it, just start at the new install point for the launcher and proceed from there. <br />'''NOTE 3:''' If you lack the free space to potentially have two copies of the entire Editor on your machine at once, then you can use a symbolic link instead. Refer to google on how to perform this action.<br />
<br />
===How do I update the Devkit for early manual-update releases without the Epic Games Launcher (Google Drive Content Diff)?===<br />
Updates are provided first through a Google-drive hosted content diff archive and will be announced on the ARK Modding discord by Staff or an otherwise permitted User once the update has been vetted to be free of crash-inducing bugs. After a period of time, the Google Drive link will be removed from the forum thread<br />
<br />
To download the Content-Diff, click the provided drive.google.com link, either in the announcement or dedicated forum thread link(one or the other will be provided), and follow the prompts to download the archive. '''Warning:''' The size of this archive can range wildly in size, anywhere from 1GB or upwards of 10GB's.<br />
<br />
Once you have the Content diff, extract the archive over the root folder of your DevKit install (see image). When you extract, overwrite all files found in your install directory when prompted, then when complete you may launch the DevKit with the .bat file called '''ARKDevKit.BAT''' and continue as normal.[[File:DevKit Root Install.png|thumb|right|View of DevKit install root, where archives get extracted.]]<br />
<br />
'''NOTE:''' The bat is required to be used because once you update manually, and once the update makes its way to the Launcher, the only option available to you in the Launcher will be '''Update''', you will not be able to launch it from there until you updated via the launcher also.<br />
<br />
=== How do I test my mod? ===<br />
There are two ways you can do this. The first is to upload the mod to a second workshop entry - a process which will be detailed at a later date, and the second is to use the '''Test Mod Output Directory''' field. This is the one detailed below.<br />
<br />
When you populate this field - it's easier to use '''...\Mods''' in your ARK install - the Editor will compile a windows-only version of the mod in a fraction of the time compared to a full cook(it will also include extraneous files but these can be ignored for the time being). This, in turn, will create a file called '''123456789.mod''' and a folder of the same name containing two "meta" data/info files. It will also create a folder that has the same name as the folder for your Mod in the Editor '''...\Mods''' folder - so for a folder in your Editor called '''MyMod''', there will be a folder of the same name in the directory you chose to cook to. The actual files for the mod are here, and must be moved into the '''123456789''' folder mentioned earlier. If you wish to test on a server, then you must copy the '''123456789.mod''' and '''123456789''' folder to the server' '''...\Mods''' folder as well.<br />
<br />
'''NOTE:''' You '''must not''' have this field populated before cooking your mod if you wish to upload it. If you have cooked your mod with this field filled, clear it, and cook again before attempting to upload.<br />
<br />
=== What files do I need for a mod? ===<br />
The minimal setup for a mod is:<br />
*'''PrimalGameData:''' - Create a child of PrimalGameDataBP<br />
*'''Level:''' - Create a new blank level file in your mod folder<br />
Open the level file(you will see a black screen, don't worry) and select the "World Settings" tab. If you don't have the tab up go to "Window" in the main menu bar and tick "World Settings".<br />
In the world settings look for the "PrimalGameData Override" and set it to the PrimalGameData in your mod folder.<br />
<br />
===How do I import the source files for a mod(tutorial, project take-over, etc.)?===<br />
To import the source files of a mod - remember that you '''cannot''' import the cooked/compiled files for a mod - either copy the '''root/base''' folder for the mod, or extract the '''root/base''' folder if the mod was sourced via an archive of some form(.7z, .zip, .rar, etc.), to the '''...\Mods\''' folder of your DevKit install with the DevKit '''closed'''. For example, I would extract the '''root''' folder of a mod' source files to '''"I:\ARKDevKit\Projects\ShooterGame\Content\Mods\..."'''.<br />
<br />
'''NOTE:''' Do '''NOT''' change any file or folder names as doing so will cause the files to lose their inheritance and reference paths when you load the DevKit next potentially making the mod unusable to you if you're unaware of what you're doing until you delete and re-do the copy/extraction process.<br />
<br />
==Blueprinting==<br />
<br />
=== How do I get a "Cast" node? ===<br />
You need to drag from a blue/purple pin and have the "Context sensitive" checkbox ticked to get the cast to options to show up.<br />
<br />
==Mapping==<br />
<br />
=== Why do I only see ocean when I load up TheIsland? ===<br />
By default the editor only loads the TheIsland persistent level to save resources. You need to load the sublevels you want to see/edit through the "Levels" tab.<br />
If you don't see the "Levels" tab go to "Window" in the main menu bar and tick "Levels". That should bring up the tab. You can then load the required sublevels by double-clicking on the name.<br />
<br />
==Troubleshooting==</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=FAQ&diff=1789FAQ2018-06-23T19:35:51Z<p>Woeful Macabre: /* How do I move the Devkit? */</p>
<hr />
<div>[[Category:Modding]]<br />
__FORCETOC__<br />
==General==<br />
<br />
===How do I get the ARK Devkit?===<br />
The only way for the initial download of the ARK Devkit is through the Epic Games Launcher. Do '''NOT''' download the version that is on Steam, it is severely outdated and unusable!<br />
After the initial download, you can either keep it up to date through the Epic Games Launcher or manually through Github and content diff download.<br />
<br />
;Epic Games Launcher:<br />
:+ You are able to verify your devkit files in case you messed something up(much like verifying a game's files on steam).<br />
:+ Easy to use<br />
:- Every update requires you to have as much free disk space as a full install, this is only to start the download of the update regardless of the updates actual size. This can be impossible if you have limited disk space available.<br />
:- Devkit Updates usually take longer until they are available on the Epic Games Launcher.<br />
<br />
;Manual Updates:<br />
:+ Gets around the free diskspace problem of the Epic Games Launcher.<br />
:+ Updates are available faster.<br />
:- No verification of the files.<br />
<br />
===How do I move the Devkit?===<br />
The Launcher lacks the ability to do this natively, but it can be done still by "tricking it". To do this you need to backup your DevKit installation. So wherever it is installed(eg: '''C:\Program Files\Epic Games\ARKDevKit\'''), you need to copy that elsewhere so you will need a decent chunk of free space to do this.<br />
<br />
After you've backed it up, '''uninstall''' the Editor from within the Launcher, when it is done I would recommend just restarting to be safe. When ready, '''install''' the Editor again at your desired location, let it go through the process of downloading until it hits at least 1% to be safe. <br />
Once this happens, kill the launcher in Task Manager, copy and paste the Editor backup where you made the new install location you chose when re-installing the Editor, start the launcher when it's done copying and let the launcher proceed to install - it may look like it's going to continue installing but it will eventually switch to '''Verifying'''.<br />
<br />
{{nowrap begin}}'''NOTE:''' This has the chance to not work correctly so that is why it is recommended to copy instead of move files.{{nowrap end}}<br />
{{nowrap begin}}'''NOTE 2:''' If you've reformatted onto a new drive, or have recently reinstalled the launcher for one reason or another and want to reconnect the Editor to the launcher, you can perform the same process as above for moving it, just start at the new install point for the launcher and proceed from there.{{nowrap end}}<br />
{{nowrap begin}}'''NOTE 3:''' If you lack the free space to potentially have two copies of the entire Editor on your machine at once, then you can use a symbolic link instead. Refer to google on how to perform this action.{{nowrap end}}<br />
<br />
===How do I update the Devkit for early manual-update releases without the Epic Games Launcher (Google Drive Content Diff)?===<br />
Updates are provided first through a Google-drive hosted content diff archive and will be announced on the ARK Modding discord by Staff or an otherwise permitted User once the update has been vetted to be free of crash-inducing bugs. After a period of time, the Google Drive link will be removed from the forum thread<br />
<br />
To download the Content-Diff, click the provided drive.google.com link, either in the announcement or dedicated forum thread link(one or the other will be provided), and follow the prompts to download the archive. '''Warning:''' The size of this archive can range wildly in size, anywhere from 1GB or upwards of 10GB's.<br />
<br />
Once you have the Content diff, extract the archive over the root folder of your DevKit install (see image). When you extract, overwrite all files found in your install directory when prompted, then when complete you may launch the DevKit with the .bat file called '''ARKDevKit.BAT''' and continue as normal.[[File:DevKit Root Install.png|thumb|right|View of DevKit install root, where archives get extracted.]]<br />
<br />
'''NOTE:''' The bat is required to be used because once you update manually, and once the update makes its way to the Launcher, the only option available to you in the Launcher will be '''Update''', you will not be able to launch it from there until you updated via the launcher also.<br />
<br />
=== How do I test my mod? ===<br />
There are two ways you can do this. The first is to upload the mod to a second workshop entry - a process which will be detailed at a later date, and the second is to use the '''Test Mod Output Directory''' field. This is the one detailed below.<br />
<br />
When you populate this field - it's easier to use '''...\Mods''' in your ARK install - the Editor will compile a windows-only version of the mod in a fraction of the time compared to a full cook(it will also include extraneous files but these can be ignored for the time being). This, in turn, will create a file called '''123456789.mod''' and a folder of the same name containing two "meta" data/info files. It will also create a folder that has the same name as the folder for your Mod in the Editor '''...\Mods''' folder - so for a folder in your Editor called '''MyMod''', there will be a folder of the same name in the directory you chose to cook to. The actual files for the mod are here, and must be moved into the '''123456789''' folder mentioned earlier. If you wish to test on a server, then you must copy the '''123456789.mod''' and '''123456789''' folder to the server' '''...\Mods''' folder as well.<br />
<br />
'''NOTE:''' You '''must not''' have this field populated before cooking your mod if you wish to upload it. If you have cooked your mod with this field filled, clear it, and cook again before attempting to upload.<br />
<br />
=== What files do I need for a mod? ===<br />
The minimal setup for a mod is:<br />
*'''PrimalGameData:''' - Create a child of PrimalGameDataBP<br />
*'''Level:''' - Create a new blank level file in your mod folder<br />
Open the level file(you will see a black screen, don't worry) and select the "World Settings" tab. If you don't have the tab up go to "Window" in the main menu bar and tick "World Settings".<br />
In the world settings look for the "PrimalGameData Override" and set it to the PrimalGameData in your mod folder.<br />
<br />
===How do I import the source files for a mod(tutorial, project take-over, etc.)?===<br />
To import the source files of a mod - remember that you '''cannot''' import the cooked/compiled files for a mod - either copy the '''root/base''' folder for the mod, or extract the '''root/base''' folder if the mod was sourced via an archive of some form(.7z, .zip, .rar, etc.), to the '''...\Mods\''' folder of your DevKit install with the DevKit '''closed'''. For example, I would extract the '''root''' folder of a mod' source files to '''"I:\ARKDevKit\Projects\ShooterGame\Content\Mods\..."'''.<br />
<br />
'''NOTE:''' Do '''NOT''' change any file or folder names as doing so will cause the files to lose their inheritance and reference paths when you load the DevKit next potentially making the mod unusable to you if you're unaware of what you're doing until you delete and re-do the copy/extraction process.<br />
<br />
==Blueprinting==<br />
<br />
=== How do I get a "Cast" node? ===<br />
You need to drag from a blue/purple pin and have the "Context sensitive" checkbox ticked to get the cast to options to show up.<br />
<br />
==Mapping==<br />
<br />
=== Why do I only see ocean when I load up TheIsland? ===<br />
By default the editor only loads the TheIsland persistent level to save resources. You need to load the sublevels you want to see/edit through the "Levels" tab.<br />
If you don't see the "Levels" tab go to "Window" in the main menu bar and tick "Levels". That should bring up the tab. You can then load the required sublevels by double-clicking on the name.<br />
<br />
==Troubleshooting==</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=FAQ&diff=1788FAQ2018-06-23T19:25:43Z<p>Woeful Macabre: /* How do I update the Devkit for early manual-update releases without the Epic Games Launcher (Google Drive Content Diff)? */</p>
<hr />
<div>[[Category:Modding]]<br />
__FORCETOC__<br />
==General==<br />
<br />
===How do I get the ARK Devkit?===<br />
The only way for the initial download of the ARK Devkit is through the Epic Games Launcher. Do '''NOT''' download the version that is on Steam, it is severely outdated and unusable!<br />
After the initial download, you can either keep it up to date through the Epic Games Launcher or manually through Github and content diff download.<br />
<br />
;Epic Games Launcher:<br />
:+ You are able to verify your devkit files in case you messed something up(much like verifying a game's files on steam).<br />
:+ Easy to use<br />
:- Every update requires you to have as much free disk space as a full install, this is only to start the download of the update regardless of the updates actual size. This can be impossible if you have limited disk space available.<br />
:- Devkit Updates usually take longer until they are available on the Epic Games Launcher.<br />
<br />
;Manual Updates:<br />
:+ Gets around the free diskspace problem of the Epic Games Launcher.<br />
:+ Updates are available faster.<br />
:- No verification of the files.<br />
<br />
===How do I move the Devkit?===<br />
The Launcher lacks the ability to do this natively, but it can be done still by "tricking it". To do this you need to backup your DevKit installation. So wherever it is installed(eg: '''C:\Program Files\Epic Games\ARKDevKit\'''), you need to copy that elsewhere so you will need a decent chunk of free space to do this.<br />
<br />
After you've backed it up, '''uninstall''' the Editor from within the Launcher, when it is done I would recommend just restarting to be safe. When ready, '''install''' the Editor again at your desired location, let it go through the process of downloading until it hits at least 1% to be safe. <br />
Once this happens, kill the launcher in Task Manager, copy and paste the Editor backup where you made the new install location you chose when re-installing the Editor, start the launcher when it's done copying and let the launcher proceed to install - it may look like it's going to continue installing but it will eventually switch to '''Verifying'''.<br />
<br />
'''NOTE:''' This has the chance to not work correctly so that is why it is recommended to copy instead of move files.<br />
'''NOTE 2:''' If you've reformatted onto a new drive, or have recently reinstalled the launcher for one reason or another and want to reconnect the Editor to the launcher, you can perform the same process as above for moving it, just start at the new install point for the launcher and proceed from there.<br />
'''NOTE 3:''' If you lack the free space to potentially have two copies of the entire Editor on your machine at once, then you can use a symbolic link instead. Refer to google on how to perform this action.<br />
<br />
===How do I update the Devkit for early manual-update releases without the Epic Games Launcher (Google Drive Content Diff)?===<br />
Updates are provided first through a Google-drive hosted content diff archive and will be announced on the ARK Modding discord by Staff or an otherwise permitted User once the update has been vetted to be free of crash-inducing bugs. After a period of time, the Google Drive link will be removed from the forum thread<br />
<br />
To download the Content-Diff, click the provided drive.google.com link, either in the announcement or dedicated forum thread link(one or the other will be provided), and follow the prompts to download the archive. '''Warning:''' The size of this archive can range wildly in size, anywhere from 1GB or upwards of 10GB's.<br />
<br />
Once you have the Content diff, extract the archive over the root folder of your DevKit install (see image). When you extract, overwrite all files found in your install directory when prompted, then when complete you may launch the DevKit with the .bat file called '''ARKDevKit.BAT''' and continue as normal.[[File:DevKit Root Install.png|thumb|right|View of DevKit install root, where archives get extracted.]]<br />
<br />
'''NOTE:''' The bat is required to be used because once you update manually, and once the update makes its way to the Launcher, the only option available to you in the Launcher will be '''Update''', you will not be able to launch it from there until you updated via the launcher also.<br />
<br />
=== How do I test my mod? ===<br />
There are two ways you can do this. The first is to upload the mod to a second workshop entry - a process which will be detailed at a later date, and the second is to use the '''Test Mod Output Directory''' field. This is the one detailed below.<br />
<br />
When you populate this field - it's easier to use '''...\Mods''' in your ARK install - the Editor will compile a windows-only version of the mod in a fraction of the time compared to a full cook(it will also include extraneous files but these can be ignored for the time being). This, in turn, will create a file called '''123456789.mod''' and a folder of the same name containing two "meta" data/info files. It will also create a folder that has the same name as the folder for your Mod in the Editor '''...\Mods''' folder - so for a folder in your Editor called '''MyMod''', there will be a folder of the same name in the directory you chose to cook to. The actual files for the mod are here, and must be moved into the '''123456789''' folder mentioned earlier. If you wish to test on a server, then you must copy the '''123456789.mod''' and '''123456789''' folder to the server' '''...\Mods''' folder as well.<br />
<br />
'''NOTE:''' You '''must not''' have this field populated before cooking your mod if you wish to upload it. If you have cooked your mod with this field filled, clear it, and cook again before attempting to upload.<br />
<br />
=== What files do I need for a mod? ===<br />
The minimal setup for a mod is:<br />
*'''PrimalGameData:''' - Create a child of PrimalGameDataBP<br />
*'''Level:''' - Create a new blank level file in your mod folder<br />
Open the level file(you will see a black screen, don't worry) and select the "World Settings" tab. If you don't have the tab up go to "Window" in the main menu bar and tick "World Settings".<br />
In the world settings look for the "PrimalGameData Override" and set it to the PrimalGameData in your mod folder.<br />
<br />
===How do I import the source files for a mod(tutorial, project take-over, etc.)?===<br />
To import the source files of a mod - remember that you '''cannot''' import the cooked/compiled files for a mod - either copy the '''root/base''' folder for the mod, or extract the '''root/base''' folder if the mod was sourced via an archive of some form(.7z, .zip, .rar, etc.), to the '''...\Mods\''' folder of your DevKit install with the DevKit '''closed'''. For example, I would extract the '''root''' folder of a mod' source files to '''"I:\ARKDevKit\Projects\ShooterGame\Content\Mods\..."'''.<br />
<br />
'''NOTE:''' Do '''NOT''' change any file or folder names as doing so will cause the files to lose their inheritance and reference paths when you load the DevKit next potentially making the mod unusable to you if you're unaware of what you're doing until you delete and re-do the copy/extraction process.<br />
<br />
==Blueprinting==<br />
<br />
=== How do I get a "Cast" node? ===<br />
You need to drag from a blue/purple pin and have the "Context sensitive" checkbox ticked to get the cast to options to show up.<br />
<br />
==Mapping==<br />
<br />
=== Why do I only see ocean when I load up TheIsland? ===<br />
By default the editor only loads the TheIsland persistent level to save resources. You need to load the sublevels you want to see/edit through the "Levels" tab.<br />
If you don't see the "Levels" tab go to "Window" in the main menu bar and tick "Levels". That should bring up the tab. You can then load the required sublevels by double-clicking on the name.<br />
<br />
==Troubleshooting==</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=FAQ&diff=1787FAQ2018-06-23T19:25:09Z<p>Woeful Macabre: /* How do I update the Devkit without the Epic Games Launcher(Github and Content Diff)? */</p>
<hr />
<div>[[Category:Modding]]<br />
__FORCETOC__<br />
==General==<br />
<br />
===How do I get the ARK Devkit?===<br />
The only way for the initial download of the ARK Devkit is through the Epic Games Launcher. Do '''NOT''' download the version that is on Steam, it is severely outdated and unusable!<br />
After the initial download, you can either keep it up to date through the Epic Games Launcher or manually through Github and content diff download.<br />
<br />
;Epic Games Launcher:<br />
:+ You are able to verify your devkit files in case you messed something up(much like verifying a game's files on steam).<br />
:+ Easy to use<br />
:- Every update requires you to have as much free disk space as a full install, this is only to start the download of the update regardless of the updates actual size. This can be impossible if you have limited disk space available.<br />
:- Devkit Updates usually take longer until they are available on the Epic Games Launcher.<br />
<br />
;Manual Updates:<br />
:+ Gets around the free diskspace problem of the Epic Games Launcher.<br />
:+ Updates are available faster.<br />
:- No verification of the files.<br />
<br />
===How do I move the Devkit?===<br />
The Launcher lacks the ability to do this natively, but it can be done still by "tricking it". To do this you need to backup your DevKit installation. So wherever it is installed(eg: '''C:\Program Files\Epic Games\ARKDevKit\'''), you need to copy that elsewhere so you will need a decent chunk of free space to do this.<br />
<br />
After you've backed it up, '''uninstall''' the Editor from within the Launcher, when it is done I would recommend just restarting to be safe. When ready, '''install''' the Editor again at your desired location, let it go through the process of downloading until it hits at least 1% to be safe. <br />
Once this happens, kill the launcher in Task Manager, copy and paste the Editor backup where you made the new install location you chose when re-installing the Editor, start the launcher when it's done copying and let the launcher proceed to install - it may look like it's going to continue installing but it will eventually switch to '''Verifying'''.<br />
<br />
'''NOTE:''' This has the chance to not work correctly so that is why it is recommended to copy instead of move files.<br />
'''NOTE 2:''' If you've reformatted onto a new drive, or have recently reinstalled the launcher for one reason or another and want to reconnect the Editor to the launcher, you can perform the same process as above for moving it, just start at the new install point for the launcher and proceed from there.<br />
'''NOTE 3:''' If you lack the free space to potentially have two copies of the entire Editor on your machine at once, then you can use a symbolic link instead. Refer to google on how to perform this action.<br />
<br />
===How do I update the Devkit for early manual-update releases without the Epic Games Launcher (Google Drive Content Diff)?===<br />
Updates are provided first through a Google-drive hosted content diff archive and will be announced on the ARK Modding discord by Staff or an other-wise permitted User once the update has been vetted to be free of crash-inducing bugs. After a period of time, the Google Drive link will be removed from the forum thread<br />
<br />
To download the Content-Diff, click the provided drive.google.com link, either in the announcement or dedicated forum thread link(one or the other will be provided), and follow the prompts to download the archive. '''Warning:''' The size of this archive can range wildly in size, anywhere from 1GB or upwards of 10GB's.<br />
<br />
Once you have the Content diff, extract the archive over the root folder of your DevKit install (see image). When you extract, overwrite all files found in your install directory when prompted, then when complete you may launch the DevKit with the .bat file called '''ARKDevKit.BAT''' and continue as normal.[[File:DevKit Root Install.png|thumb|right|View of DevKit install root, where archives get extracted.]]<br />
<br />
'''NOTE:''' The bat is required to be used because once you update manually, and once the update makes its way to the Launcher, the only option available to you in the Launcher will be '''Update''', you will not be able to launch it from there until you updated via the launcher also.<br />
<br />
=== How do I test my mod? ===<br />
There are two ways you can do this. The first is to upload the mod to a second workshop entry - a process which will be detailed at a later date, and the second is to use the '''Test Mod Output Directory''' field. This is the one detailed below.<br />
<br />
When you populate this field - it's easier to use '''...\Mods''' in your ARK install - the Editor will compile a windows-only version of the mod in a fraction of the time compared to a full cook(it will also include extraneous files but these can be ignored for the time being). This, in turn, will create a file called '''123456789.mod''' and a folder of the same name containing two "meta" data/info files. It will also create a folder that has the same name as the folder for your Mod in the Editor '''...\Mods''' folder - so for a folder in your Editor called '''MyMod''', there will be a folder of the same name in the directory you chose to cook to. The actual files for the mod are here, and must be moved into the '''123456789''' folder mentioned earlier. If you wish to test on a server, then you must copy the '''123456789.mod''' and '''123456789''' folder to the server' '''...\Mods''' folder as well.<br />
<br />
'''NOTE:''' You '''must not''' have this field populated before cooking your mod if you wish to upload it. If you have cooked your mod with this field filled, clear it, and cook again before attempting to upload.<br />
<br />
=== What files do I need for a mod? ===<br />
The minimal setup for a mod is:<br />
*'''PrimalGameData:''' - Create a child of PrimalGameDataBP<br />
*'''Level:''' - Create a new blank level file in your mod folder<br />
Open the level file(you will see a black screen, don't worry) and select the "World Settings" tab. If you don't have the tab up go to "Window" in the main menu bar and tick "World Settings".<br />
In the world settings look for the "PrimalGameData Override" and set it to the PrimalGameData in your mod folder.<br />
<br />
===How do I import the source files for a mod(tutorial, project take-over, etc.)?===<br />
To import the source files of a mod - remember that you '''cannot''' import the cooked/compiled files for a mod - either copy the '''root/base''' folder for the mod, or extract the '''root/base''' folder if the mod was sourced via an archive of some form(.7z, .zip, .rar, etc.), to the '''...\Mods\''' folder of your DevKit install with the DevKit '''closed'''. For example, I would extract the '''root''' folder of a mod' source files to '''"I:\ARKDevKit\Projects\ShooterGame\Content\Mods\..."'''.<br />
<br />
'''NOTE:''' Do '''NOT''' change any file or folder names as doing so will cause the files to lose their inheritance and reference paths when you load the DevKit next potentially making the mod unusable to you if you're unaware of what you're doing until you delete and re-do the copy/extraction process.<br />
<br />
==Blueprinting==<br />
<br />
=== How do I get a "Cast" node? ===<br />
You need to drag from a blue/purple pin and have the "Context sensitive" checkbox ticked to get the cast to options to show up.<br />
<br />
==Mapping==<br />
<br />
=== Why do I only see ocean when I load up TheIsland? ===<br />
By default the editor only loads the TheIsland persistent level to save resources. You need to load the sublevels you want to see/edit through the "Levels" tab.<br />
If you don't see the "Levels" tab go to "Window" in the main menu bar and tick "Levels". That should bring up the tab. You can then load the required sublevels by double-clicking on the name.<br />
<br />
==Troubleshooting==</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=FAQ&diff=1786FAQ2018-06-23T19:23:10Z<p>Woeful Macabre: Removed all references to Github process for manual updates.</p>
<hr />
<div>[[Category:Modding]]<br />
__FORCETOC__<br />
==General==<br />
<br />
===How do I get the ARK Devkit?===<br />
The only way for the initial download of the ARK Devkit is through the Epic Games Launcher. Do '''NOT''' download the version that is on Steam, it is severely outdated and unusable!<br />
After the initial download, you can either keep it up to date through the Epic Games Launcher or manually through Github and content diff download.<br />
<br />
;Epic Games Launcher:<br />
:+ You are able to verify your devkit files in case you messed something up(much like verifying a game's files on steam).<br />
:+ Easy to use<br />
:- Every update requires you to have as much free disk space as a full install, this is only to start the download of the update regardless of the updates actual size. This can be impossible if you have limited disk space available.<br />
:- Devkit Updates usually take longer until they are available on the Epic Games Launcher.<br />
<br />
;Manual Updates:<br />
:+ Gets around the free diskspace problem of the Epic Games Launcher.<br />
:+ Updates are available faster.<br />
:- No verification of the files.<br />
<br />
===How do I move the Devkit?===<br />
The Launcher lacks the ability to do this natively, but it can be done still by "tricking it". To do this you need to backup your DevKit installation. So wherever it is installed(eg: '''C:\Program Files\Epic Games\ARKDevKit\'''), you need to copy that elsewhere so you will need a decent chunk of free space to do this.<br />
<br />
After you've backed it up, '''uninstall''' the Editor from within the Launcher, when it is done I would recommend just restarting to be safe. When ready, '''install''' the Editor again at your desired location, let it go through the process of downloading until it hits at least 1% to be safe. <br />
Once this happens, kill the launcher in Task Manager, copy and paste the Editor backup where you made the new install location you chose when re-installing the Editor, start the launcher when it's done copying and let the launcher proceed to install - it may look like it's going to continue installing but it will eventually switch to '''Verifying'''.<br />
<br />
'''NOTE:''' This has the chance to not work correctly so that is why it is recommended to copy instead of move files.<br />
'''NOTE 2:''' If you've reformatted onto a new drive, or have recently reinstalled the launcher for one reason or another and want to reconnect the Editor to the launcher, you can perform the same process as above for moving it, just start at the new install point for the launcher and proceed from there.<br />
'''NOTE 3:''' If you lack the free space to potentially have two copies of the entire Editor on your machine at once, then you can use a symbolic link instead. Refer to google on how to perform this action.<br />
<br />
===How do I update the Devkit without the Epic Games Launcher(Github and Content Diff)?===<br />
Updates are provided first through a Google-drive hosted content diff archive and will be announced on the ARK Modding discord by Staff or an other-wise permitted User once the update has been vetted to be free of crash-inducing bugs. After a period of time, the Google Drive link will be removed from the forum thread<br />
<br />
To download the Content-Diff, click the provided drive.google.com link, either in the announcement or dedicated forum thread link(one or the other will be provided), and follow the prompts to download the archive. '''Warning:''' The size of this archive can range wildly in size, anywhere from 1GB or upwards of 10GB's.<br />
<br />
Once you have the Content diff, extract the archive over the root folder of your DevKit install (see image). When you extract, overwrite all files found in your install directory when prompted, then when complete you may launch the DevKit with the .bat file called '''ARKDevKit.BAT''' and continue as normal.[[File:DevKit Root Install.png|thumb|right|View of DevKit install root, where archives get extracted.]]<br />
<br />
'''NOTE:''' The bat is required to be used because once you update manually, and once the update makes its way to the Launcher, the only option available to you in the Launcher will be '''Update''', you will not be able to launch it from there until you updated via the launcher also.<br />
<br />
=== How do I test my mod? ===<br />
There are two ways you can do this. The first is to upload the mod to a second workshop entry - a process which will be detailed at a later date, and the second is to use the '''Test Mod Output Directory''' field. This is the one detailed below.<br />
<br />
When you populate this field - it's easier to use '''...\Mods''' in your ARK install - the Editor will compile a windows-only version of the mod in a fraction of the time compared to a full cook(it will also include extraneous files but these can be ignored for the time being). This, in turn, will create a file called '''123456789.mod''' and a folder of the same name containing two "meta" data/info files. It will also create a folder that has the same name as the folder for your Mod in the Editor '''...\Mods''' folder - so for a folder in your Editor called '''MyMod''', there will be a folder of the same name in the directory you chose to cook to. The actual files for the mod are here, and must be moved into the '''123456789''' folder mentioned earlier. If you wish to test on a server, then you must copy the '''123456789.mod''' and '''123456789''' folder to the server' '''...\Mods''' folder as well.<br />
<br />
'''NOTE:''' You '''must not''' have this field populated before cooking your mod if you wish to upload it. If you have cooked your mod with this field filled, clear it, and cook again before attempting to upload.<br />
<br />
=== What files do I need for a mod? ===<br />
The minimal setup for a mod is:<br />
*'''PrimalGameData:''' - Create a child of PrimalGameDataBP<br />
*'''Level:''' - Create a new blank level file in your mod folder<br />
Open the level file(you will see a black screen, don't worry) and select the "World Settings" tab. If you don't have the tab up go to "Window" in the main menu bar and tick "World Settings".<br />
In the world settings look for the "PrimalGameData Override" and set it to the PrimalGameData in your mod folder.<br />
<br />
===How do I import the source files for a mod(tutorial, project take-over, etc.)?===<br />
To import the source files of a mod - remember that you '''cannot''' import the cooked/compiled files for a mod - either copy the '''root/base''' folder for the mod, or extract the '''root/base''' folder if the mod was sourced via an archive of some form(.7z, .zip, .rar, etc.), to the '''...\Mods\''' folder of your DevKit install with the DevKit '''closed'''. For example, I would extract the '''root''' folder of a mod' source files to '''"I:\ARKDevKit\Projects\ShooterGame\Content\Mods\..."'''.<br />
<br />
'''NOTE:''' Do '''NOT''' change any file or folder names as doing so will cause the files to lose their inheritance and reference paths when you load the DevKit next potentially making the mod unusable to you if you're unaware of what you're doing until you delete and re-do the copy/extraction process.<br />
<br />
==Blueprinting==<br />
<br />
=== How do I get a "Cast" node? ===<br />
You need to drag from a blue/purple pin and have the "Context sensitive" checkbox ticked to get the cast to options to show up.<br />
<br />
==Mapping==<br />
<br />
=== Why do I only see ocean when I load up TheIsland? ===<br />
By default the editor only loads the TheIsland persistent level to save resources. You need to load the sublevels you want to see/edit through the "Levels" tab.<br />
If you don't see the "Levels" tab go to "Window" in the main menu bar and tick "Levels". That should bring up the tab. You can then load the required sublevels by double-clicking on the name.<br />
<br />
==Troubleshooting==</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=FAQ&diff=999FAQ2018-04-05T04:15:25Z<p>Woeful Macabre: Added instructions for moving the DevKit install without a SymLink.</p>
<hr />
<div>__FORCETOC__<br />
==General==<br />
<br />
===How do I get the ARK Devkit?===<br />
The only way for the initial download of the ARK Devkit is through the Epic Games Launcher. Do '''NOT''' download the version that is on Steam, it is severely outdated and unusable!<br />
After the initial download, you can either keep it up to date through the Epic Games Launcher or manually through Github and content diff download.<br />
<br />
;Epic Games Launcher:<br />
:+ You are able to verify your devkit files in case you messed something up(much like verifying a game's files on steam).<br />
:+ Easy to use<br />
:- Every update requires you to have as much free disk space as a full install, this is only to start the download of the update regardless of the updates actual size. This can be impossible if you have limited disk space available.<br />
:- Devkit Updates usually take longer until they are available on the Epic Games Launcher.<br />
<br />
;Manual Updates:<br />
:+ Gets around the free diskspace problem of the Epic Games Launcher.<br />
:+ Updates are available faster.<br />
:- No verification of the files.<br />
<br />
===How do I move the Devkit?===<br />
The Launcher lacks the ability to do this natively, but it can be done still by "tricking it". To do this you need to backup your DevKit installation. So wherever it is installed(eg: '''C:\Program Files\Epic Games\ARKDevKit\'''), you need to copy that elsewhere so you will need a decent chunk of free space to do this.<br />
<br />
After you've backed it up, '''uninstall''' the Editor from within the Launcher, when it is done I would recommend just restarting to be safe. When ready, '''install''' the Editor again at your desired location, let it go through the process of downloading until it hits at least 1% to be safe. <br />
Once this happens, kill the launcher in Task Manager, copy and paste the Editor backup where you made the new install location you chose when re-installing the Editor, start the launcher when it's done copying and let the launcher proceed to install - it may look like it's going to continue installing but it will eventually switch to '''Verifying'''.<br />
<br />
'''NOTE:''' This has the chance to not work correctly so that is why it is recommended to copy instead of move files.<br />
'''NOTE 2:''' If you've reformatted onto a new drive, or have recently reinstalled the launcher for one reason or another and want to reconnect the Editor to the launcher, you can perform the same process as above for moving it, just start at the new install point for the launcher and proceed from there.<br />
'''NOTE 3:''' If you lack the free space to potentially have two copies of the entire Editor on your machine at once, then you can use a symbolic link instead. Refer to google on how to perform this action.<br />
<br />
===How do I update the Devkit without the Epic Games Launcher(Github and Content Diff)?===<br />
Updates are usually provided first through GitHub(binaries) and a Google-drive hosted content diff archive and will be announced on the ARKModding discord by an Admin once the update has been vetted to be free of crash-inducing bugs. To update you need '''BOTH''' the binaries from GitHub and the content diff package.<br />
<br />
To download the Github Binaries, you '''must''' be a member of Epic' organisation on Github. You do this by creating a Github account first, if you don't have one already, then you will need to proceed to [https://www.epicgames.com/account/settings?productName=epicgames your Epic Games account settings] and specify the username you used for your Github account in the '''Github Account Name''' field(see first image)[[File:Epic Account Settings.png|thumb|right|Put the GitHub account name in the highlighted field.]]<br />
<br />
You should then, either immediately or sometime after clicking "Save", receive an email with an offer to join Epic's Github organisation, which gives you access to the UE4 source repository and the DevKit binaries repository. To download the binaries, click on the green '''Clone or Download''' button and then '''Download ZIP'''.<br />
<br />
To download the Content-Diff, click the provided drive.google.com link and follow the prompts to download the archive. '''Warning:''' The size of this archive can range from ~1GB to ~5GB's or more.<br />
<br />
Once you have both the Google-Drive Content-diff ''and'' the Github binaries, extract them both over the root folder of your DevKit install (see the second image). When you extract both archives, overwrite all files found in your install directory when prompted, then when both are completed you may launch the DevKit with the .bat file called '''ARKDevKit.BAT''' and continue as normal.[[File:DevKit Root Install.png|thumb|right|View of DevKit install root, where archives get extracted.]]<br />
<br />
'''NOTE:''' The Github binaries archive contents are buried inside a second folder within the archive, you '''must''' extract the contents of this base folder in the archive for the update to work, you will know you're in the right place because there will be a folder called '''Engine'''. (see the third image)[[File:Binaries Archive Contents.png|thumb|right|Correct files to extract from within the GitHib archive download.]]<br />
<br />
=== How do I test my mod? ===<br />
There are two ways you can do this. The first is to upload the mod to a second workshop entry - a process which will be detailed at a later date, and the second is to use the '''Test Mod Output Directory''' field. This is the one detailed below.<br />
<br />
When you populate this field - it's easier to use '''...\Mods''' in your ARK install - the Editor will compile a windows-only version of the mod in a fraction of the time compared to a full cook(it will also include extraneous files but these can be ignored for the time being). This, in turn, will create a file called '''123456789.mod''' and a folder of the same name containing two "meta" data/info files. It will also create a folder that has the same name as the folder for your Mod in the Editor '''...\Mods''' folder - so for a folder in your Editor called '''MyMod''', there will be a folder of the same name in the directory you chose to cook to. The actual files for the mod are here, and must be moved into the '''123456789''' folder mentioned earlier. If you wish to test on a server, then you must copy the '''123456789.mod''' and '''123456789''' folder to the server' '''...\Mods''' folder as well.<br />
<br />
'''NOTE:''' You '''must not''' have this field populated before cooking your mod if you wish to upload it. If you have cooked your mod with this field filled, clear it, and cook again before attempting to upload.<br />
<br />
=== What files do I need for a mod? ===<br />
The minimal setup for a mod is:<br />
*'''PrimalGameData:''' - Create a child of PrimalGameDataBP<br />
*'''Level:''' - Create a new blank level file in your mod folder<br />
Open the level file(you will see a black screen, don't worry) and select the "World Settings" tab. If you don't have the tab up go to "Window" in the main menu bar and tick "World Settings".<br />
In the world settings look for the "PrimalGameData Override" and set it to the PrimalGameData in your mod folder.<br />
<br />
===How do I import the source files for a mod(tutorial, project take-over, etc.)?===<br />
To import the source files of a mod - remember that you '''cannot''' import the cooked/compiled files for a mod - either copy the '''root/base''' folder for the mod, or extract the '''root/base''' folder if the mod was sourced via an archive of some form(.7z, .zip, .rar, etc.), to the '''...\Mods\''' folder of your DevKit install with the DevKit '''closed'''. For example, I would extract the '''root''' folder of a mod' source files to '''"I:\ARKDevKit\Projects\ShooterGame\Content\Mods\..."'''.<br />
<br />
'''NOTE:''' Do '''NOT''' change any file or folder names as doing so will cause the files to lose their inheritance and reference paths when you load the DevKit next potentially making the mod unusable to you if you're unaware of what you're doing until you delete and re-do the copy/extraction process.<br />
<br />
==Blueprinting==<br />
<br />
=== How do I get a "Cast" node? ===<br />
You need to drag from a blue/purple pin and have the "Context sensitive" checkbox ticked to get the cast to options to show up.<br />
<br />
==Mapping==<br />
<br />
=== Why do I only see ocean when I load up TheIsland? ===<br />
By default the editor only loads the TheIsland persistent level to save resources. You need to load the sublevels you want to see/edit through the "Levels" tab.<br />
If you don't see the "Levels" tab go to "Window" in the main menu bar and tick "Levels". That should bring up the tab. You can then load the required sublevels by double-clicking on the name.<br />
<br />
==Troubleshooting==</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=FAQ&diff=916FAQ2017-05-11T14:37:26Z<p>Woeful Macabre: Added test output information.</p>
<hr />
<div>__FORCETOC__<br />
==General==<br />
<br />
===How do I get the ARK Devkit?===<br />
The only way for the initial download of the ARK Devkit is through the Epic Games Launcher. Do '''NOT''' download the version that is on Steam, it is severely outdated and unusable!<br />
After the initial download you can either keep it up to date through the Epic Games Launcher or manually through Github and content diff download.<br />
<br />
;Epic Games Launcher:<br />
:+ You are able to verify your devkit files in case you messed something up(much like verifying a games files on steam).<br />
:+ Easy to use<br />
:- Every update requires you to have as much free diskspace as a full install, this is only to start the download of the update regardless of the updates actual size. This can be impossible if you have limited diskspace available.<br />
:- Devkit Updates usually take longer until they are available on the Epic Games Launcher.<br />
<br />
;Manual Updates:<br />
:+ Gets around the free diskspace problem of the Epic Games Launcher.<br />
:+ Updates are available faster.<br />
:- No verification of the files.<br />
<br />
=== How do I update the Devkit without the Epic Games Launcher(Github and Content Diff)? ===<br />
Updates are usually provided first through github(binaries) and a Google-drive hosted content diff archive, and will be announced on the ARKModding discord by an Admin once the update has been vetted to be free of crash-inducing bugs. To update you need '''BOTH''' the binaries from github and the content diff package.<br />
<br />
To download the Github Binaries, you '''must''' be a member of Epic' organisation on Github. You do this by creating a Github account first, if you don't have one already, then you will need to proceed to [https://www.epicgames.com/account/settings?productName=epicgames your Epic Games account settings] and specify the username you used for your Github account in the '''Github Account Name''' field(see first image)[[File:Epic Account Settings.png|thumb|right|Put the GitHub account name in the highlighted field.]]<br />
<br />
You should then, either immediately or sometime after clicking "Save", receive an email with an offer to join Epic's Github organisation, which gives you access to the UE4 source repository and the DevKit binaries repository. To download the binaries, click on the green '''Clone or Download''' button and then '''Download ZIP'''.<br />
<br />
To download the Content-Diff, click the provided drive.google.com link and follow the prompts to download the archive. '''Warning:''' The size of this archive can range from ~1GB to ~5GB's or more.<br />
<br />
Once you have both the Google-Drive Content-diff ''and'' the Github binaries, extract them both over the root folder of your DevKit install (see second image). When you extract both archives, overwrite all files found in your install directory when prompted, then when both are complteted you may launch the DevKit with the .bat file called '''ARKDevKit.BAT''' and continue as normal.[[File:DevKit Root Install.png|thumb|right|View of DevKit install root, where archives get extracted.]]<br />
<br />
'''NOTE:''' The Github binaries archive contents are buried inside a second folder within the archive, you '''must''' extract the contents of this base folder in the archive for the update to work, you will know you're in the right place because there will be a folder called '''Engine'''. (see third image)[[File:Binaries Archive Contents.png|thumb|right|Correct files to extract from within the GitHib archive download.]]<br />
<br />
=== How do I test my mod? ===<br />
There are two ways you can do this. The first is to upload the mod to a second workshop entry - a process which will be detailed at a later date, and the second is to use the '''Test Mod Output Directory''' field. This is the one detailed below.<br />
<br />
When you populate this field - it's easier to use '''...\Mods''' in your ARK install - the Editor will compile a windows-only version of the mod in a fraction of the time compared to a full cook(it will also include extraneous files but these can be ignored for the time being). This, in turn, will create a file called '''123456789.mod''' and a folder of the same name containing two "meta" data/info files. It will also create a folder that has the same name as the folder for your Mod in the Editor '''...\Mods''' folder - so for a folder in your Editor called '''MyMod''', there will be a folder of the same name in the directory you chose to cook to. The actual files for the mod are here, and must be moved into the '''123456789''' folder mentioned earlier. If you wish to test on a server, then you must copy the '''123456789.mod''' and '''123456789''' folder to the server' '''...\Mods''' folder as well.<br />
<br />
'''NOTE:''' You '''must not''' have this field populated before cooking your mod if you wish to upload it. If you have cooked your mod with this field filled, clear it, and cook again before attempting to upload.<br />
<br />
=== What files do I need for a mod? ===<br />
The minimal setup for a mod is:<br />
*'''PrimalGameData:''' - Create a child of PrimalGameDataBP<br />
*'''Level:''' - Create a new blank level file in your mod folder<br />
Open the level file(you will see a black screen, don't worry) and select the "World Settings" tab. If you don't have the tab up go to "Window" in the main menu bar and tick "World Settings".<br />
In the world settings look for the "PrimalGameData Override" and set it to the PrimalGameData in your mod folder.<br />
<br />
===How do I import the source files for a mod(tutorial, project take-over, etc.)?===<br />
To import the source files of a mod - remember that you '''cannot''' import the cooked/compiled files for a mod - either copy the '''root/base''' folder for the mod, or extract the '''root/base''' folder if the mod was sourced via an archive of some form(.7z, .zip, .rar, etc.), to the '''...\Mods\''' folder of your DevKit install with the DevKit '''closed'''. For example, I would extract the '''root''' folder of a mod' source files to '''"I:\ARKDevKit\Projects\ShooterGame\Content\Mods\..."'''.<br />
<br />
'''NOTE:''' Do '''NOT''' change any file or folder names as doing so will cause the files to lose their inheritance and reference paths when you load the DevKit next potentially making the mod unusable to you if you're unaware of what you're doing until you delete and re-do the copy/extraction process.<br />
<br />
==Blueprinting==<br />
<br />
=== How do I get a "Cast" node? ===<br />
You need to drag from a blue/purple pin and have the "Context sensitive" checkbox ticked to get the cast to options to show up.<br />
<br />
==Mapping==<br />
<br />
=== Why do I only see ocean when I load up TheIsland? ===<br />
By default the editor only loads the TheIsland persistent level to save resources. You need to load the sublevels you want to see/edit through the "Levels" tab.<br />
If you don't see the "Levels" tab go to "Window" in the main menu bar and tick "Levels". That should bring up the tab. You can then load the required sublevels by double-clicking on the name.<br />
<br />
==Troubleshooting==</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=FAQ&diff=865FAQ2017-01-28T01:34:19Z<p>Woeful Macabre: </p>
<hr />
<div>__FORCETOC__<br />
==General==<br />
<br />
===How do I get the ARK Devkit?===<br />
The only way for the initial download of the ARK Devkit is through the Epic Games Launcher. Do '''NOT''' download the version that is on Steam, it is severely outdated and unusable!<br />
After the initial download you can either keep it up to date through the Epic Games Launcher or manually through Github and content diff download.<br />
<br />
;Epic Games Launcher:<br />
:+ You are able to verify your devkit files in case you messed something up(much like verifying a games files on steam).<br />
:+ Easy to use<br />
:- Every update requires you to have as much free diskspace as a full install, this is only to start the download of the update regardless of the updates actual size. This can be impossible if you have limited diskspace available.<br />
:- Devkit Updates usually take longer until they are available on the Epic Games Launcher.<br />
<br />
;Manual Updates:<br />
:+ Gets around the free diskspace problem of the Epic Games Launcher.<br />
:+ Updates are available faster.<br />
:- No verification of the files.<br />
<br />
=== How do I update the Devkit without the Epic Games Launcher(Github and Content Diff)? ===<br />
Updates are usually provided first through github(binaries) and a Google-drive hosted content diff archive, and will be announced on the ARKModding discord by an Admin once the update has been vetted to be free of crash-inducing bugs. To update you need '''BOTH''' the binaries from github and the content diff package.<br />
<br />
To download the Github Binaries, you '''must''' be a member of Epic' organisation on Github. You do this by creating a Github account first, if you don't have one already, then you will need to proceed to [https://www.epicgames.com/account/settings?productName=epicgames your Epic Games account settings] and specify the username you used for your Github account in the '''Github Account Name''' field(see first image)[[File:Epic Account Settings.png|thumb|right|Put the GitHub account name in the highlighted field.]]<br />
<br />
You should then, either immediately or sometime after clicking "Save", receive an email with an offer to join Epic's Github organisation, which gives you access to the UE4 source repository and the DevKit binaries repository. To download the binaries, click on the green '''Clone or Download''' button and then '''Download ZIP'''.<br />
<br />
To download the Content-Diff, click the provided drive.google.com link and follow the prompts to download the archive. '''Warning:''' The size of this archive can range from ~1GB to ~5GB's or more.<br />
<br />
Once you have both the Google-Drive Content-diff ''and'' the Github binaries, extract them both over the root folder of your DevKit install (see second image). When you extract both archives, overwrite all files found in your install directory when prompted, then when both are complteted you may launch the DevKit with the .bat file called '''ARKDevKit.BAT''' and continue as normal.[[File:DevKit Root Install.png|thumb|right|View of DevKit install root, where archives get extracted.]]<br />
<br />
'''NOTE:''' The Github binaries archive contents are buried inside a second folder within the archive, you '''must''' extract the contents of this base folder in the archive for the update to work, you will know you're in the right place because there will be a folder called '''Engine'''. (see third image)[[File:Binaries Archive Contents.png|thumb|right|Correct files to extract from within the GitHib archive download.]]<br />
<br />
=== What files do I need for a mod? ===<br />
The minimal setup for a mod is:<br />
*'''PrimalGameData:''' - Create a child of PrimalGameDataBP<br />
*'''Level:''' - Create a new blank level file in your mod folder<br />
Open the level file(you will see a black screen, don't worry) and select the "World Settings" tab. If you don't have the tab up go to "Window" in the main menu bar and tick "World Settings".<br />
In the world settings look for the "PrimalGameData Override" and set it to the PrimalGameData in your mod folder.<br />
<br />
===How do I import the source files for a mod(tutorial, project take-over, etc.)?===<br />
To import the source files of a mod - remember that you '''cannot''' import the cooked/compiled files for a mod - either copy the '''root/base''' folder for the mod, or extract the '''root/base''' folder if the mod was sourced via an archive of some form(.7z, .zip, .rar, etc.), to the '''...\Mods\''' folder of your DevKit install with the DevKit '''closed'''. For example, I would extract the '''root''' folder of a mod' source files to '''"I:\ARKDevKit\Projects\ShooterGame\Content\Mods\..."'''.<br />
<br />
'''NOTE:''' Do '''NOT''' change any file or folder names as doing so will cause the files to lose their inheritance and reference paths when you load the DevKit next potentially making the mod unusable to you if you're unaware of what you're doing until you delete and re-do the copy/extraction process.<br />
<br />
==Blueprinting==<br />
<br />
=== How do I get a "Cast" node? ===<br />
You need to drag from a blue/purple pin and have the "Context sensitive" checkbox ticked to get the cast to options to show up.<br />
<br />
==Mapping==<br />
<br />
=== Why do I only see ocean when I load up TheIsland? ===<br />
By default the editor only loads the TheIsland persistent level to save resources. You need to load the sublevels you want to see/edit through the "Levels" tab.<br />
If you don't see the "Levels" tab go to "Window" in the main menu bar and tick "Levels". That should bring up the tab. You can then load the required sublevels by double-clicking on the name.<br />
<br />
==Troubleshooting==</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=FAQ&diff=837FAQ2017-01-05T03:12:43Z<p>Woeful Macabre: Embedded images due to image host.</p>
<hr />
<div>__FORCETOC__<br />
==General==<br />
<br />
===How do i get the ARK Devkit?===<br />
The only way for the initial download of the ARK Devkit is through the Epic Games Launcher. Do '''NOT''' download the version that is on Steam, it is severely outdated and unusable!<br />
After the initial download you can either keep it up to date through the Epic Games Launcher or manually through Github and content diff download.<br />
<br />
;Epic Games Launcher:<br />
:+ You are able to verify your devkit files in case you messed something up(much like verifying a games files on steam).<br />
:+ Easy to use<br />
:- Every update requires you to have as much free diskspace as a full install, this is only to start the download of the update regardless of the updates actual size. This can be impossible if you have limited diskspace available.<br />
:- Devkit Updates usually take longer until they are available on the Epic Games Launcher.<br />
<br />
;Manual Updates:<br />
:+ Gets around the free diskspace problem of the Epic Games Launcher.<br />
:+ Updates are available faster.<br />
:- No verification of the files.<br />
<br />
=== How do I update the Devkit without the Epic Games Launcher(Github and Content Diff)? ===<br />
Updates are usually provided first through github(binaries) and a Google-drive hosted content diff archive, and will be announced on the ARKModding discord by an Admin once the update has been vetted to be free of crash-inducing bugs. To update you need '''BOTH''' the binaries from github and the content diff package.<br />
<br />
To download the Github Binaries, you '''must''' be a member of Epic' organisation on Github. You do this by creating a Github account first, if you don't have one already, then you will need to proceed to [https://www.epicgames.com/account/settings?productName=epicgames your Epic Games account settings] and specify the username you used for your Github account in the '''Github Account Name''' field(see first image)[[File:Epic Account Settings.png|thumb|right|Put the GitHub account name in the highlighted field.]]<br />
<br />
You should then, either immediately or sometime after clicking "Save", receive an email with an offer to join Epic's Github organisation, which gives you access to the UE4 source repository and the DevKit binaries repository. To download the binaries, click on the green '''Clone or Download''' button and then '''Download ZIP'''.<br />
<br />
To download the Content-Diff, click the provided drive.google.com link and follow the prompts to download the archive. '''Warning:''' The size of this archive can range from ~1GB to ~5GB's or more.<br />
<br />
Once you have both the Google-Drive Content-diff ''and'' the Github binaries, extract them both over the root folder of your DevKit install (see second image). When you extract both archives, overwrite all files found in your install directory when prompted, then when both are complteted you may launch the DevKit with the .bat file called '''ARKDevKit.BAT''' and continue as normal.[[File:DevKit Root Install.png|thumb|right|View of DevKit install root, where archives get extracted.]]<br />
<br />
'''NOTE:''' The Github binaries archive contents are buried inside a second folder within the archive, you '''must''' extract the contents of this base folder in the archive for the update to work, you will know you're in the right place because there will be a folder called '''Engine'''. (see third image)[[File:Binaries Archive Contents.png|thumb|right|Correct files to extract from within the GitHib archive download.]]<br />
<br />
=== What files do i need for a mod? ===<br />
The minimal setup for a mod is:<br />
*'''PrimalGameData:''' - Create a child of PrimalGameDataBP<br />
*'''Level:''' - Create a new blank level file in your mod folder<br />
Open the level file(you will see a black screen, don't worry) and select the "World Settings" tab. If you don't have the tab up go to "Window" in the main menu bar and tick "World Settings".<br />
In the world settings look for the "PrimalGameData Override" and set it to the PrimalGameData in your mod folder.<br />
<br />
==Blueprinting==<br />
<br />
=== How do i get a "Cast" node? ===<br />
You need to drag from a blue/purple pin and have the "Context sensitive" checkbox ticked to get the cast to options to show up.<br />
<br />
==Mapping==<br />
<br />
=== Why do i only see ocean when i load up TheIsland? ===<br />
By default the editor only loads the TheIsland persistent level to save ressources. You need to load the sublevels you want to see/edit through the "Levels" tab.<br />
If you don't see the "Levels" tab go to "Window" in the main menu bar and tick "Levels". That should bring up the tab. You can then load the required sublevels by double-clicking on the name.<br />
<br />
==Troubleshooting==</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=File:Binaries_Archive_Contents.png&diff=836File:Binaries Archive Contents.png2017-01-05T03:10:09Z<p>Woeful Macabre: </p>
<hr />
<div>Shows the correct files to extract after having navigated to the folder within the root of the archive.</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=File:Epic_Account_Settings.png&diff=835File:Epic Account Settings.png2017-01-05T03:05:36Z<p>Woeful Macabre: </p>
<hr />
<div>Where to specify the GitHub username used when creating the account for linking.</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=File:DevKit_Root_Install.png&diff=834File:DevKit Root Install.png2017-01-05T02:45:09Z<p>Woeful Macabre: </p>
<hr />
<div>The root location of the DevKit install, where manual update archives are to be extracted.</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=FAQ&diff=824FAQ2016-12-26T17:24:46Z<p>Woeful Macabre: Habitually added my signature, removed it.</p>
<hr />
<div>__FORCETOC__<br />
==General==<br />
<br />
===How do i get the ARK Devkit?===<br />
The only way for the initial download of the ARK Devkit is through the Epic Games Launcher. Do '''NOT''' download the version that is on Steam, it is severely outdated and unusable!<br />
After the initial download you can either keep it up to date through the Epic Games Launcher or manually through Github and content diff download.<br />
<br />
;Epic Games Launcher:<br />
:+ You are able to verify your devkit files in case you messed something up(much like verifying a games files on steam).<br />
:+ Easy to use<br />
:- Every update requires you to have as much free diskspace as a full install, this is only to start the download of the update regardless of the updates actual size. This can be impossible if you have limited diskspace available.<br />
:- Devkit Updates usually take longer until they are available on the Epic Games Launcher.<br />
<br />
;Manual Updates:<br />
:+ Gets around the free diskspace problem of the Epic Games Launcher.<br />
:+ Updates are available faster.<br />
:- No verification of the files.<br />
<br />
=== How do I update the Devkit without the Epic Games Launcher(Github and Content Diff)? ===<br />
Updates are usually provided first through github(binaries) and a Google-drive hosted content diff archive, and will be announced on the ARKModding discord by an Admin once the update has been vetted to be free of crash-inducing bugs. To update you need '''BOTH''' the binaries from github and the content diff package.<br />
<br />
To download the Github Binaries, you '''must''' be a member of Epic' organisation on Github. You do this by creating a Github account first, if you don't have one already, then you will need to proceed to [https://www.epicgames.com/account/settings?productName=epicgames your Epic Games account settings] and specify the username you used for your Github account in the '''Github Account Name''' field like so: http://i.imgur.com/yNIGTh7.png <br />
<br />
You should then, either immediately or sometime after clicking "Save", receive an email with an offer to join Epic's Github organisation, which gives you access to the UE4 source repository and the DevKit binaries repository. To download the binaries, click on the green '''Clone or Download''' button and then '''Download ZIP'''.<br />
<br />
To download the Content-Diff, click the provided drive.google.com link and follow the prompts to download the archive. '''Warning:''' The size of this archive can range from ~1GB to ~5GB's or more.<br />
<br />
Once you have both the Google-Drive Content-diff ''and'' the Github binaries, extract them both over the root folder of your DevKit install (see: https://i.gyazo.com/90bbb1d07a8c6067b7cad883fdaf48ed.png). When you extract both archives, overwrite all files found in your install directory when prompted, then when both are complteted you may launch the DevKit with the .bat file called '''ARKDevKit.BAT''' and continue as normal.<br />
<br />
'''NOTE:''' The Github binaries archive contents are buried inside a second folder within the archive, you '''must''' extract the contents of this base folder in the archive for the update to work, you will know you're in the right place because there will be a folder called '''Engine'''. See: https://i.gyazo.com/134b9fc07217815089e8960898abb10b.png<br />
<br />
=== What files do i need for a mod? ===<br />
The minimal setup for a mod is:<br />
*'''PrimalGameData:''' - Create a child of PrimalGameDataBP<br />
*'''Level:''' - Create a new blank level file in your mod folder<br />
Open the level file(you will see a black screen, don't worry) and select the "World Settings" tab. If you don't have the tab up go to "Window" in the main menu bar and tick "World Settings".<br />
In the world settings look for the "PrimalGameData Override" and set it to the PrimalGameData in your mod folder.<br />
<br />
==Blueprinting==<br />
<br />
=== How do i get a "Cast" node? ===<br />
You need to drag from a blue/purple pin and have the "Context sensitive" checkbox ticked to get the cast to options to show up.<br />
<br />
==Mapping==<br />
<br />
=== Why do i only see ocean when i load up TheIsland? ===<br />
By default the editor only loads the TheIsland persistent level to save ressources. You need to load the sublevels you want to see/edit through the "Levels" tab.<br />
If you don't see the "Levels" tab go to "Window" in the main menu bar and tick "Levels". That should bring up the tab. You can then load the required sublevels by double-clicking on the name.<br />
<br />
==Troubleshooting==</div>Woeful Macabrehttps://wiki.arkmodding.net/index.php?title=FAQ&diff=823FAQ2016-12-26T17:23:14Z<p>Woeful Macabre: Provided instructions for downloading Git archive and ensuring correct paths are used.</p>
<hr />
<div>__FORCETOC__<br />
==General==<br />
<br />
===How do i get the ARK Devkit?===<br />
The only way for the initial download of the ARK Devkit is through the Epic Games Launcher. Do '''NOT''' download the version that is on Steam, it is severely outdated and unusable!<br />
After the initial download you can either keep it up to date through the Epic Games Launcher or manually through Github and content diff download.<br />
<br />
;Epic Games Launcher:<br />
:+ You are able to verify your devkit files in case you messed something up(much like verifying a games files on steam).<br />
:+ Easy to use<br />
:- Every update requires you to have as much free diskspace as a full install, this is only to start the download of the update regardless of the updates actual size. This can be impossible if you have limited diskspace available.<br />
:- Devkit Updates usually take longer until they are available on the Epic Games Launcher.<br />
<br />
;Manual Updates:<br />
:+ Gets around the free diskspace problem of the Epic Games Launcher.<br />
:+ Updates are available faster.<br />
:- No verification of the files.<br />
<br />
=== How do I update the Devkit without the Epic Games Launcher(Github and Content Diff)? ===<br />
Updates are usually provided first through github(binaries) and a Google-drive hosted content diff archive, and will be announced on the ARKModding discord by an Admin once the update has been vetted to be free of crash-inducing bugs. To update you need '''BOTH''' the binaries from github and the content diff package.<br />
<br />
To download the Github Binaries, you '''must''' be a member of Epic' organisation on Github. You do this by creating a Github account first, if you don't have one already, then you will need to proceed to [https://www.epicgames.com/account/settings?productName=epicgames your Epic Games account settings] and specify the username you used for your Github account in the '''Github Account Name''' field like so: http://i.imgur.com/yNIGTh7.png <br />
<br />
You should then, either immediately or sometime after clicking "Save", receive an email with an offer to join Epic's Github organisation, which gives you access to the UE4 source repository and the DevKit binaries repository. To download the binaries, click on the green '''Clone or Download''' button and then '''Download ZIP'''.<br />
<br />
To download the Content-Diff, click the provided drive.google.com link and follow the prompts to download the archive. '''Warning:''' The size of this archive can range from ~1GB to ~5GB's or more.<br />
<br />
Once you have both the Google-Drive Content-diff ''and'' the Github binaries, extract them both over the root folder of your DevKit install (see: https://i.gyazo.com/90bbb1d07a8c6067b7cad883fdaf48ed.png). When you extract both archives, overwrite all files found in your install directory when prompted, then when both are complteted you may launch the DevKit with the .bat file called '''ARKDevKit.BAT''' and continue as normal.<br />
<br />
'''NOTE:''' The Github binaries archive contents are buried inside a second folder within the archive, you '''must''' extract the contents of this base folder in the archive for the update to work, you will know you're in the right place because there will be a folder called '''Engine'''. See: https://i.gyazo.com/134b9fc07217815089e8960898abb10b.png<br />
<br />
[[User:Woeful Macabre|Woeful Macabre]] ([[User talk:Woeful Macabre|talk]]) 17:23, 26 December 2016 (UTC)<br />
<br />
=== What files do i need for a mod? ===<br />
The minimal setup for a mod is:<br />
*'''PrimalGameData:''' - Create a child of PrimalGameDataBP<br />
*'''Level:''' - Create a new blank level file in your mod folder<br />
Open the level file(you will see a black screen, don't worry) and select the "World Settings" tab. If you don't have the tab up go to "Window" in the main menu bar and tick "World Settings".<br />
In the world settings look for the "PrimalGameData Override" and set it to the PrimalGameData in your mod folder.<br />
<br />
==Blueprinting==<br />
<br />
=== How do i get a "Cast" node? ===<br />
You need to drag from a blue/purple pin and have the "Context sensitive" checkbox ticked to get the cast to options to show up.<br />
<br />
==Mapping==<br />
<br />
=== Why do i only see ocean when i load up TheIsland? ===<br />
By default the editor only loads the TheIsland persistent level to save ressources. You need to load the sublevels you want to see/edit through the "Levels" tab.<br />
If you don't see the "Levels" tab go to "Window" in the main menu bar and tick "Levels". That should bring up the tab. You can then load the required sublevels by double-clicking on the name.<br />
<br />
==Troubleshooting==</div>Woeful Macabre