How To Install Mods In Ark Survival Evolved Cracked

0 views

Skip to first unread message

Idara Viengxay

unread,

Aug 3, 2024, 4:29:29 PM8/3/24

to tighcharlila

The mods are not actually installed correctly yet, Steam has only downloaded the files it needs to start installing them. To perform the actual installation, you will need to start Ark next on your PC.

It's highly recommended that you "zip" all the files up before uploading them to your server. Files contained in a single zip file are also easier to move around on your server if you need to transfer them from one directory to another.

Once you've gone to the LinuxServer folder, select the file GameUserSettings.ini by clicking the blue box to the left of the file name in the Nodecraft file manager view. Then click the "Edit" button at the top of the file manager window.

We founded Nodecraft with a mission to make multiplayer gaming easier for player-owned game servers. We promise to serve gamers with the best quality service, real customer support, & innovation above all else.

Hi all. I've been reading through several tutorials and guides on how to install mods on a Linux server, but I'm still having issues. I'm running Ubuntu 18.04 Server and the server runs fine with no mods. From what I can gather, the mod installation procedure is basically copy over the "*.mod" file and "mod" directory into "/arkserver/ShooterGame/Content/Mods/" and then add "ActiveMods=xxxxxxxxxx" under "[Server Settings]" in the GameUserSettings.ini file.

I've done all this and restarted the ark service (with systemctl restart ark) but the client no longer sees the server despite it showing as "active (running)" when I use "systemctl status ark". Under Steam's server list, it just says "not responding". I tried waiting a while to see if it just takes a crazy amount of time to load with mods, but after about an hour it still isn't showing up in Steam's server list or in the Ark client's server list.

I changed all of the permissions of the mod file and directory (recursively) to the same owner/group that every thing else is. To my knowledge there are no errors that I can see to indicate what might be wrong.

I also read a couple of forums with other people asking how to install mods, and a few people were mentioning editing other files (such as Game.ini) and also editing the server execution command with something, but I think those are referring to servers that were installed differently than how I installed mine. I did go into "Game.ini" as well and added the "[ModInstaller]
ModIDS=xxxxxxxxxxx" lines, but this causes segmentation faults and other errors upon starting the ark service.

From what I understand, it's supposed to be as simple as copying the mods to the right directory, and adding the "ActiveMods=xxxxxxxx" line to the settings file, and it should work. But it's not. Can anyone point me to a complete guide on how to install mods or know what I'm doing wrong here? Thanks.

Getting a segmentation fault when starting the server could mean that a particular mod isn't installed correctly, or it is incompatible with another mod.

I would be tempted to delete all the mod files you've copied by hand, and let Ark auto-download and install them for you.

I forgot to mention that for now I'm only attempting to load one mod just so I can figure out how to get it working before I start adding more. But in regards to your step 3 above, where exactly am I supposed to add that argument? The way I have my server set up is I have a script in /lib/systemd/system/ark.service that has the preexec and exec commands there which are:

Basically it seems like as soon as I add "-automanagedmods" or edit the Game.ini file, it begins to give segmentation faults. Otherwise if I leave the automanagedmod argument out and delete the contents of Game.ini the game runs fine.

Did you run a status check to confirm that the server was fully shut down before you ran the new start command? I've had a few occasions where the shutdown command completed and it returned me to the command prompt, but something still wasn't finished, I had to wait until the status check gave me a good result before I could start the server again.

Yes, I made sure to check that the service was stopped. I even went so far as to disable the service, edit the systemd file, and then re-enabled the service along with daemon-reload. For some reason it's just not happy when I attempt to start referencing mods.

Yes, I made sure to go in an delete the mod that I had previously moved over manually. I'm attempting to load Structures+ which seems to be a well supported mod, so hopefully it doesn't mean that my server is incompatible with that specific mod. I'll try a different mod though and see what it does.

