> But, how do i update my l4d instance if i have multiple forks? Can i just > run the updater even though people are still playing? My biggest issue is > that when i want to update the installation there are always people on it > (which is ofcourse not a bad thing) but i just dont want to be the admin > that kicks people off for the update (unless the clients cant connect to > it, but then i can update anyways)
There's documentation for the mentioned shutdown (over netcon) command around somewhere, definitely in the list archives. Search for netcon/netconport or things like that if no one else provides a link. > Is there also a way to go back 1 version in updates? That way i could just > test some stuff out, also for tf2 to get it finally to work as it should > (i've modified srcds_run multiple times, and it did work at some point and > now it does not anymore) just thinking out loud here.. Clients don't get a choice about updating and can't roll back. There'd be no point. -Fyren _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
