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 problems with your Silica game server—from the server list and maps to configuration and admin permissions. Find out more →
10 November 20263 min read1 Views0 helpful
Introduction
Is your Silica game server missing from the server list, not starting on the map you want, or are your admin permissions not working? Don't worry—most problems have a simple cause. Here we'll cover the most common issues and how you can quickly fix them yourself.
FAQ
Frequently asked questions
Check in the Overview to see if your server is online, and in the console to see whether it has logged in to Steam. It can take one or two minutes after starting the server or changing a setting. Search for the exact server name and turn off filters.
The map must be listed in the MapList for the selected game mode in Silica/ServerSettings.xml, with the exact capitalization. Otherwise, the server keeps the current map and displays a warning in the console.
No. The Silica console is read-only. It shows what your server is doing and any warnings about your configuration.
In the Files tab, in the Silica folder, as Server_*.log files. Your server keeps the ten most recent log files.
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
Silica
Problems and solutions
Your game server's console is the most useful tool for troubleshooting. It shows what your server is doing as it starts, whether it has logged in to Steam, and whether it reports a warning about your configuration. These warnings begin with [silica-config] warning. The Silica console is read-only, so you can't enter commands there.
Server list and connection
Server doesn't appear in the server list
Check in the Overview to see if your server is online.
Check the console to see whether your server has logged in to Steam. It may take a little while after that for the server to appear in the list. After changing the settings, it can take one or two minutes.
Search for the exact name in the Server name field and turn off filters in the server list.
Check that your game is up to date. The game and server must be running the same version. Update your game through Steam. If your server is older than your game, apply the update in the Overview: as soon as a new server version is available, ZapX will display the Update available notice with the Apply update button. If you've set a server password, make sure you enter it with the correct capitalization. If the server is full, no one else can join until a spot opens up.
Configuration
Server doesn't start on the selected map
Your server checks the map against the map list for the selected game mode. If the map isn't listed there, the server keeps the current map and displays a console warning that the map isn't available for this mode, along with a list of allowed maps. Enter the name exactly as it appears in the MapList in Silica/ServerSettings.xml, including capitalization and without spaces. Learn more in our guide Server configuration.
My changes to ServerSettings.xml are gone after restarting
Your server writes the server name, password, game mode, ports, and player count to the file from the startup parameters every time it starts. So always change these values in the Configuration tab under Startup parameters.
If the file is no longer valid XML after a change, your server renames it to ServerSettings.xml.broken when it starts and creates a new file with the default values. You can find your changes in the file with the .broken extension.
Admin permissions aren't working
Check the console to see if your server skipped the ID with a warning. Only a 17-digit Steam64 ID beginning with 7656 is valid—not a Steam name or a custom profile URL. You must restart the server after adding it. Learn more in our guide Become an admin.
Performance
Server is overloaded or lagging
Check the Statistics tab to see how heavily your server is using CPU and memory. If you've increased Max Fps, your server processes more frames per second and uses significantly more CPU, even when there are no players. If so, set it back to the default value of 60. Large maps also need more memory than small ones.
More help
If none of these suggestions help, our support team is available every day. Just start a Support chat in your ZapX customer account and describe your problem in as much detail as possible, ideally including the last few lines from the console. You can also find your server's log files in the Silica folder in the Files tab, named Server_*.log. Your server keeps the ten most recent files.
Conclusion
With these tips, you should be able to solve the most common problems with your Silica server yourself. If you have any other questions, our support team is available every day! 🙂
Server hosting from €2.49 / month, online instantly, DDoS protection included.
Preferred source on Google
