Debriefing > Questions, Help, & How To's
Server help
czarofthefrozentundra:
--- Quote from: mookie on February 26, 2010, 04:08:03 pm ---I think they're talking about a blob file not blog, but maybe I'm behind the times.
--- End quote ---
Thanks. I was up all night and didn't catch the error.
--- Quote ---After you change sv_lan you'll need to changelevel for that change to be effective.
--- End quote ---
Yup, like I said, I hosted many servers in 3.14. I assure you, I tried this (heartbeat, and other options) to no avail. Didn't work like 3.14 for some reason. I may need to reinstall. Would prefer not to, though.
killermonkey:
Rest assured localhost server works the same as in Beta 3.1.4.
You must be sure that you forward your ports porperly. If you upgraded windows you might also want to make sure the firewall is not blocking anything.
czarofthefrozentundra:
Yeah. I am checking again. Just reinstalled GE:S Beta 4. Now I am getting a readout when I type heartbeat. It says:....
Nevermind. I got it working. The only thing I changed now is I made my own server.cfg and listenserver.cfg files by adding the sv_lan 0 command, and now I see it. Didn't change any of the port forwarding, as it was already in place from before. Any idea why the console wouldn't take my commands, but the .cfg files work?
UPDATE: Well, I tried this morning to load the server, nothing. Still LAN only. I didn't change a single thing over night. I notice one error I get when running heartbeat is the "A2C_PRINT [IP address:port] bad challenge." Would it help to modify the valve.rc? This is really getting annoying as I spend more time trying to run a server for my friends than playing with them.
Also, I have an SBG900 Surfboard router. Apparently the port forwarding instructions for this router are incorrect (as you cannot add overlapping ports). Perhaps this is the issue, although I ran beta 3.14 without any problems, and I didn't change the router settings after moving to beta 4.
UPDATE: Thanks km. Was a windows firewall problem. I guess somehow the application was blocked. When I disabled windows firewall, poof, there the server was. So dumb.
UPDATE: Oh my. Doesn't work anymore. Is it possible to assign the ports that the server uses instead of trying to do all the range and stuff. Maybe that would work. <sigh> So much for beta 4 and my friends.
UPDATE: Well, I got it working after about 6 hours of frustration. I am not sure exactly what did it, whether editing the listenserver.cfg file, adding +port 27015 to the launch properties or ip [my public ip]. Maybe it was something else. The strangest thing is that the server never showed up on the steam list. I happened to have it in my favorites, and looked at it and saw that the ip was public and not LAN. Then I asked a friend to try to connect to me directly, and it worked. After an hour or so of playing, however, the game still never showed up on the Steam servers. I hope someone with more networking and Valve knowledge than I can maybe help me make heads or tails of all this. So far I feel quite alone in this thread.
killermonkey:
Well i am chalking this up to valve, their master server is seemingly picking and choosing which servers to display recently... The important thing is if your friends can CONNECT to you. Regardless of its visibility (which we can't fix)
czarofthefrozentundra:
--- Quote from: killermonkey on March 05, 2010, 01:37:37 pm ---Well i am chalking this up to valve, their master server is seemingly picking and choosing which servers to display recently... The important thing is if your friends can CONNECT to you. Regardless of its visibility (which we can't fix)
--- End quote ---
I agree. It was such a relief to finally see the game pop up on favorites with the public IP and seeing my friend connect. Just lucky thing I checked the server info or I wouldn't have seen it and would have gone to bed livid after wasting half a day/ I racked by brain forever, trying to figure out what was wrong, going to forums all over the place, reading about similar problems, blah, blah, blah. Usually every Thursday night I put up a server and play with the 10+ people I introduced to this game, but it hasn't happened because of all this valve junk. Ridiculous. Thanks for the positivity and support (I chewed out a guy on email for not sending me a package on time because I was upset, had to apologize this morning to him.).
It seemed after a while that I couldn't have been a problem on my end, as I tried on two separate computers after changing the ports. Port checker came out fine, just the stupid servers weren't showing the game, which is usually how I check to see if it is visible for others. Now I know that I cannot rely solely on that.
KM, do you know if you have to put the ip [my public ip] in for it to show up. I read that on a Steam support page talking about listen servers. I never did this with 3.14, but then again, I am not really sure if everything was working fine yesterday, and I just couldn't see the server, or if one of those things I did helped.
Also, (if you don't mind a couple more questions) which commands can I put into the listenserver.cfg. It seems that a bunch of them I put in worked fine, but others (like ge_startarmed 2 and I think ge_gameplay_mode 1) didn't work, and I had to manually do it after the server started. Could be wrong about the ge_gameplay.
Last question: is there a post or link to show me how to make a config file that does the same thing as the "crate server" GUI? (random map, random weapons, etc)?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version