How to Make an ASKA Server: Step-by-Step Setup Guide

To make an ASKA server, either install the official dedicated-server files with SteamCMD on a computer you control or rent a managed ASKA instance. Both methods require the same core sequence: install the server, create a Steam Game Server Login Token (GSLT) for ASKA, enter that token in the server properties, start the server, and join through ASKA’s Multiplayer browser. ASKA supports solo play or co-op with up to three friends, so plan for four simultaneous players unless a later official update changes that limit.

The self-hosted route gives you control over files, backups and network settings, but you maintain the machine yourself. Managed hosting costs a recurring fee but usually provides a control panel, automatic restarts and support. This guide explains both routes, the settings that matter, the limits that are actually documented, and the fixes for common connection problems.

What does an ASKA server actually provide?

An ASKA dedicated server runs the shared world independently of any one player’s game session. Friends connect to that world from ASKA’s server browser instead of relying on a host’s local co-op session. You can run the server on a spare Windows computer, a compatible rented machine, or a managed game-server account.

ASKA was released on June 20, 2024, by Sand Sailor Studio and Thunderful Publishing, and its Steam listing still identifies it as an Early Access game. That matters because server app IDs, configuration names, token behavior and hosting-panel workflows can change with updates. Keep the official Steam listing and your provider’s current documentation available when you update the installation.

The store description covers solo play and co-op with up to three friends. In practical terms, that is four players total. A server advertised as supporting more than four simultaneous players would need newer, authoritative documentation from the developer.

Which ASKA hosting method should you choose?

Self-hosting is best when you already have a machine, understand basic networking and want direct access to files. Managed hosting is easier when you want a web panel, provider-side maintenance or a location near your players. Neither method removes the need for a GSLT or the in-game region selection.

Consideration	Self-hosted with SteamCMD	Managed ASKA hosting
Cost pattern	No separate game-server subscription if you use your own machine, but you supply electricity, storage and internet service.	Recurring rental charge; exact prices and hardware tiers vary by provider and date.
Control	Direct control of server files, properties, backups and any supported modifications.	Control is exposed through a provider panel; file access and mod support depend on the plan.
Maintenance	You handle SteamCMD updates, operating-system maintenance, firewall rules and recovery.	The provider maintains the host machine; you still apply game updates and review configuration changes.
Setup effort	Requires SteamCMD, a dedicated folder, token creation and network configuration.	Usually a panel form for the token and properties, followed by Start and Stop controls.
Support	Your support is your own troubleshooting, community documentation and your internet provider.	Support availability depends on the host and its terms.
Location	You choose the physical machine and therefore its network path.	You choose from the regions the provider offers; select one close to most players.

Do not choose on a promised CPU or RAM number alone. No developer-certified dedicated-server minimum is published, and a provider’s advertised tier is not an official ASKA requirement.

What do you need before installing a self-hosted server?

Prepare the machine and accounts before downloading files. The following checklist prevents most avoidable setup failures.

• A computer or virtual machine that can stay online while friends play. The researched walkthrough uses Windows and SteamCMD; other operating systems may require compatibility workarounds that are not covered by the official instructions.
• A dedicated folder for SteamCMD and the ASKA server files. Avoid placing the installation inside a personal Steam library that other users or software may modify.
• Administrator access to install SteamCMD, open the required firewall rules and edit the generated properties file.
• A Steam account that can create a Game Server Login Token through Steam’s Game Server Management page.
• A stable upload connection and a way to forward or permit the ports shown in the generated server properties. Do not assume a port pair from an unrelated guide.
• A plan for backups and updates. Early Access patches can alter files or settings, so retain a copy of your properties and configuration files before updating.

Steam’s store lists 16 GB of RAM and 6 GB of storage for the game client. Those figures describe the player’s client, not a dedicated-server specification. They should not be presented as a guaranteed server minimum.

How do I install the ASKA dedicated server with SteamCMD?

The exact SteamCMD command used in the researched walkthrough is +app_update 3246670. Treat the app ID as volatile: verify it against current Steam tooling or the latest official hosting instructions if the command stops finding the application.

