This guide is designed for players and server hosts of ARK: Survival Ascended who want to set up a dedicated server on Windows PCs, with or without custom mods.

It’s perfect for:

• Solo hosts managing small private servers.
  
• Players setting up servers for friends or LAN parties.
  
• Those struggling to install mods or troubleshoot server issues with the latest game updates.
  
• HEY ITS YOUR GIRL BACK WITH ANOTHER LIKE AND SUBSCRIBE TO TURNING ON NOTIFICATIONS TO JOIN MY MAILING LIST People who hate video tutorials.
  
• People who prefer detailed, written guides.
  
• People who like using the search function and text-based instructionals.

When I attempted to set up my server, I found that the information for ARK: Survival Ascended (ASA) was vague, non-existent, or relied on outdated instructions for ARK: Survival Evolved (ASE). These instructions weren’t compatible with ASA’s Unreal Engine 5 structure, which caused confusion and errors.

On top of that, I had to cobble together bits and pieces of information from multiple sources scattered across the internet. Much of it wasn’t obvious, and finding the right answers took far longer than it should have.

I also found a lot of lengthy videos with no transcripts that I had to scrub through just to find relevant points. Other guides had blurry screenshots that made copying and pasting text almost impossible.

So I created this guide to make things easier, with text and visuals that show you exactly what to do. I hope this will provide you with clear, step-by-step instructions to get your server running!

First things first. Here are the basic things you'll need. If you don't know what I'm talking about in this section, like, I dunno, maybe don't try doing this till you brush up on basic PC knowledge before diving in—it’ll make the process much easier!

Surprisingly, not any outrageous requirements. Many people have run a server on spare/obsolete PCs. Keep in mind that the server doesn't use the GPU so feel free to dust off that old tower you have sitting in the closet as long as it meets these bare bones specs:

• Storage Space:
  As of 10 December 2024, One server installation is approximately 10 GB. Try to have about 200 GB worth of storage available to account for mod installations, multiple maps, and future updates. Use an SSD for faster speeds.
  
• CPU:
  Have 4 logical cores available on your processor for each server instance you plan to run. Some people have had success running with 2 cores per map, which might work for smaller setups.
  
• GPU:
  The server does not rely on the GPU, so you can use an older or integrated graphics card. All the heavy lifting is done by the CPU and RAM.
  
• RAM:
  Each map uses approximately 10 GB of RAM. 32 GB seems to be the preferred number but you can get away with 16 GB if you only need to run one server.
  
• Network Requirements:
  Make sure your internet connection is stable and fast enough for hosting. You’ll also need to set up port forwarding for others to connect to your server.
  
• Operating System Requirements:
  This guide is designed for Windows 64 bit machines.

These are the tools you’ll need to successfully set up and run your ARK: Survival Ascended server:

SteamCMD:
• The Steam Console Client (SteamCMD) is a command-line version of the Steam Client. It is used to install and update dedicated servers available on Steam. This tool is required for setting up your ARK server.
  
  • Download SteamCMD: https://developer.valvesoftware.com/wiki/SteamCMD

These tools can make your life easier, but they’re not strictly required to run the server:

Notepad++:
• Download Notepad++ if you haven't already. Notepad++ makes editing .ini and .bat files way easier with features like syntax highlighting and line numbering, which can save you a lot of headaches. You can stick with regular Notepad or Wordpad if you'd like that level of suffering.
  
  Notepad++ can be obtained here:
  
  • Website with installer packs: https://notepad-plus-plus.org/
    
  • GitHub for the nerds (you know who you are): https://github.com/notepad-plus-plus/notepad-plus-plus

I know many people have multiple hard drives, but for simplicity, let's use the C:\ drive in this guide. Feel free to tailor any drive or directory names to your own preferences where specifically noted.

Let's get started.

So, you’ve already downloaded SteamCMD, right? If not, go to the developer's page at: https://developer.valvesoftware.com/wiki/SteamCMD and grab it. I’ll wait...

1. Create a Home for SteamCMD:
First, let’s give SteamCMD a cozy little folder to live in.

• Go to the drive where you want to install it (e.g., C: or D:).
  
  • Create a folder named steamcmd. Example:
    
    C:\steamcmd D:\steamcmd

2. Unpack SteamCMD:
Take the steamcmd.zip file you downloaded earlier and extract it into the steamcmd folder you just created.
Use your favorite tool for this—WinRAR, 7-Zip, or just the built-in extractor if you’re feeling basic.

