STORE COMMUNITY ABOUT SUPPORT
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) 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
Feel free to pastebin it and share it with us and we can try to help you out.
1) Downloading the game to the server did not work when logged into SteamCMD as anonymous. Needed to use Steam account.
2) I used forced dir and my warfork directory looked completely different. The find command gave me a bunch of access denied messages when logged in as steam user, and wouldn't function at all when logged in as root. The path to the folder which hosts my dedicated_autoexec.cfg is home/steam/warfork/Warfork.app/Contents/Resources/basewf. I ended up just downloading FileZilla and looking on there.
Edit: to clarify, "warfork" was what i set as the new directory when using force dir
Thanks for posting this guide.
Did either of you get steam keys for access to the game before Early Access?
Can Confirm this is the file path as well for dedicated_autoexec.cfg
Thanks again for the guide.
Without downloading the steamcmd
You can, if you are using windows just navigate to your steam folder for Warfork and run the windows server binaries instead.
The Linux setup seems to be more stable though. I tried to talk about Windows hosting a little here. I'll add more to this post whenever I get a chance.
Whether you're on Windows, Linux or Mac, the linux server binaries should be in the same Warfork.app path.