ASKA Dedicated Server Setup Guide: 2026

An ASKA dedicated server keeps your Viking world available without requiring one player to host every session. However, an incorrect App ID, invalid GSLT, or blocked port can prevent the server from appearing online.

To set it up, install the dedicated server tool with App ID 3246670, launch it with SteamAppId=1898300, and add a valid GSLT. Configure server properties.txt, allow the selected UDP ports, and start the server through a batch file. The world pauses when empty unless Keep Server World Alive is enabled.

This guide covers installation, configuration, custom worlds, networking, saves, backups, Linux and Docker options, and common troubleshooting steps for reliable ASKA hosting in 2026.

ASKA Dedicated Server Quick Facts

Latest Updates

The ASKA Dedicated Server Steam Tool remains active in 2026 under App ID 3246670. SteamDB lists it as a Windows-supported tool with AskaServer.exe as the server executable. The latest major ASKA update was the Great Hall & Feasts Update, released on August 31, 2026. It was followed by fixes on September 1, September 2, and September 8, including dedicated-server fixes for custom-world creation and first-join customization loading. Update both the game client and server before troubleshooting version or preset problems.

ASKA Dedicated Server App ID and Steam Distribution

ASKA Steam App IDs

ASKA uses separate Steam App IDs for the game client and dedicated server:

• Game App ID 1898300: Used to install the game client, create the Steam Game Server Login Token, and set SteamAppId=1898300 during server launch.
• Dedicated Server App ID 3246670: Used with SteamCMD to download and install the ASKA server runtime.

Server Installation Package

SteamCMD downloads the server files to the directory specified through +force_install_dir. The package includes AskaServer.exe, configuration files, and the runtime components required to host a multiplayer world.

ASKA Dedicated Server is distributed as a Steam Tool. Administrators typically launch it through a batch file to apply the correct App ID and configuration path.

Steam Authentication

The server requires the correct App ID and a valid GSLT for Steam authentication and public listing. Missing or incorrect values may prevent the server from starting or appearing in the server browser.

Hardware Requirements and Server Capacity

The performance of an ASKA dedicated server depends on four main resources:

• CPU performance
• RAM capacity
• storage speed
• network latency and bandwidth

ASKA simulates villagers, structures, weather systems, and world state on the server. These processes run continuously while players are connected, so hardware limits directly affect stability and join performance.

• CPU performance determines how smoothly the world simulation runs. Faster cores help maintain consistent server tick rates when players build structures or expand settlements.
• RAM stores world data, villagers, and active structures. Larger worlds and longer sessions gradually increase memory usage.
• Storage speed affects how quickly the server reads and writes world saves. Fast SSD or NVMe storage reduces delays during save operations and world loading.
• Network quality affects connection stability. High latency affects responsiveness, while packet loss or jitter can cause disconnects and synchronization problems. Insufficient throughput matters mainly when the connection becomes congested.

ASKA is designed for small cooperative sessions rather than large public multiplayer servers. A typical ASKA world supports up to 4 players working together to manage villagers, resources, and settlement growth. Because of this design, most servers are run for private groups rather than large communities.

If you plan to keep a persistent world online for extended sessions, running the server on stable hosting infrastructure with reliable bandwidth and fast storage can provide a more consistent multiplayer experience than hosting directly from a gaming PC.

Quick Overview of the ASKA Dedicated Server Setup Process

Setting up an ASKA dedicated server follows a clear sequence. This section gives a quick overview before the guide moves into detailed instructions.

The typical setup flow looks like this:

1. Install SteamCMD or the Steam Server ToolPrepare the environment where the server software will run.
2. Download the ASKA Dedicated Server FilesUse SteamCMD or Steam Tools to install the server package.
3. Configure the Server Properties fileSet the core server properties, then create and deploy a separate preset if you are starting a custom world.
4. Open the Required Network PortsConfigure firewall or router rules so players can connect.
5. Launch the Server ProcessStart the server using a startup script or command line.
6. Join the server from the game clientPlayers connect through the in-game server browser.

The following sections explain each step in detail, including configuration, networking, and troubleshooting for stable multiplayer hosting.

Setting Up an ASKA Dedicated Server Using SteamCMD

SteamCMD is a common way to install an ASKA dedicated server on remote machines. Administrators prefer it because it works well on headless servers, hosting platforms, and automated deployment environments.

