Protecting server for map testing?
StreamlineData
10-23-2005, 09:29 PM
Sorry, couldn't find this anywhere else (yes, I tried the search button).
Everytime I test my map (starts up automatically after I compile in Hammer), people start joining.
Although this does give a chance for others to see my WIP as I go.... I prefer that they didn't until I'm ready to show it off.
How do I protect my localserver so that this doesn't happen?
Dark Dog
10-23-2005, 09:30 PM
sv_lan 1 usually does the trick
Bocasean
10-23-2005, 09:30 PM
In server.cfg make sure that sv_allowdownload 0 is enabled
Default is sv_allowdownload 1
If you do that, then you can test whatever you'd like.
StreamlineData
10-23-2005, 09:34 PM
Cool... where is the server.cfg file located? in the CFG folder?
Do I have to make the file? because I can't find it...
josh_u[RR]
10-23-2005, 09:51 PM
just password protect it and don't tell anyone. :P
the server.cfg goes in the .cfg folder and yes, you'll proably have to make it. check the server forum if you need an example.
prone ranger
10-30-2005, 07:44 AM
I dont let hammer run dods after compiling. I close hammer then run dods and create a passworded server.
no need to edit configs or any of that :D
I think that once you have pw'd the created server it will be pw'd everytime you create a new server on your pc so you probably could just run it from hammer after compiling after the pw has been set up in the new game menu
Stuka
10-30-2005, 09:31 AM
this happened to me once, pretty annoying when they start whining about how nothing works
StreamlineData
10-31-2005, 09:29 PM
Originally posted by Stuka
this happened to me once, pretty annoying when they start whining about how nothing works lol... sigh.. some people, eh?
Going on the suggestion of some people, right after the map loads, I found that going into the console and typing:
sv_password <passwordhere>
works perfectly.
TheMiede
10-31-2005, 09:59 PM
Lol, i have the opposite problem. Whenever i compile or create my own server i cant people come on my server to test it. Damn firewalls(or so i think).
StreamlineData
10-31-2005, 10:07 PM
Originally posted by TheMiede
Lol, i have the opposite problem. Whenever i compile or create my own server i cant people come on my server to test it. Damn firewalls(or so i think). lol =D
I don't think it's a firewall problem... because I have a firewall and I still (used to) have people joining.
How long have you waited for people to join? For me, it only took about... 5-10 minutes before people started joining (at which point, I shut down the server... lol ;) )
I think the map name also affects people's decision whether or not they want to join your server.
Have you checked to see if you have the server.cfg file in your CFG folder that might be restricting people from joining your server?
[edit]
btw, Valetta is lookin pretty good there! :)
Effexx
11-01-2005, 03:47 AM
Originally posted by TheMiede
Lol, i have the opposite problem. Whenever i compile or create my own server i cant people come on my server to test it. Damn firewalls(or so i think).
This may be pointing out the painfully obvious, but try:
sv_lan 0
StreamlineData
11-01-2005, 04:22 AM
Originally posted by Effexx
This may be pointing out the painfully obvious, but try:
sv_lan 0 Actually... heh. I tried that.
It didn't work.
Someth|ngW|cked
11-02-2005, 01:59 AM
I had someone join when i was running a test compile of hill-clasic for dods and even though the map was only at about 30% complete he complimented every aspect of it so i guess i am going in the right direction ;)
[SAS]==Colster==
11-02-2005, 06:29 AM
Originally posted by StreamlineData
lol... sigh.. some people, eh?
Going on the suggestion of some people, right after the map loads, I found that going into the console and typing:
sv_password <passwordhere>
works perfectly.
Just add that line to server.cfg too
sv_password <passwordhere>
We had the same problem when we first launched our dod:s server.
On launch night we had decided to password our clan pub server then gave out the password on our forum, but the minute I booted the server just to check everything was ok all 32 slots filled.... it was scary.
I had to quit the server and while it was winding up to auto restart change the server.cfg
StreamlineData
11-02-2005, 11:31 AM
Originally posted by [SAS]==Colster==
Just add that line to server.cfg too
sv_password <passwordhere>
We had the same problem when we first launched our dod:s server.
On launch night we had decided to password our clan pub server then gave out the password on our forum, but the minute I booted the server just to check everything was ok all 32 slots filled.... it was scary.
I had to quit the server and while it was winding up to auto restart change the server.cfg I actually did add that line to my server.cfg file..
...as I said before, "server.cfg" didn't work. People still joined.
Twigee
11-02-2005, 11:45 AM
Pull the network cable for the test? People can't join to the end of a cable.
Ginger Lord
11-02-2005, 11:50 AM
sv_lan 1 will make your server only available to computers connected to your network.
It should work, failing that password protect, failing that just unplug your line as the above said.
josh_u[RR]
11-02-2005, 12:13 PM
Originally posted by StreamlineData
I actually did add that line to my server.cfg file..
...as I said before, "server.cfg" didn't work. People still joined.
type in console:
exec server.cfg
if you use a GUI to start your server, which I'm sure you are, the server.cfg doesn't execute on startup unless you add it to autoexec.cfg.
Day of Defeat Forum Archive created by
Neil Jedrzejewski.
This in an partial archive of the old Day of Defeat forums orignally hosted by
Valve Software LLC.
Material has been archived for the purpose of creating a knowledge base from messages posted between 2003 and 2008.