Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I have no idea why people keep saying that "there are only Linux binaries".
The only reason why there are "only Linux binaries" is because Windows doesn't need a specialized Dedicated Server, you can run one by using the Quake Live executable with special parameters. And here's actual proof of it, Dedicated Server running on Windows Server 2012 and without Steam running: https://i.imgur.com/hLIVJr7.png
So, how to do it?
- Install SteamCMD
- Login in SteamCMD using an account that owns Quake Live
- Just install Quake Live using SteamCMD, use:
app_update 282440 validate
- Once done, install the SteamWorks SDK Redist, use:
app_update 1007 validate
- Quit SteamCMD
- In your SteamCMD install directory, open steamapps\common\Steamworks SDK Redist and copy all the dll files to steamapps\common\Quake Live
- Edit baseq3\access.txt to your liking
- Edit baseq3\server.cfg to your liking
- Add set sv_pure "0" in the end of your baseq3\server.cfg server
- Run quakelive_steam.exe with + set dedicated 1 parameter
- Profit
This is all, you should now have a Windows server up and running.Please note: Don't bind a different IP in your server.cfg file because it causes the server to disappear from list and refuse all connections. This is a bug and can't be fixed afaik.
Edit: Just made a guide for that:
https://steamcommunity.com/sharedfiles/filedetails/?id=1410490276
Hopefully it will be easier to understand how to open a Windows dedicated server now.
Played Clan Arena all around for several days in a row and everything is working as expected, I don't see how it's "unstable".
The windows server is ok for a server that runs ccasionally. But if you want a server than runs 365 days a year 24/7, then a linux server is much more effective.
I run many different servers at the same time on the same machine, including but not limited to: Multi Theft Auto (2 servers), Serious Sam HD: The Second Encounter (4 servers), Counter-Strike: Global Offensive (1 server), Counter-Strike: Source (1 server), Serious Sam Fusion (1 server), Sven Co-op (1 server), Reflex Arena (1 server) and, of course, Quake Live (1 server). Then the server also runs a free VPN service, a free web hosting service, a free image hosting service, a wiki and a storage website in which we commit builds of our in-development game.
Maybe a solution would be running the server on an actual Windows Server machine (Windows Server 2012+), on a decent processor (Xeon with 4+ cores) and on a decent amount of RAM (24+ GB of RAM).
I'm running the server on a Xeon E7 8890 with 32 GB of RAM and Windows Server 2012 if this helps.
Edit: For developers: If the GUI really hangs the server up on slow processors, it is definitely possible to make an application that disables shellexecute and redirects stdin and stdout to/from commandline. This way, no windows will appear and the server will be a command-line.
Edit2: ^ Welp, the server just starts the GUI no matter what so I think it's not possible to do such thing. You'll have to live with the GUI.