1. Download SteamCMD. Install or extract the SteamCMD tool into the dedicated server folder you prepared. Keep the path short and free of characters that your command shell may interpret.
2. Use the server machine’s Steam offline mode when appropriate. The walkthrough recommends Steam offline mode on the machine running the server so an ordinary client login does not interfere with the dedicated installation. This is a host-management choice, not a requirement for every deployment.
3. Run SteamCMD and install the app. In SteamCMD, authenticate as required by the current tool, select the installation directory, and run the update command shown below. The command is written as SteamCMD syntax, not a Windows PowerShell script.

app_update 3246670

4. Wait for the update to finish. SteamCMD should report that the app is installed or up to date. If it reports an invalid app, check the current app ID before changing anything else.
5. Find the generated server files. Open the installation directory and locate the server properties file. The filename and subfolder can change with a game update, so use the file created by the current build rather than copying a path from an old guide.

Do not launch the game client as a substitute for the dedicated executable. The dedicated files and their generated properties are the parts that publish the server to the browser.

How do I configure the self-hosted server properties?

Open the generated properties file in a plain-text editor and set the identity and access fields before the first launch. At minimum, define a display name that your friends can recognize and a password that is not reused elsewhere.

Set the identity and access values

• Server name: Use a short, distinctive name. Avoid punctuation that your provider panel or command shell may escape.
• Password: Set one for a private group. Share it through a private channel rather than posting it publicly.
• Region: Choose the region that minimizes latency for the group. Everyone must select the same region when joining.
• Authentication token: Leave the field ready for the GSLT you create in the next step. Keep the token out of screenshots, public logs and community posts.

Handle ports conservatively

The walkthroughs list game-port and query-port fields, but the researched guides do not agree on one universal port pair. A host panel may also generate different values. Read the ports from your current properties file, permit those exact values through the operating-system firewall and router, and use the provider’s current instructions if you rent a machine.

Changing a port is not enough by itself. The same value must be available to the server process, allowed through the local firewall and, on a home connection, forwarded from the router to the host computer. If any layer disagrees, the server may run locally but remain invisible to friends.

How do I create the Steam Game Server Login Token?

ASKA uses a Steam Game Server Login Token to authenticate the dedicated server. The token is created for ASKA’s game App ID, 1898300, not for the dedicated-server tool’s installation app ID.

1. Sign in to Steam and open the Game Server Management page.
2. Create a new login token for App ID 1898300.
3. Give the token a descriptive memo so you know which machine uses it.
4. Copy the token immediately and store it in a password manager or another private location.
5. Paste it into the authentication-token or GSLT field in the server properties file, then save.

Never publish the token in a support screenshot or paste it into a public chat. If it is exposed, revoke it through Steam’s management page and create a replacement, then update the server configuration.

How do I start the self-hosted server and join it?

After saving the token and properties, launch the ASKA dedicated-server executable supplied with the installation. Leave its process running while players connect.

1. Start the dedicated server and watch its console or log for a successful initialization message. A process that closes immediately usually indicates a missing file, invalid property or incompatible environment.
2. On the player’s PC, launch ASKA and open Multiplayer.
3. Choose Join.
4. Select the same region configured in the server properties.
5. Find the server by its display name, enter the password and join.

If the name does not appear, first verify that the process is still running and that the region matches. Then check the exact game and query ports shown in the generated properties, the firewall rule and any router forwarding. Do not replace those values with a port number copied from a different version of a guide.

How do I set up an ASKA server with managed hosting?

Managed hosting removes the SteamCMD installation and machine-maintenance work, but the authentication sequence is still the same. Providers expose the files through a control panel rather than a desktop folder.

