Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
2. Does your server have any plugins?
3. Did you install that dreadful SynergyPlus crap?
2. it's a "create server" thing from game menu. so, no.
3. no.
I made a script a while back to make it easier for people to install Synergy dedicated server. All you have to do is run the script as admin for the first install. There is an option for the Synergy Development Beta as well.
Rename Syndsinstall27015.txt to Syndsinstall27015.bat to make it an executable script. Place the script in the same folder as steamcmd.exe and run it.
https://www.dropbox.com/s/yh951oh5eniwj2j/Syndsinstall27015.txt?dl=1
You can put in your server-specific settings like sv_password "" etc in steamapps\Synergy\synergy\cfg\server2.cfg or steamapps\synbeta\"" after installing.
What I was looking here was a quick solution for me and my friends to have a quick play, as googling for this problem lead to nothing useful.
It may also be caused by certain mods attempting to attach to an open instance of Steam for their API. In that case, you can try running that mods dedicated server client with -nosteam on the startup line.
For Synergy dedicated server, it doesn't.