HLDSUpdate Tool, does update work?

Balmark

B170 is currently available... however:

C:\Program Files\Valve\HLServer>"C:\Program Files\Valve\HLServer\HldsUpdateTool.
exe" -game naturalselection2 -command update -dir c:\Servers\NS2Server
Checking bootstrapper version ...
Updating Installation
Checking/Installing 'Natural Selection 2 - Dedicated Server' version 11


HLDS installation up to date

........................
then
........................

C:\Servers\NS2Server>C:\Servers\NS2Server\server.exe -name "Core Server B170 10S
lot" -limit 10 -lan false -map ns2_rockdown
Disabled saving of configuration file overrides.
Changing setting 'lanGame' to: 'false'...
Changing setting 'mapName' to: 'ns2_rockdown'...
Changing setting 'playerLimit' to: '10'...
Changing setting 'serverName' to: 'Core Server B170 10Slot'...
<!--sizeo:3--><span style="font-size:12pt;line-height:100%"><!--/sizeo--><b>Build 169</b><!--sizec--></span><!--/sizec-->
Starting Natural Selection 2
Starting server

endar

It does, here is my log of this mornings restart:
<div class='codetop'>CODE</div><div class='codemain' style='height:200px;white-space:pre;overflow:auto'>Date: 04/04/11
Time: 05:30:00
--------------------------------------------------------------
Build 170
Starting Natural Selection 2 (using NS2-GmOvrmind(v7))
Starting server
Connected to Steam servers</div>
<div class='codetop'>CODE</div><div class='codemain' style='height:200px;white-space:pre;overflow:auto'>hldsupdatetool -command update -game naturalselection2 -dir C:\somedir
Checking bootstrapper version ...
Updating Installation
Checking/Installing 'Natural Selection 2 - Dedicated Server' version 11


HLDS installation up to date</div>

No idea whats giving you that old number, can people with 170 connect? If not have you tried deleting your files and getting them all again.

Adama

I agree with Endar

Run the same command again but point to another directory (NSServer2 for example) - this will redownload everything.

Balmark

I'm sure using a new folder will get 170, but that's not the point :P I wanted to setup so it'd just perform a scheduled task to do the update

I'll do a 'manual' update now and see what happened next build :/ althought I don't hold any high hopes it'll do it.. are there issues with running an update while a server is running? That's all I can think of ..

I guess I can run a scheduled task and batch the update command with the server command every night and stop it after 23.5 hours of execution.

(the first time the update ran, the server would have been running, I guess that might have created a problem if files were in use)