1. Order or create an ASKA instance. Select a region close to the players and confirm that the plan supports the current ASKA build.
2. Open the game-control panel. Locate the ASKA server’s startup or configuration page.
3. Enter the GSLT. Paste the token created for App ID 1898300 into the field labelled Game Server Login Token, GSL Token or an equivalent authentication field. Citadel’s quick-start documentation uses the Game Server Login Token label; BisectHosting’s sequence places it in a GSL Token field.
4. Stop the server before editing. If the panel shows the instance as running, use Stop before changing properties. Editing a live file can be overwritten when the process restarts.
5. Edit server properties. Set the name, password, region and any ports or gameplay values exposed by the panel. GhostCap’s configuration guidance separates basic options from detailed config.txt settings.
6. Save and start. Start the instance and wait for the panel’s status or console to show that initialization completed.
7. Join in ASKA. Open Multiplayer, choose Join, select the configured region and select the server name.

Managed panels differ in labels, restart behavior and file access. Follow the panel’s current instructions for backups, scheduled restarts and updates instead of assuming that a control in one provider exists in another.

How do I change ASKA gameplay settings?

Basic properties identify and protect the server. More detailed world rules are commonly exposed in config.txt. Stop the server before editing that file, save a backup, then restart it so the new values load.

Use custom mode for custom-only settings

GhostCap’s guidance says to set mode=custom when you want custom-only gameplay settings to apply. If a setting appears to have no effect, check the mode first, confirm the spelling and capitalization used by the current file, and restart after saving.

Examples of available world controls

• Day length and year length
• Invasion difficulty
• Animal and monster population levels
• Precipitation
• Starting season
• Structure decay
• Terrain height

The exact option names and valid ranges can change during Early Access. Copy the syntax already present in the current configuration file rather than inventing a key from memory. Make one group of changes at a time so you can identify which value caused a startup or gameplay problem.

Why does my ASKA world pause when everyone leaves?

ThunderfulPaige, the ASKA community account, stated: “The server will pause if nobody is online.” That behavior is useful for a private group because the world waits between sessions instead of progressing while nobody can respond to events.

Some hosting configurations expose a keep-world-alive option. Enable it only when the group intentionally wants simulation to continue while the server is empty—for example, to allow seasons, villagers or other world activity to advance. Keeping the world alive can also consume resources and move the world state forward while no player is present, so agree on the policy with everyone who shares the save.

What ports and network settings should I use?

There is no reliable universal port pair in the available ASKA setup material. The researched walkthrough and another hosting guide give conflicting port guidance, while provider panels may assign their own values. Treat the generated properties file and current host documentation as authoritative for your installation.

Home-host checklist

• Reserve a local IP address for the server computer so a router rule does not point to a different device later.
• Allow the dedicated-server executable through the operating-system firewall, or create rules for the exact game and query ports listed in the properties file.
• Forward those same ports from the router to the server computer if players connect from outside your home network.
• Check whether your internet service uses carrier-grade NAT. If it does, ordinary port forwarding may not provide an inbound route; a rented host or a private network solution may be necessary.
• Restart the server after changing ports and test from a different network, such as a friend’s connection or a mobile hotspot.

Managed-host checklist

Do not add router rules for a provider-managed machine. Use the ports and connection details shown in the panel, and contact the provider if its status page reports that the instance is online but the server browser cannot find it.

What hardware does an ASKA dedicated server need?

No developer-issued CPU, RAM or storage minimum for the dedicated server is published in the available material. The Steam page’s 16 GB RAM and 6 GB storage figures are client requirements, so they cannot be used as a certified server specification.

For a self-hosted machine, choose hardware conditionally: leave memory and CPU headroom for the operating system, SteamCMD, logging and any other services, and keep enough disk space for the server, updates and backups. A four-player world may be light enough for modest hardware, but an official benchmark or minimum is not available to guarantee a particular tier. Watch CPU use, memory pressure, disk latency and upload utilization during a full session, then adjust the host or player count if the machine becomes the bottleneck.

For managed hosting, compare the provider’s included resources, backup policy, region and support rather than treating a listed tier as an ASKA-certified requirement. Ask whether resources are dedicated or shared and whether an upgrade preserves the existing world files.

How do I back up, update and recover an ASKA server?

Backups are your protection against configuration mistakes, Early Access changes and accidental world deletion. Stop the server before copying files so the save is not changing during the backup.