3. Fire Up SteamCMD:

• Navigate to the steamcmd folder.
  
• Double-click on steamcmd.exe.

SteamCMD will update itself and set up everything it needs.

4. Set a Destination for Your ARK Server:
In the SteamCMD prompt, tell it where to install the ARK server files. Use the following command and replace <install_dir> with the folder path of your choice:
Example:

5. Log in:
No Steam account needed here, this is just basic protocol for their server. Just type:

6. Download the ARK: Survival Ascended Server:
Use the App ID 2430930 for ARK: Survival Ascended and run this command:
This ensures all the files download correctly and are ready to go.
Once everything is downloaded, type:
SteamCMD will close, and you’re ready to move on to the next steps!

1. Set Up a Folder for the Server Files
Create a folder where your server files will live. Name it whatever you want. For this guide we're going to call it ArkAscendedServer

2. Download the Server Files
Go to the folder where you installed steam CMD and run the steamcmd.exe file. It'll open a window like this:

Run the following commands using App ID 2430930 for ARK: Survival Ascended.

• Just replace C:\ArkAscendedServer with the full path to the folder you created in Step 2 if you customized it. It'll look something like this:
  
  
  It's going to go through the whole validation process that will look like this:
  
  
  Watch the progress number increase to 100, this might take some time but when it finishes it will look like this and you can exit out of the command line.
  