SteamCMD downloads the server package directly from Steam and installs it in the directory you choose.

Step 1: Install SteamCMD

Download SteamCMD from the official Steam developer website and extract it to a working directory.

Example:

C:\steamcmd\

Run steamcmd.exe once so the tool updates itself and prepares its runtime files.

Step 2: Create a Server Installation Directory

Create a separate directory where the ASKA server files will be installed.

Example:

C:\aska-server\

Keeping the server files separate from SteamCMD makes updates, backups, and troubleshooting easier.

Step 3: Download the ASKA Dedicated Server Files with SteamCMD

Use the ASKA Dedicated Server App ID 3246670 when installing the server package with SteamCMD.

Example:steamcmd.exe +force_install_dir "C:\aska-server" +login anonymous +app_update 3246670 validate +quit

ASKA server files and world saves are stored in different locations. The server files install to the directory you define in SteamCMD, while the save and backup section below explains where persistent world data is stored.

When SteamCMD Is the Best Choice

SteamCMD is useful when running servers on:

• Remote machines
• VPS or dedicated hosting environments
• Linux servers using unofficial Wine, Proton, or Docker compatibility layers
• Automated deployment pipelines

Administrators often create scripts or scheduled tasks to update the server automatically.

Why Many Admins Prefer SteamCMD Over Steam Client Installs

SteamCMD offers several advantages for server administrators:

• Works without a graphical interface
• Installs to any directory you define
• Supports automation and scripted deployments
• Commonly used by hosting providers

After the server files are installed, the next step is configuring the ASKA server properties, which define the server name, world settings, and access rules.

Steam Authentication and Running the Server Without Extra Copies

ASKA’s dedicated server is distributed through Steam and still relies on Steam authentication. This can confuse administrators running the server on the same machine they use for gaming.

The dedicated server files themselves can be installed with SteamCMD using the server App ID 3246670, and this does not require purchasing an additional copy of the game. At launch, set SteamAppId=1898300 and supply a valid GSLT created for App ID 1898300. The server does not require a second logged-in Steam client session.

Use the following token-based method when launching the server.

Use the Provided Batch File or Correct SteamAppId Value

If the same computer is used for both playing the game and hosting the server, make sure the server starts with the correct Steam App ID value and a valid GSLT.

If you host and play on the same machine, account and session behavior can be confusing. The safer fix is to launch the server with SteamAppId=1898300, add a valid GSLT, and verify that it appears in the server browser.

GSLT Account Requirement

The Steam account used to create the GSLT must meet Valve’s requirements and own ASKA. The server itself does not need a separate Steam account or a logged-in Steam client session.

Important Notes

• Current setup references commonly use +login anonymous with App ID 3246670 to install the ASKA Dedicated Server Tool.
• Server authentication with Steam services still requires a Steam Game Server Login Token (GSLT) created with the ASKA game App ID 1898300.

Understanding this Steam behavior prevents many startup and authentication issues when deploying an ASKA dedicated server.

Configuring the ASKA Dedicated Server

After installing the server files, the next step in the ASKA dedicated server setup is configuring the server settings. These settings control how the server appears in the server list and how players connect.

The ASKA server package uses server properties.txt to store core server parameters. The current configuration file commonly referenced by ASKA server tools and hosting docs is server properties.txt.

Typical server configuration options include:

• Display Name: The name shown in the multiplayer browser
• Server Name: Internal server identifier
• Password: Optional server access password
• Steam Game Port: Gameplay networking port
• Steam Query Port: Server discovery port
• Authentication Token: Steam Game Server Login Token (GSLT)
• Region: Server region identifier
• Keep Server World Alive: Controls whether simulation continues when no players are connected. Leave it disabled if the group wants the world to pause while empty.

These values determine how the server registers with Steam services and how clients locate the world.

Create and Deploy a Custom World Preset

1. Create the Preset

• Open New Game > Custom Game in the ASKA client.
• Configure the world and save the preset with a clear name.
• Find the generated file in:

%USERPROFILE%\AppData\LocalLow\Sand Sailor Studio\Aska\data\WorldCustomizationPresets

The filename begins with worldCustomization_.

2. Deploy the Preset

