Puny Human forums

For an always updated version head over to our wiki:

http://www.dystopia-game.com/wiki/index ... alkthrough

If you need further help, join #dystopia-help on gamesurge.

irc://irc.gamesurge.net/dystopia-help

If there are people there and they are awake, they will help.

If you don't want to get on irc, put questions here. Please only questions relevant to server setup in this topic though.

If you server won't start and just continuously restarts, check your config.cfg and valve.rc files for map dys_assemble and fix it like I say to above.

This doesn't apply since we fixed it.

the first code to download the DS* update is for HL1, thus totally out of date, we need a SDS** before we can do this, because this is a source mod, second of all, i have no clue how to do most of the stuff to set this up on my own for windows, can you enlighten me on this please?



*dedicated server

**source dedicated server

should still be ok to use, if you still need help try the IRC

If you need further help, join #dystopia-help on gamesurge.

irc://irc.gamesurge.net/dystopia-help

to get the new Dystopia v1.2 Server you don't need the download package anymore. instead you use the hldsupdate tool.
For Linux:

Code: Select all

./steam -command install -game "dystopia" -dir . -verify_all

Thanks Don. I am going to updated this for 1.2 today so please bear with me while we wait.

I have updated the install instructions for v1.2 on steamworks. If you find any problems with this, let me know and I will fix them.

If you server won't start and just continuously restarts, check your config.cfg and valve.rc files for map dys_assemble and fix it like I say to above.

Why is this line even in the config files if it borks things? Just fucking fix it!

It isn't in the config files, but if you copy over your old install configs then it might be in there.

The command in Linux is
./steam -command update -game dystopia -dir . -verify_all

Also, I dunno why you make the srcds directory since it's unused..

BTW unless you use screen you won't be able to 'fg' the backgrounded server once you log out - it isn't possible.

IMO just delete the other instructions and keep the 'screen' ones.

Good point, I just left them in for completeness sake.

I wrote this many moons ago, I didn't want to go deleting willy nilly.

btw, the tickrate launch option is "-tickrate" and NOT "-ticrate", as suggested in the guide

Thanks for the fix. Copy pasta error ftw.

Hi. I'm hoping people still read this thread as I'm having a bit of an issue with my Dystopia server. I followed the instructions on the Wiki, albeit with a different install path, but I don't have a "server.cfg" file in my dystopia\cfg folder. Did I do something wrong? Has anyone got a default server.cfg I can use?

Also, I'm a little confused about having to install Dystopia AND the orange box. Considering the orange box is just a package of games as far as I'm aware, what exactly am I installing? Source engine files?

Thanks guys.

This thread was updated a while ago so there might be differences now, I think there was, or still is some problem when installing dystopia using srcds, such as the directories were in the wrong place, I'm not too sure.

I do not know if a server.cfg should be there by default but it will also differ depending on if you want a primarily public or pug server.

The attached file is a fairly recent cfg I created, some of the variables may be obsolete or dependent on your specific setup so you might want to change things such as rate settings or fastdl.

Thanks, I'm using that now. My server also says it can't exec skill1.cfg when I launch it. Is that a problem? What is skill1.cfg, and do I need it? Thanks.

Nah, that is fine.

If it connects to vac, master servers, dys stats etc should be ok.

...
Also, I'm a little confused about having to install Dystopia AND the orange box. Considering the orange box is just a package of games as far as I'm aware, what exactly am I installing? Source engine files?.

The problem here is that our dedicated server deploy process is a bit broken, but since you can fix that issue yourself by issuing a 2nd command we haven't seen this as a high priority issue here.