ExecStart=/path/ShooterGameServer TheCenter?listen?SessionName=MyCenter?ServerPassword=MyPassword?AltSaveDirectoryName=Center?MultiHome=192.168.1.15?Port=7781?QueryPort=27018?GameModIds=11111111,22222222,33333333 -automanagedmods -NoTransferFromFiltering -server -log clusterid=MyCluster

From what I can gather, the mod installation procedure is basically copy over the "*.mod" file and "mod" directory into "/arkserver/ShooterGame/Content/Mods/" and then add "ActiveMods=xxxxxxxxxx" under "[Server Settings]" in the GameUserSettings.ini file.

The reason I'm asking is that Steam doesn't fully install the mods, it downloads the install kit (or update kit) and then the kit just sits there until you actually run the game client and the game client finishes the installation. This can be seen if you subscribe to a new mod, then open your game client and go to the host/local page, the new mod won't show up on the page at first but in the lower right corner you'll see the message(s) showing the mod(s) being installed. It's only after this installation is complete that you can copy them over to the server.

I followed the advice of Larkfields (list the mods in Game.ini, list in GameUserSettings.ini and add -automanagedmods to ark.service). In addition, I added WorkingDirectory=/home/ark/server/ShooterGame/Binaries/Linux to ark.service since the dedicated server setup page states that this is necessary to download mods.

SteamCMD can download the workshop mods but they are 100% unusable by themselves since they are just archives that need a very specific method to decompress them and to create an associated .mod file.

The downloader script was modified from the original format which was mainly for Windows platform but now works on Linux. However, it was supposed to handle downloading all the mods at once but that did not work and I never fixed it. Just call the script for each individual mod you want downloaded and extracted.

Note: Before doing any of the below instructions, your ARK:SE server must be started at least once. So, after creating the ARK:SE instance in AMP, manage the instance and click Update to install the ARK:SE server. Then click Start, wait until the server is running, and then stop it.

Currently some manual intervention is required to install mods on ARK:SE servers on Linux. There are two options: manually upload mods to the server, or manually adjust the server files so that mods are able to be automatically downloaded by the server.

While it is possible to download Steam workshop items, including mods, on Linux servers via AMP (via Configuration->Steam Workshop), steamcmd does not install them in the correct directory, and therefore they need to be manually moved. In addition, in the case of ARK:SE servers, the required .mod file is not created at all when this method is used.

ARK:SE comes with a launch parameter option that is meant to automate the process of downloading, installing and updating mods. Unfortunately it does not work on Linux systems without manual intervention.

This tutorial should show you how to quickly install your ARK: Survival Evolved mods to your server. First you will need to have all of your mods installed to your Steam client. If you don't know how, read this tutorial.

When you update your mods, you will need to remove all of the ones that you have uploaded and replace them with the newer version. However, make sure not to remove the added DLC content that comes with the game in the three pictured folders: 111111111, Ragnarok, and TheCenter. If you remove these, they will need to be reuploaded or reinstalled which can take some time.

Summary
Players can install Ark mods that provide exciting content that can bring a fresh perspective to the game. Various mods, such as new maps, creatures, weapons, and game mechanics, can add more depth and complexity to the game. Mod settings can also be customized, similar to changing Ark's base server settings. Installing Ark mods can breathe new life into the game and provide endless possibilities for players to explore.

Setting up mods for your Ark: Survival Evolved server can be a simple and rewarding process. With a basic knowledge of FTP (File Transfer Protocol), you can easily enhance the gameplay experience. This guide will show you the necessary steps to install mods on your server using FTP, this guide is useful if you plan to host a server on your desktop, or have a dedicated server rented with a server company. If you already rent an ARK game server from a company this guide will not apply.

Remember, it's important to update your mods regularly to ensure their functionality and compatibility with the game. To update mods, you will need to repeat this process. It's also crucial to have backups of your server before making any changes or installing mods to prevent potential data loss. Happy gaming!