• Stop the dedicated server.
• Copy the preset to the location required by your server build or hosting panel.
• Set mode = custom.
• Select the uploaded preset and start a new world.

Existing worlds retain their original settings. A new preset cannot modify an existing save.

3. Protect the Configuration

• Keep the original server properties.txt file for schema comparison.
• Store the live configuration in a protected location.
• If supported, use -propertiesPath to point the startup script to the live file.
• Back up the configuration before updates or validation.
• Never commit GSLTs or passwords to version control.

After configuring the world, prepare the network ports required for multiplayer connections.

Create the Steam Authentication Token (GSLT) for ASKA

ASKA dedicated servers require a Steam Game Server Login Token (GSLT) to authenticate with Steam services and appear in the server browser. This token is generated from your Steam account and is tied to the ASKA game App ID: 1898300.

Prerequisites

• A Steam account in good standing
• A qualifying registered phone number on the Steam account
• Ownership of ASKA on the Steam account used to create the token

Step 1: Generate your GSLT on Steam

1. Open Steam’s Game Server Account Management page: steamcommunity.com/dev/managegameservers
2. Scroll to “Create a new game server account”.
3. Enter:
   • App ID: 1898300
   • Memo: any label you’ll recognize later (example: ASKA-MyServer-Frankfurt)
4. Click Create, then copy the token.

Important: Each ASKA server instance should use its own token.

Step 2: Add the Token to server properties.txt

Paste the token into your server’s config file (commonly referenced as server properties.txt by community + tooling).

Add or replace the authentication token line in server properties.txt using the key name expected by your build or hosting panel.

Example (generic): authentication token = YOUR_GSLT_TOKEN_HERE

Step 3: Restart and verify

Restart the server after adding the token. Confirm token acceptance in the console or log, then check whether the server appears in the in-game browser.

For successful Steam authentication and server listing, set SteamAppId=1898300 and add a valid GSLT created for App ID 1898300 in server properties.txt.

Security note

Steam warns you should not share game server login tokens and should delete/rotate them if exposed.

Ports Required for ASKA Dedicated Servers

Network configuration is required for any ASKA dedicated server that accepts external player connections. If the required ports are blocked, players will not be able to discover or join the server.

Multiplayer game servers normally rely on two categories of network ports:

Gameplay Ports

These ports handle real-time communication between the server and connected players. Player movement, world updates, and synchronization traffic pass through these ports.

Server Query Ports

Query ports allow the server to register with Steam and appear in multiplayer server lists. For ASKA, treat the query port as part of Steam-backed server listing and discovery. Do not assume that the server exposes standard Valve A2S fields or supports direct-IP joining unless the current build has been tested to do so.

Common ASKA dedicated server configurations use 7777 as the Steam game port and 27015 as the Steam listing or query port. Confirm the active values in server properties.txt before creating firewall, router, or container rules. Open the required UDP ports only, and add TCP only when the current build or hosting implementation explicitly requires it.

Common ASKA Dedicated Server Ports

Router and Firewall Configuration

If the server runs on a home network, the router must forward the required ports to the machine running the server. The firewall on the server must also allow incoming connections on those ports.

Without correct forwarding rules, external players cannot reach the server.

Common Networking Issues

Administrators often encounter several networking problems when hosting locally.

NAT Restrictions

Home networks typically use Network Address Translation. This hides devices behind the router and blocks incoming connections unless ports are forwarded.

Residential ISP Limitations

Some internet providers block incoming traffic or change public IP addresses frequently. This can prevent players from connecting reliably.

Port Conflicts

If another application is already using a required port, the server will fail to bind to that port and may not start correctly.

Why Dedicated Hosting Simplifies Networking

Hosting the server on dedicated infrastructure removes common residential NAT and ISP limitations while simplifying firewall and port management.

Dedicated environments usually provide:

• Public static IP addresses
• Direct port access
• Stable bandwidth and latency

For private groups running long-term worlds, dedicated hosting infrastructure often provides a more stable environment than hosting from a residential connection.

Launching the Server on Windows

After installing the server files, the next step in the ASKA dedicated server setup is starting the server process.

Most administrators launch the server using a batch startup script. A script ensures the correct working directory and environment variables are applied each time the server starts.

Create a Startup Script

Inside the server directory, create a file such as:

start_server.bat