📌Protip:
Create a Batch File! You can run these lines as a single command from your system’s command line. This is a great way to help automate anytime you need to update the server because of patches or whatever. Just open Notebook++ and type in the following line (assuming you used the same installation folder for steamcmd.exe, if not change that to what you made it:
Save it as a .bat file with an easy name like Server_Update.bat or similar and put it somewhere you'll remember to click on it. It should look something like this:
Note: I did not add the +quit command just because I like to close the window myself, that part is up to your own preference.

3. Create a Launch Script
Now you’ll need a script to start your server with your chosen settings.
Open Notepad++ and create a new file with this line of script feel free to customize it for your server:
I'll break this example down for you.

Start the server itself with the path to the executable file
• start c:\ArkAscendedServer\ShooterGame\Binaries\Win64\ArkAscendedServer.exe

Use ScorchedEarth as the map. It looks like the four maps available currently are:
• TheIsland_WP
  
• TheCenter_WP
  
• ScorchedEarth_WP
  
• Aberration_WP
  They appear to follow the same naming convention so I expect all of the other maps will follow suit.

The session name LadyVyrusSuperServer can be replaced by whatever you want to name your server publicly.

The default port addresses used by the server are
• Port 7777

The maximum number of players is set to 5. I think it defaults to 70. Set it to however many people you expect to be playing.

Save this script with the name start_server.bat in the same folder where your server files were downloaded. For example we are using:
It will look something like this:

📌ProTip:
I saw a lot of guides and threads that sugget you format the command line with something like this:
Best practices dictate avoiding the inclusion of passwords in your launch script for security reasons. I believe this was a change to the Unreal 5 engine from the way ASE was handled. We'll configure these securely in the next section. Let's avoid saving our passwords in plain text format on launch commands so we don't accidentally let the whole world know how to run havoc on our servers.

📌Protip:
For more advanced server settings and a list of command line options, check out the Server Configuration section of the Ark Wiki at:
https://ark.wiki.gg/wiki/Server_configuration#Command_line_options
We're just doing the basics here folks.

Let's move on to configuring the server.

Okay, now that your server is installed, let’s make sure it’s actually visible to the outside world. This is a key step—without it, no one (not even you) will be able to connect to your server. If you skip this or mess it up, your server won’t show up on the server list. Let’s not let that happen!

Port forwarding ensures that incoming connections from the internet can reach your server. This involves configuring your router to allow traffic through specific ports.

ASA uses the following ports for server functionality:

🤔Note: If you're a previous ASE server admin and are wondering about Query Port (27015) or the peer ports which were the game port +1 DONT! Unlike ASE, ASA does not use that or a Steam Query Port because the server does not use the Steam network. Peer Ports were historically used for in-game Steam browser advertising in ASE, but this functionality does not apply to ASA. Direct discovery relies on game servers being visible via their game ports. Yay! Less to configure! 🎉

📌Protip: If you’re running multiple servers or maps, you’ll need to assign different ports to each one. The syntax follows a sequential order of Game Port and RCON. For example:

You can specify a range of external ports to cover all your server instances at once. For example if we use those three servers it will look like this:


This ensures traffic for multiple maps or server instances is routed correctly. Just make sure each server instance uses its own unique ports to avoid conflicts.

How to Set Up Port Forwarding:
1. Access your router settings by opening a web browser and enter your router’s IP address (commonly 192.168.1.1 or 192.168.0.1).
2. Log in with your admin credentials. (Usually found on a sticker on the physical router.)
3. Find the Port Forwarding Section: Look for settings like "Port Forwarding," "NAT," or "Virtual Server."
4. Create Port Forwarding Rules:
5. Save your changes and restart your router if needed.

If you need more detailed steps for your specific router, refer to its user manual or Port Forward’s router database at Setup Router[setuprouter.com]

By default, Windows Firewall may block connections to your server. You’ll need to allow traffic through the same ports you just forwarded.

Setting Up Firewall Rules:
1. Click Start, search for wf.msc, and press Enter.


2. Select "Inbound Rules" in the left panel.


3. Click "New Rule" in the right panel.


4. Choose "Port" and click Next.


5. Select UDP and specify the ports (e.g., 7777-7779). Click Next.


6. Choose "Allow the Connection" and continue.


7. Press Next.


8. Name your rule and add a description (e.g., "ARK Server Ports (UDP)"). Adding the protocol name, UDP, to the rule is a best practice for finding the rule easier in the future. Press finish.


Repeat the steps above, but choose TCP and specify the RCON port (e.g., 27020).
You should now see your rules listed under "Inbound Rules." No need to configure "Outbound Rules" unless you’ve altered your Windows Firewall’s default settings.

📌Protip: RCON: To Use or Not to Use?
RCON (Remote Console) is a protocol that allows server administrators to manage their ARK server remotely out-of-game. With RCON, you can:

• Execute server commands (e.g., spawn items, adjust settings).
  
• View logs and player activity.
  
• Manage server settings without direct access to the server machine.

When is RCON Useful?
RCON shines in scenarios where:

• You don’t have physical or remote desktop access to the server machine.
  
• You’re managing the server from a completely different location.
  
• You’re hosting a public server with multiple admins who need remote management access.
  
• Automation or real-time monitoring tools are needed.

When is RCON Unnecessary?
RCON might be overkill (or even a security risk) if:

• You’re running the server and client on the same PC. You already have direct access to the server console.
  
• You’re hosting for friends on the same local network. Local access allows you to manage the server directly without RCON.
  
• You’re concerned about security risks. If not properly configured, RCON can expose your server to unauthorized access, especially if ports are left open or passwords are weak.

Security Concerns with RCON
If enabled, RCON opens an additional network port (default: 27020). This can be exploited if:

• The port is improperly secured or left open to the internet.
  
• The RCON password is weak or shared with others.
  
• Unauthorized users gain access, allowing them to execute commands on your server.

My recommendation?
For most local setups or small private servers whom this guide is geared towards:
Just skip enabling RCON. It adds unnecessary complexity and potential security risks.
Instead, manage server settings and commands directly from the machine hosting the server.
If you are looking for a way to enable cheats, admin or creative mode, RCON is unnecessary because those admin commands like enablecheats [adminpassword] are handled directly by the game client once connected to the server. These commands do not rely on the RCON protocol. They are sent from the client to the server via the game port (e.g., 7777) that is already open for player connections.

If you still decide to use RCON, ensure you:

• Use a strong, unique password.
  
• Limit RCON access to specific IPs (if supported by your router or firewall).
  
• Monitor logs for unauthorized access attempts.

To test if your ports are open:
Start your server and see if it appears in the ARK server list or can be connected to directly using its IP.
Use an online tool like CanYouSeeMe.org to check if your forwarded ports are accessible.
- Start your server.
- Visit CanYouSeeMe.org (or a similar port-checking tool of your choice).
- Enter your Game Port (e.g., 7777) and click "Check." If it says "Success," your setup is correct.

Now that your server is up and running, it’s time to tweak the settings to suit your play style. Below, I’ll list some of the most commonly configured options in the GameUserSettings.ini and Game.ini files. These examples illustrate how some of the parameters are set. For instance, taming speed multipliers are typically whole numbers greater than 1, while day cycle speeds use decimals. Pay close attention to these distinctions since each multiplier is configured differently for some reason (thanks, ARK logic!).

Also, keep gameplay mechanics in mind. Sure, it’s great to breeze through the dark by setting the night cycle to 10 (making it pass 10 times faster), but some creatures are only active or gain unique abilities at night (Troodons and Megalosaurus). You might unintentionally limit certain gameplay features if you're not careful. Be sure to consider how your settings might impact your gameplay experience before diving in.

All server settings are stored in:

Here are some of the most popular settings to configure in the [ServerSettings] section of GameUserSettings.ini:

For more detailed customization, edit the Game.ini file. Here’s how to set up advanced options:

Player and Dino Stats Multipliers: Adjust stats like health, stamina, oxygen, and weight for players and dinos.

How to Apply Your Changes
• Save your changes to both files.
  
• Restart your server to apply the new settings.

📌ProTip:
Back up your GameUserSettings.ini and Game.ini files before you go messing with them so that you have a clean version saved somewhere incase you REALLY mess things up. For example, if you set the 💩 interval too short... it's gonna get real ridiculous real fast.

If somehow you absolutely need more settings and customization, you're gonna have to check out other sources of information. The Ark Wiki[http//url%3Dhttps] has a huge list of settings for the ini files as well a some more command line parameters. I don't know if the information is up to date or not on those sites, so good luck to you. I'm just here to help you get the server running, tweaking isn't quite my thing.

There are two options for adding mods to the server. You can use the newer server-driven mod download functionality or manually place the mods.

Set Up Your Batch File
Locate your start_server.bat file. Using our guide directory structure it will be here:

Update the batch file to include the -mods parameter with your desired mod IDs in quotes with a comma between each mod:

935528 and 990263 are some random Mod IDs I picked. Replace those if you want or add whatever Mod IDs you want to install. The order doesn't really matter. That's it.

🤔Confused? There is no need to edit the GameUserSettings.ini anymore with regards to mods.The -mods argument should be used in the server launch batch file, not the ActiveMods line in the GameUserSettings.ini file. The ?GameModIds inline argument in the command-line launch string is explicitly marked as obsolete for ASA.

Once you've ensured your start_server.bat includes the -mods="MODID1,MODID2" parameters. Start your server using the batch file.

The server will automatically:
• Download the mods directly from CurseForge.
  
• Extract them.
  
• Place them in the correct directory:
  
  C:\ArkAscendedServer\ShooterGame\Binaries\Win64\ShooterGame\Mods\MODID\

Check the directory to make sure they are there. The structure will look something like this:


Alternatively, you can verify the logs to confirm successful mod downloads:

This is highly unnecessary extra work and only advisable if you are a more advanced user doing things such as testing mods or where you would want to roll-back versions. If you don't know what I mean, then don't do it this way.

Step 1. Download the mod files from CurseForge or another trusted source. Each mod typically includes .pak, .utoc, and .ucas files.
Step 2. Place the files into a properly nested folder structure:
Example:
For Mod ID 935528, the folder should be:
Step 3: Start the Server
Launch the server using the updated start_server.bat.
Verify that the mods are loaded by checking the logs for entries like:

---

Seasonal events like Fear Evolved, Turkey Trial, and Winter Wonderland bring exclusive in-game activities, items, and creatures, such as the elusive DodoRex and giant super turkeys. Installing event mods uses the same process as regular mods!

Here's how to add event mods:
• Find the Mod ID for the event on the ARK Wiki or CurseForge.
  
• Add it to your server's batch file under the -mods parameter. For example, to activate Fear Ascended, https://www.curseforge.com/ark-survival-ascended/mods/fear-ascended, add 877752.
  
  start C:\ArkAscendedServer\ShooterGame\Binaries\Win64\ArkAscendedServer.exe ScorchedEarth_WP?listen?SessionName=LadyVyrusSuperServer?Port=7777?MaxPlayers=5 -mods="935528,990263,877752"
• Restart your server.

📌Protip: If you’re running multiple event mods simultaneously, separate Mod IDs with commas, just like with regular mods.

Missing Mods in Logs:
• Ensure your -mods syntax includes quotes around the Mod IDs.
  
• Verify that the Mod IDs match the ones listed on CurseForge.

Manually Placed Mods Not Loading:
• Confirm the file structure:
  
  C:\ArkAscendedServer\ShooterGame\Binaries\Win64\ShooterGame\Mods\MODID\
• Check for correct file extensions (.pak, .utoc, .ucas).
  
• Force Re-Download Mods:
  
• Run the following admin command in-game:
  Press the ~ (tilde) key to bring up the admin console and type in:
  
  cheat RedownloadModsOnServerRestart
  Restart the server to trigger a fresh download.

This section consolidates key information from the guide and adds helpful links for advanced server setup and troubleshooting.

1. Batch File Script for Updates
Save this script as a .bat file to automate updates for your server:
Running this file ensures your server stays updated with the latest patches.

2. Launch Script Template
Use this example to create your start_server.bat file:
Replace ScorchedEarth_WP with your chosen map.
Customize the session name and player settings to your liking.

3. Advanced Server Settings
Explore more command-line options and server configurations: Ark Wiki Server Configuration Guide[ark.wiki.gg]

4. Port Forwarding
Ensure your ports are open for others to connect to your server. Typical ports include:
Game Port: 7777

You may need to refer to your router's user manual or manufacturer’s website for specific setup instructions.

For more general information on port forwarding check out: https://lazyadmin.nl/home-network/port-forwarding/ or https://learn.g2.com/port-forwarding

5. Free up Drive Space:
Recover approximately 13Gig of drive space by removing removing pre-rendered cutscenes from:

6. Backup your files:
Reload or save your backups of the game files stored at:

7. Disable BattleEye:
Why would you or your friends need to cheat when you have access to the actual in game cheats? BattleEye is an anti-cheat system designed to detect and prevent cheating in online games and can consume system resources because actively monitors for suspicious activity. Disabling it can free up a bit of performance, which might be valuable if you're running both the server and client on the same machine or if your hardware is uh....modest. Just add -NoBattleye to your start_server.bat file. Remember, you can always kick, or ban players using the in-game admin console commands.



Encountering issues? Here are quick tips:

1. Mods Not Loading:
Verify file structure and use the -mods parameter in your batch file.

2. Server Failing to Start:
Check for typos in your start_server.bat script or review logs for specific errors.

3. Validation Loop:
Rerun the app_update command with validate.

4. Mods won't load:

• Make sure you have the proper MoID numbers typed in. They can be found on their respective mod pages at CurseForge at: https://www.curseforge.com/ark-survival-ascended/ on the right hand side of the page under "Project ID"
  
  
  
• Check the syntax! Be sure to use quotations " around the ModId numbers. Separate the numbers with a comma , and do not use any spaces. Make sure you are using the updated Mod syntax.
  
  Here is a comparison of the ASE and ASA differences:
  
  • ASE:
    
    ShooterGameServer.exe TheIsland?listen?SessionName=MyServer?ModIds=123456,654321?Port=7777?QueryPort=27015?MaxPlayers=10
  • ASA:
    
    ShooterGameServer.exe ScorchedEarth_WP?listen?SessionName=MyServer?Port=7777?QueryPort=27015?MaxPlayers=10 -game -server -log -mods="123456,654321"

Key Differences:

Placement:
• The ?ModIds= syntax was embedded inline with other settings, such as SessionName and Port, in the command line.
  
• The -mods= syntax is now appended as a separate parameter at the end of the command line.

Punctuation:
• ?ModIds= used a question mark ? to define settings inline.
  
• -mods= uses a hyphen - to specify mods as a distinct command.

Quotations:
• -mods= requires the mod IDs to be enclosed in quotes (e.g., "123456,654321").
  
• ?ModIds= did not require quotes.

Flexibility:
• The -mods= syntax is better suited for Unreal Engine 5, as it's easier to modify and separates mods from the map and server-specific settings.

5. Server won't download/update:
Make sure you are using App ID 2430930

Setting up your own Ascended server might feel overwhelming at first, but it’s totally doable. Whether you’re hosting for friends, running a private server, or experimenting with mods and settings, I hope this guide has saved you the time and frustration I went through when piecing all this together.

Remember, the real joy of ARK isn’t just in the setup—it’s in the moments you’ll create with your friends, exploring the map, taming dinos, and conquering challenges together. Dying. Constant. Unending. Corpse runs. Bodies strewn all over the world. Probably under the mesh. So. Much. Dying.

If you ever run into issues, don’t hesitate to revisit this guide or check out the resources linked throughout. And if you’ve found this helpful, consider sharing it with others who might benefit.

Good luck, survivors!

-LadyVyrus