Or you could just have nemrun send a kick/say command with that quit command option.
On Sat, Aug 28, 2010 at 2:26 PM, bl4nk <[email protected]> wrote: > I'm not a whiz with the Master Server protocol, but I'm pretty sure there's > no way to determine if an update is required or not, just that there is an > update. As for alerting players about the server shutting down, you should > be able to use the SteamTools extension ( > http://forums.alliedmods.net/showthread.php?t=129763) with it's > Steam_RestartRequested() forward to notify your players. > > On Sat, Aug 28, 2010 at 9:22 AM, PharaohsPaw <[email protected]> wrote: > > > > Oh boy more spam. > > > > > > Its been brought to my attention that valve's master server ignores the > > > requested port in server registration packets - instead using the > source > > > port of the packet to identify the server. This causes update daemons > > > to register multiple fake servers on valve's list instead of just one - > > > which isnt' the nicest thing for a script to be doing to valve's > > > servers. So... fix'd. > > > > > > Get it here: > > > http://nephyrin.net/tools/nemrun/1.5.1/ > > > (only the srcupdatecheck script has changed since 1.5) > > > > Hi Nephyrin, > > > > Thanks for your work with nemrun. I've started using it in the last > month > > or so and it has been nice to use. > > > > One question I've thought of after seeing it in action for a while and > > looking at the srcupdatecheck script a bit -- and I get the impression > > this may be more of an issue with challenge/responses -- but is there > some > > way to tell the difference between a mandatory update and an optional > > update with the responses we can get from the valve master server > > indicating an update is available? > > > > The reason I'm wondering is, if there was a way to distinguish between > > them, it might be neat to only have nemrun's updatedaemon only update the > > server when it's a mandatory update. > > > > I've also been working on adding a couple extra configurable screen stuff > > commands so that when an update is detected, it will (for example) throw > > an "exec update-pending-alert.cfg" into all the games running off of that > > tree, with sm_say commands etc. to alert the players that are currently > on > > the server that an update is coming in - and another "exec blah.cfg" hook > > for when the update is complete which execs right before sending the > > 'quit' to reboot the servers, so currently connected players know why the > > server is about to go down and that they should reconnect. > > > > Right now they only work for -updatefirst scenarios but I'm getting ready > > to add similar options for when -updatefirst is not being used (as I am > > probably going to stop using -updatefirst myself). > > > > If thats something you think might be neat I'm glad to share what I have. > > > > Cheers, > > PharaohsPaw > > > > _______________________________________________ > > To unsubscribe, edit your list preferences, or view the list archives, > > please visit: > > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