A typical startup script looks like this:

@echo off
cd /d C:\aska-server

REM Important:

REM - Install/update uses AppID 3246670 (ASKA Dedicated Server Tool)

REM - Launch/runtime SteamAppId must be 1898300 (ASKA game AppID) for Steam auth/listing

set SteamAppId=1898300

start "" "C:\aska-server\AskaServer.exe" -propertiesPath "C:\aska-server\server properties.txt"

Why Use a Startup Script

Running the server through a script helps prevent common startup issues.

• Ensures the correct Steam App ID environment variable is available
• Keeps the server working directory consistent
• Allows you to add launch parameters or restart logic later

Administrators often expand these scripts with logging or automatic restart commands.

Server Logs and Monitoring

ASKA logs are written under the Windows account that runs the server, not necessarily inside the installation directory. Preserve the server console output and check the ASKA LocalLow directory for Player.log. For crashes, also check %LOCALAPPDATA%\Temp\Sand SailorStudio\Aska\Crashes.

These logs help diagnose problems such as:

• Server startup failures
• Configuration errors
• Player connection problems

If the server fails to start or does not appear in the server list, reviewing the log output is usually the fastest way to identify the cause.

Running ASKA Dedicated Server on Linux with Wine or Proton

The ASKA dedicated server is distributed through Steam as a Windows-supported Steam Tool. The available server binary is Windows-targeted, which means Linux hosts require a compatibility layer such as Wine or Proton to run it.

Administrators typically run the server on Linux using one of the following approaches.

Wine Runtime

Linux hosting is unofficial. It requires a tested Wine or Proton version, a persistent Wine prefix, the necessary Windows runtime libraries, and often Xvfb on a headless host. Package names and launch commands vary by distribution, so a generic sudo apt install wine command is not a complete ASKA server procedure.

Compatibility Layer Considerations

Running Windows server software on Linux may introduce additional complexity.

Possible limitations include:

• Compatibility differences between Wine versions
• Server updates that require libraries
• Additional debugging if runtime errors occur

Linux hosting is possible for experienced admins, but it should be treated as unofficial because the ASKA Dedicated Server is listed as Windows-supported.

Running ASKA Dedicated Server in Docker

Some administrators deploy game servers inside Docker containers. Containers package the runtime environment and server files together.

This approach can simplify repeatable deployments, but ASKA Docker setups usually depend on community-maintained images or Wine-based containers.

Typical Docker Architecture

A containerized deployment normally looks like this:

Host machine

└─ Docker container

└─ Runtime environment (Wine or system libraries)

└─ ASKA server process

Core Docker Configuration Elements

Most Docker game server deployments include three key components.

Container Image

The base image provides the operating system and runtime libraries.

Persistent Storage

Save files must be stored outside the container so they survive container restarts.

Example volume mount:

Map the container’s actual ASKA save directory to persistent host storage. The exact path depends on the Docker image, Wine prefix, and container user.

Network Ports

Required server ports must be exposed from the container to the host system so players can connect.

Docker is useful when administrators want repeatable deployments or automated server management.

ASKA Dedicated Server Save Location and Backup Strategy

World data is stored in the ASKA server save directory, which is created when the server generates a new world. On Windows, the known dedicated server save location is the LocalLow user data directory.

ASKA stores dedicated server saves in the Windows LocalLow directory, not inside the server install folder.

Default path:

C:\Users\<USERNAME>\AppData\LocalLow\Sand Sailor Studio\Aska\data\server

Worlds are saved inside folders named:

savegame_{SaveGameID}

Example:

C:\Users\John\AppData\LocalLow\Sand Sailor Studio\Aska\data\server\savegame_123456789

Quick open (Win + R):

%USERPROFILE%\AppData\LocalLow\Sand Sailor Studio\Aska\data\server

What Save Files Contain

Server save files store persistent world data such as:

• Map state and terrain
• Constructed buildings
• Villager data
• Player progress

This data allows the world to continue evolving across multiple sessions.

Backup Strategy

Regular backups protect the world's data from corruption or accidental deletion.

Stop the server before copying the live save directory. Then create a timestamped backup:

powershell -NoProfile -Command "$stamp=Get-Date -Format 'yyyyMMdd-HHmmss'; $dst=Join-Path 'D:\aska-backups' $stamp; robocopy 'C:\Users\<USERNAME>\AppData\LocalLow\Sand Sailor Studio\Aska\data\server' $dst /E /COPY:DAT /DCOPY:T /R:2 /W:5"

This command copies the save directory to a backup location.

Recommended practices include:

• Daily automated backups
• Storing backups outside the server folder
• Keeping multiple backup versions

Migrating a Server World

1. Stop the server
2. Copy the folder:

savegame_{SaveGameID}

from

C:\Users\<USERNAME>\AppData\LocalLow\Sand Sailor Studio\Aska\data\server

1. Move it to the same location on the new server
2. Start the server again

The world should load only when the complete save folder, save ID, required preset, configuration, file permissions, Windows account profile, and server build are compatible. Verify the migrated world before deleting the source copy.

How to Join an ASKA Dedicated Server

Once an ASKA dedicated server is running and reachable on the network, players can join it through the multiplayer interface inside the game.

Because ASKA is actively updated, the exact menu names may change slightly between updates. However, the general connection process follows the same structure used in most Steam multiplayer titles.

Joining Through the Multiplayer Server List

Most players join servers through the multiplayer server browser inside the game.

Typical Steps:

1. Launch ASKA from Steam.
2. Open the Multiplayer section from the main menu.
3. Browse the list of available servers.
4. Use the search field to locate the server name.
5. Select the server and choose Join.

If the server is configured correctly and publicly reachable, it should appear in the global server list.

Joining Password-Protected Servers

Many private groups protect their servers using a password.

When joining a protected server:

1. Select the server from the multiplayer list.
2. Enter the password when prompted.
3. Connect to the world.

Passwords are commonly used to prevent public access while allowing invited players to join.

When a Server Does Not Appear in the List

Sometimes, a running server may not appear in the browser immediately.

Common reasons include:

• The server is still starting and loading the world
• Firewall or router ports are not configured correctly
• Server listing updates have not propagated yet

If the server is running but does not appear in the browser, verify the GSLT, SteamAppId=1898300, query port, firewall rules, and region filter.

Internet-Listed and Password-Protected Servers

ASKA uses its in-game Steam-backed server browser. Current documentation does not establish a separate LAN-only or direct-IP joining mode.

Home-hosted servers require the configured ports to be forwarded and allowed through the firewall. Test browser discovery and joining from outside the host’s local network.

Troubleshooting Common ASKA Dedicated Server Problems

Even a properly installed ASKA dedicated server may encounter connection or performance problems. Most issues relate to networking configuration, server startup parameters, or hardware limitations.

The table below outlines common problems, their likely causes, and practical diagnostic steps.

Basic Diagnostic Workflow

When troubleshooting a server issue, administrators typically follow these steps:

• Confirm the server process is running.
• Review server logs for errors during startup.
• Verify that required ports are open and reachable.
• Confirm that configuration files are loading correctly.

If these checks do not identify the problem, compare the client and server builds, confirm the selected save and preset, and review the complete startup output.

ASKA Dedicated Server Hosting Options

Hosting location plays an important role in the stability and performance of a multiplayer server. ASKA servers can run in several environments depending on whether the goal is a private 4-player world, easier management, or more reliable uptime.

Hosting Environment Comparison

Factors to Evaluate When Choosing a Host

When selecting a hosting provider, several infrastructure characteristics have a direct impact on server stability.

Running High-Performance Game Servers with Dedicated Infrastructure

A reliable ASKA dedicated server depends on more than completing the initial installation. Correct App IDs, valid GSLT authentication, properly configured UDP ports, protected configuration files, and regular backups all contribute to stable hosting.

Once configured, the server keeps your Viking world available without relying on one player to host every session.

For a persistent multiplayer world, the underlying infrastructure is equally important. RedSwitches dedicated servers provide isolated computing resources, fast NVMe or SSD storage, high-bandwidth networking, DDoS protection, and full administrative access.

These capabilities help administrators maintain consistent performance, manage updates, monitor resources, and restore backups without competing with local gaming workloads.

With the setup covered in this guide and properly sized dedicated infrastructure, your group can spend less time resolving connection problems and more time building, defending, and expanding its settlement.

Choose a RedSwitches dedicated server when you are ready to give your ASKA world a stable, high-performance hosting environment.