You decide which services we may enable for analytics, personalization, and external content.
We use cookies and similar technologies on our website to personalize content, embed external media, and better understand how individual areas are used.
Necessary cookies
These entries support essential functions such as security, stability, and form processing.
Optional sections
AnalyticsMarketingPersonalizationExternal media
Your data may be processed with your consent or on the basis of legitimate interests. In the cookie settings, you can reject or explicitly allow each optional category.
Some services process personal data in third countries. By consenting, you also agree to this transfer. You can find more information in our Privacy Policy.
You can reopen and change your selection at any time. · 1.0.2
Learn how to fix common issues with your ASKA game server—from server tokens and the session list to lost save data → Find out more
10 November 20266 min read1 Views0 helpful
Introduction
Is your ASKA game server missing from the session list, has your progress disappeared after a restart, or won't your uploaded world load? Don't worry—most issues have a simple cause. Here we'll cover the most common problems and show you how to fix them quickly yourself.
FAQ
Frequently asked questions
Usually, the Steam server token is missing or was created for the wrong App ID. The correct ID is 1898300. Also check the console to make sure the server has fully started, and set the region to your group's region. The same region must be selected in the bottom-right corner of the in-game server list.
ASKA doesn't save when the server is stopped. It only saves via autosave and when the last player leaves. Have everyone leave the server before restarting, or wait for the next autosave.
The savegame_[ID] folder must be directly inside the savegame folder, and the save id value in server_properties.txt must exactly match the ID, meaning everything after savegame_.
If the server can't find the preset file in the presets folder, it starts in normal mode and displays a warning in the console. Check the folder and filename, and make sure Game Mode is set to custom.
No. ASKA allows a maximum of 4 players at the same time. This is a game limit.
Your Steam account can't be limited or banned, must have a phone number associated with it, and must own ASKA.
Feedback
Was this article helpful?
Your feedback helps us prioritize and improve content.
0 of 0 Users found this article helpful.
Personal support
Need more help than the guide provides?
Our ZAP support team knows your product — briefly describe your issue and we'll help you personally.
Navigation
ASKA
Problems and solutions
The most useful tool for troubleshooting is your game server's console. It shows you what your server is doing during startup, whether it has signed in to Steam, and whether it displays a warning—for example, about a missing token or preset.
Server token and Steam
Console warns that the Steam server token is missing
Your server needs its own Steam Game Server Login Token (GSLT). If it's missing, the console displays a warning during startup. Create the token at steamcommunity.com/dev/managegameservers using App ID 1898300, enter it in the Steam Server Token field under Startup Parameters in the Configuration tab, and restart your server. For detailed instructions, see Create a server token (GSLT).
Token is set, but the server still doesn't start properly
Check the Steam page to see which App ID your token was created for. The correct App ID is 1898300, the App ID for the game ASKA. App ID 3246670 belongs to the “ASKA Dedicated Server” tool and is listed right next to it on sites such as SteamDB. A token created for this App ID won't work. If that's the case, create a new token for 1898300 and replace the old one.
If you generated a new token or deleted one on the Steam page, the old token is no longer valid. Enter the current token instead.
Steam won't let me create a token
Valve has requirements for the Steam account you use to create the token: it can't be a limited account, it must have a phone number associated with it, it can't be banned, and it must own ASKA. A Steam account is generally considered limited until at least 5 USD has been spent in the Steam Store. If your account doesn't meet these requirements, it can't create tokens.
Session list and connection
Server doesn't appear in the session list
ASKA servers do not appear in the Steam server browser. They only appear in the in-game session list under Multiplayer → Join. Follow these steps:
Check the console to make sure your server has fully started and isn't showing a token warning. It can take a moment after startup for the session to become available.
Search for the exact name shown in the Server Name field.
Set the Region to your group's region, for example, europe instead of default, and restart the server.
In the game, select the same Region in the bottom-right corner of the server list. The list only shows servers in the selected region.
ASKA doesn't support direct connections via IP address.
More than 4 players can't join
ASKA allows a maximum of 4 players in a world at the same time. This is a game limit that also applies to dedicated servers. More players aren't possible, even with more server resources.
Password isn't accepted
Set the password in the Server Password field. You need to restart your server after changing it. If you only change a password directly in server_properties.txt, it will be overwritten with the value from the configuration the next time the server starts.
Save data and worlds
Progress is lost after a restart
ASKA only saves via autosave (every 10 minutes by default) and when the last player leaves the server—not when the server is stopped or restarted. Anything since the last autosave will be lost when the server restarts.
To avoid this:
Have all players leave the server before restarting it, or wait for the next autosave.
Schedule automatic restarts under Schedules for times when no one is playing.
Don't set Autosave Interval to disabled. A shorter interval, such as every 5 minutes, reduces potential data loss.
A new world is created every time the server starts
If Keep World Running is set to false (the default), your server creates a new world only when the first player joins. Until then, no world exists, and the value in the save id line may change with each startup. Once a player has joined, the server saves the world's ID permanently and loads it again every time it starts.
If a new world is still created every time, check the save id line in server_properties.txt. It must contain the ID of an existing world in the savegame folder.
Uploaded world won't load
For your server to load an uploaded world, two things must be correct:
The savegame_[ID] folder must be directly inside the savegame folder, not inside a subfolder—for example, one created when extracting an archive.
The save id value in server_properties.txt must exactly match the ID, meaning everything after savegame_, for example, save id = 86713_271026105256.
Stop your server before changing the line, then restart it. For step-by-step instructions, see our guide Manage save games and upload your own world. If the world still won't load despite the correct ID, please contact our support team.
New seed or preset has no effect
World Seed and Custom Preset only apply when a new world is created. If your server loads an existing world, that world keeps its settings. Clear the save id line in server_properties.txt so a new world is created the next time someone joins. Your old world will remain in the savegame folder. For details, see Set a world seed.
Custom preset is ignored
If your server can't find the file specified in the Custom Preset field in the presets folder, it starts in normal mode and displays a warning in the console. Check the following:
Is the preset file in your server's presets folder?
Is the filename exactly correct, for example, worldCustomization_server? Enter only the filename, not the folder.
Is Game Mode set to custom? No preset is used in normal mode.
The ASKA Dedicated Server uses approximately one CPU core even when idle. This is normal game behavior, not an error. If Keep World Running is set to true, the world also continues running continuously. Monitor usage under Statistics and upgrade your server if needed.
DDoS and other network threats
Game servers can be targeted by attacks that flood them with traffic, causing lag or dropped connections. ZAP-Hosting provides built-in protection systems to protect your server from common attacks. If you suspect an attack, contact our support team.
Preventive measures
Regular backups can save you a lot of stress. We already back up your game server automatically every day. With the ZapX Pass, you can also create your own backups at any time and restore them with a click—with ZapX Pass Pro, you can even automate backups on your own schedule. Before making major changes, download your world from the Savegames tab, and remember that ASKA doesn't save when the server is stopped.
Conclusion
These steps should help you resolve your issue. If they don't, please don't hesitate to contact our support team—we're here every day and happy to help! 🙂
Server hosting from €2.49 / month, online instantly, DDoS protection included.
Preferred source on Google