1. Stop the server cleanly.
2. Copy the world/save directory, server properties and config.txt to a separate disk or private storage location.
3. Label the backup with the date, ASKA build and any major configuration change.
4. Update SteamCMD or the managed instance according to the current instructions.
5. Start the server and test joining before inviting the whole group.
6. If the update breaks startup or changes a setting, stop the server and restore the last known-good files, then report the exact build and error to the provider or community support channel.

Do not assume that a provider’s automatic snapshot includes every configuration file. Confirm what is covered, how long snapshots are retained and whether you can download a copy.

What are the most common setup failures?

Symptom	Likely cause	What to check
SteamCMD cannot find the app	The dedicated-server app ID changed or the command was entered in the wrong context.	Verify the current app ID and run app_update 3246670 in SteamCMD, not in a normal game console.
Server starts but is invisible	Wrong region, blocked firewall, incorrect forwarding or mismatched ports.	Compare the in-game region with the properties file and permit the exact current game/query ports.
Authentication error	Missing, mistyped, revoked or wrong-app token.	Create the token for App ID 1898300, paste it without extra spaces and replace it if it was exposed or revoked.
Friends see the name but cannot join	Password mismatch, stale server process or a network path that permits discovery but not gameplay traffic.	Restart the server, verify the password and test the game port from outside the host network.
Custom settings do nothing	The file was edited while running, the mode is not custom or the option name changed.	Stop first, set mode=custom where required, use keys from the current file and restart.
World seems frozen between sessions	The documented empty-server pause is active.	Decide whether that behavior is desired; use a keep-world-alive option only when the host provides one and the group wants continuous simulation.

Is self-hosting or managed hosting better for a four-player group?

Choose self-hosting when one player can keep a machine online, configure a firewall and maintain backups. Choose managed hosting when the group values a nearby data-center region, a browser-based panel and provider support more than direct control over the operating system.

For either route, keep the same operational habits: use a private GSLT, stop before editing configuration, back up the world, and test after updates. The four-player limit means you do not need to size the service for a large public community unless official documentation later expands the supported population.

What should I verify before inviting friends?

• The server name is distinctive and the password works.
• The GSLT belongs to ASKA App ID 1898300 and is not visible in logs or screenshots.
• The configured region is the one players will select in Multiplayer > Join.
• The server process remains running after the first successful connection.
• The exact ports in the current properties file are allowed by the firewall and, for home hosting, forwarded by the router.
• A recent backup exists for the world and configuration files.
• Everyone understands that the world pauses when empty unless a supported keep-world-alive setting is deliberately enabled.

What can change because ASKA is in Early Access?

Early Access status means the installation app ID, property names, token handling, configuration keys and hosting-panel workflows may change after an update. Recheck the current Steam listing, SteamCMD output and your provider’s documentation whenever a patch causes a startup, discovery or authentication problem.

The most stable facts are the workflow and the player limit documented by the store: install the server, authenticate it with a token for the game, configure it, start it and join through the browser, with solo or up to three friends. Treat every port number, hardware estimate and unlisted setting as installation-specific until the developer publishes a definitive specification.

Frequently Asked Questions

Can I use the same ASKA world after moving from self-hosting to a managed provider?

Usually, migration depends on whether the provider lets you upload the world and configuration files. Stop the old server, make a complete backup, confirm the provider’s file locations, and test the copied world privately before deleting the original.

Does every player need to own ASKA on Steam?

The available setup material does not document a guest or family-sharing exception. Plan for each participant to use a legitimate ASKA installation and the same platform ecosystem unless the developer publishes different account guidance.

Can I run more than one ASKA server from one machine?

The documented instructions cover one instance and do not establish a supported multi-instance layout. Separate installations would need distinct files, ports, tokens and enough resources, so confirm that arrangement with current developer or provider documentation first.

What should I do if a patch invalidates my configuration?

Restore the pre-update backup, compare the newly generated properties or config file with your saved version, and reapply only keys that still exist. Keep a copy of the post-update file so you can identify renamed or removed settings before changing the live world again.