I'm trying to host a tournament, but I have no idea how to establish a simple config for the server! Is anyone willing to add me on Steam and sort of walk me through it? Like, it may seem simple but I really need someone to treat me like an idiot and go through step by step.
Your best bet is probably using one of the established server configs like ESEA, UGC, or the old CEVO ones if they still work. At least that seems a lot easier.
Are those easily altered? I have a specific weapon whitelist that I need to use, as well as setting time and point limits. Also, how exactly do I use them on the server?
yes they can be easily modified. just put them in your server's cfg folder in tf and exec them from the console with rcon. add me if you need any help with that.
hl configs: http://www.ugcleague.com/files_tf2h.cfm
6s configs: http://www.ugcleague.com/files_tf26.cfm
6s configs for ESEA: http://matchmod.net/download/MatchMod/league-configs/ESEA-Configs-20110103.zip
hl configs: http://www.ugcleague.com/files_tf2h.cfm
6s configs: http://www.ugcleague.com/files_tf26.cfm
6s configs for ESEA: http://matchmod.net/download/MatchMod/league-configs/ESEA-Configs-20110103.zip
I don't really have time tonight to run through it in great detail, but hopefully these steps get you in the right direction. I'm going to assume you have a server up and running, and you have FTP access.
These are off the top of my head, so I could be wrong.
1. Use FTP to put something like ESEA.cfg or CEVO.cfg into the "tf/cfg" folder on your server. If you have an NFO server, this can be done through an autoinstaller on the control panel.
2. These are just text files, and they're not too difficult to edit; a lot of them are commented with stuff that can be changed, and most of the variables are self explanatory.
3. Create a textfile called item_whitelist.txt in your cfg. You could use this as a basis, nixnyte wrote it up real quick for ESEA S13 weapons: http://pastebin.com/raw.php?i=dHd9h6DA
Note that this is more of a blacklist; the listed items are the ones that are not allowed; anything not there is legal. The format should be pretty easy to follow.
4. In your server, all you have to do now is "exec config" where config is the name of the file (excluding the extension, .cfg, that you put in step one). Everything should handle itself from there.
And that's it! You should be good to go just from those few steps, hope it helps.
These are off the top of my head, so I could be wrong.
1. Use FTP to put something like ESEA.cfg or CEVO.cfg into the "tf/cfg" folder on your server. If you have an NFO server, this can be done through an autoinstaller on the control panel.
2. These are just text files, and they're not too difficult to edit; a lot of them are commented with stuff that can be changed, and most of the variables are self explanatory.
3. Create a textfile called item_whitelist.txt in your cfg. You could use this as a basis, nixnyte wrote it up real quick for ESEA S13 weapons: http://pastebin.com/raw.php?i=dHd9h6DA
Note that this is more of a blacklist; the listed items are the ones that are [i]not[/i] allowed; anything not there is legal. The format should be pretty easy to follow.
4. In your server, all you have to do now is "exec config" where config is the name of the file (excluding the extension, .cfg, that you put in step one). Everything should handle itself from there.
And that's it! You should be good to go just from those few steps, hope it helps.
I followed the instructions you listed, but when I try to execute the config on my server, I get this message "'ugc_6v_standard' not present; not executing." I haven't altered the UGC configs in any way, I just wanted to test them on my server before I edited them.
Should I put them in the SourceMod folder instead?
EDIT: NEVER MIND! I figured out what I needed to do! Everyone, thank you so much for your help, I would have never figured this out without you.
Should I put them in the SourceMod folder instead?
EDIT: NEVER MIND! I figured out what I needed to do! Everyone, thank you so much for your help, I would have never figured this out without you.
It looks like the DocProfessor has become the student.