Re: [hlds_linux] Instructions for migrating an existing TF2 server to beta / new format?
You actually need to create an additional subdirectory inside of custom (e.g. .../tf/custom/my_custom_content/) and copy your maps-dir etc. into that one because srcds mounts everything (vpks and directories) inside custom/ to the game-rootdir on startup. See gameinfo.txt and custom/readme.txt for more info on that mechanism. I don't know if I've already posted it to the mailing list. Last time I've to do lot of work (normal and coding), so i can't remind.. You can do all this steps automated and easier for your customers (yourself). If you are using Linux, you can write a shell script to fix it. 1.) Install a vanillaserver with hldsupdatetool 2.) Copy the vanillaserver to a second location for testing and run this one time. Then create a filelist from this server: $ cd $serverroot $ find -type f -print0 | xargs egrep -Zzv 'motd\.txt|otherfile\.cfg' > tf2_hldsupdatetool_filelist.0 # Last command searches only for files and seperate them with 0-byte-char, # then piping to egrep for filtering (-v) with input and output with delimiter \0 (-z for input -Z for output), # then redirect the output to a file 3.) Put addons, maps, configs all this modifications to the right place (old syle) for testing all 4.) Update the testserver with steampipe 5.) Delete with files with your created filelist of the old vanillacontent: cd $serverroot cat /place/of/tf2_hldsupdatetool_filelist.0 | xargs -0 rm # cat prints the filelist to stdout and piping it to xargs # xargs is calling the command rm (for remove) with all args # you have to use the -0 option the tell xargs for using # the 0-byte-delimiter for arguments 6.) Moving content and configs: $ cd $serverroot/orangebox/tf $ mkdir custom $ mv maps materials particles reslists sound custom #control right spelling, maybe i missed one dir $ mv $serverroot/orangebox/tf/* $serverroot/tf/ $ cd $serverroot/tf/ # start your updated server and test all I've follwed Peter Reinhold's description and think that all customcontent like maps, models, sound and other have to move into the subdirectory custom. Maybe I'm wrong and it doesn't work for anthing else except maps. The command has naver been testet for this case but may work. Test it only on servers you don't neet. Best thing is to crate a new useraccount for testing all this things. Providers can use thier scripts to rollout a convertion one time. Not every stucture is the same. I've told it 100 times, use symlinks and you have never the problems with changed structure. Easier for deleting broken symlinks an easier to convert to new stucture with all files which the customer has created. 2013/2/26 Peter Reinhold : > On 26.02.2013 16:43, Ross Bemrose wrote: > >> The only one that will take any time is moving maps. Based on what's >> previously been discussed >> >> 1. Install the new TF server into a new directory >> 2. Move oldserver/orangebox/tf/addons/ to newserver/tf/addons/ >> 3. Move oldserver/orangebox/tf/cfg/ to newserver/tf/cfg/ >> 4. Sort through the oldserver/orangebox/tf/maps folder for custom maps >> and move them to newserver/tf/custom/maps/ (note: /custom is optional >> here, but Valve's maps still live in tf/maps/ No sense in keeping >> them together if you don't have to) >> 5. Harass plugin makers to make VPK files for their models, materials, >> and sounds. Or just do it yourself; the vpk binary comes with current >> TF2 Beta clients and servers. Note that you'll still need them loose >> on the disk on fastdownload servers as it sounds like there are no >> plans on making VPKs downloadable that way (although possible Workshop >> support was mentioned...) > > > So basically, reinstall and then move all the files you put into the TF2 > folder yourself to the new folder .. Check. > > > > /Peter > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
Re: [hlds_linux] Instructions for migrating an existing TF2 server to beta / new format?
I don't know if I've already posted it to the mailing list. Last time I've to do lot of work (normal and coding), so i can't remind.. You can do all this steps automated and easier for your customers (yourself). If you are using Linux, you can write a shell script to fix it. 1.) Install a vanillaserver with hldsupdatetool 2.) Copy the vanillaserver to a second location for testing and run this one time. Then create a filelist from this server: $ cd $serverroot $ find -type f -print0 | xargs egrep -Zzv 'motd\.txt|otherfile\.cfg' > tf2_hldsupdatetool_filelist.0 # Last command searches only for files and seperate them with 0-byte-char, # then piping to egrep for filtering (-v) with input and output with delimiter \0 (-z for input -Z for output), # then redirect the output to a file 3.) Put addons, maps, configs all this modifications to the right place (old syle) for testing all 4.) Update the testserver with steampipe 5.) Delete with files with your created filelist of the old vanillacontent: cd $serverroot cat /place/of/tf2_hldsupdatetool_filelist.0 | xargs -0 rm # cat prints the filelist to stdout and piping it to xargs # xargs is calling the command rm (for remove) with all args # you have to use the -0 option the tell xargs for using # the 0-byte-delimiter for arguments 6.) Moving content and configs: $ cd $serverroot/orangebox/tf $ mkdir custom $ mv maps materials particles reslists sound custom #control right spelling, maybe i missed one dir $ mv $serverroot/orangebox/tf/* $serverroot/tf/ $ cd $serverroot/tf/ # start your updated server and test all I've follwed Peter Reinhold's description and think that all customcontent like maps, models, sound and other have to move into the subdirectory custom. Maybe I'm wrong and it doesn't work for anthing else except maps. The command has naver been testet for this case but may work. Test it only on servers you don't neet. Best thing is to crate a new useraccount for testing all this things. Providers can use thier scripts to rollout a convertion one time. Not every stucture is the same. I've told it 100 times, use symlinks and you have never the problems with changed structure. Easier for deleting broken symlinks an easier to convert to new stucture with all files which the customer has created. 2013/2/26 Peter Reinhold : > On 26.02.2013 16:43, Ross Bemrose wrote: > >> The only one that will take any time is moving maps. Based on what's >> previously been discussed >> >> 1. Install the new TF server into a new directory >> 2. Move oldserver/orangebox/tf/addons/ to newserver/tf/addons/ >> 3. Move oldserver/orangebox/tf/cfg/ to newserver/tf/cfg/ >> 4. Sort through the oldserver/orangebox/tf/maps folder for custom maps >> and move them to newserver/tf/custom/maps/ (note: /custom is optional >> here, but Valve's maps still live in tf/maps/ No sense in keeping >> them together if you don't have to) >> 5. Harass plugin makers to make VPK files for their models, materials, >> and sounds. Or just do it yourself; the vpk binary comes with current >> TF2 Beta clients and servers. Note that you'll still need them loose >> on the disk on fastdownload servers as it sounds like there are no >> plans on making VPKs downloadable that way (although possible Workshop >> support was mentioned...) > > > So basically, reinstall and then move all the files you put into the TF2 > folder yourself to the new folder .. Check. > > > > /Peter > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
Re: [hlds_linux] Instructions for migrating an existing TF2 server to beta / new format?
On 26.02.2013 16:43, Ross Bemrose wrote: The only one that will take any time is moving maps. Based on what's previously been discussed 1. Install the new TF server into a new directory 2. Move oldserver/orangebox/tf/addons/ to newserver/tf/addons/ 3. Move oldserver/orangebox/tf/cfg/ to newserver/tf/cfg/ 4. Sort through the oldserver/orangebox/tf/maps folder for custom maps and move them to newserver/tf/custom/maps/ (note: /custom is optional here, but Valve's maps still live in tf/maps/ No sense in keeping them together if you don't have to) 5. Harass plugin makers to make VPK files for their models, materials, and sounds. Or just do it yourself; the vpk binary comes with current TF2 Beta clients and servers. Note that you'll still need them loose on the disk on fastdownload servers as it sounds like there are no plans on making VPKs downloadable that way (although possible Workshop support was mentioned...) So basically, reinstall and then move all the files you put into the TF2 folder yourself to the new folder .. Check. /Peter ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
Re: [hlds_linux] Instructions for migrating an existing TF2 server to beta / new format?
Just realized I forgot to mention copying mapcycle.txt, but you realized that on your own, right? On Tue, Feb 26, 2013 at 10:43 AM, Ross Bemrose wrote: > The only one that will take any time is moving maps. Based on what's > previously been discussed > > 1. Install the new TF server into a new directory > 2. Move oldserver/orangebox/tf/addons/ to newserver/tf/addons/ > 3. Move oldserver/orangebox/tf/cfg/ to newserver/tf/cfg/ > 4. Sort through the oldserver/orangebox/tf/maps folder for custom maps > and move them to newserver/tf/custom/maps/ (note: /custom is optional > here, but Valve's maps still live in tf/maps/ No sense in keeping > them together if you don't have to) > 5. Harass plugin makers to make VPK files for their models, materials, > and sounds. Or just do it yourself; the vpk binary comes with current > TF2 Beta clients and servers. Note that you'll still need them loose > on the disk on fastdownload servers as it sounds like there are no > plans on making VPKs downloadable that way (although possible Workshop > support was mentioned...) > > On Tue, Feb 26, 2013 at 6:47 AM, Peter Reinhold > wrote: >> Hi all, >> >> Has anyone done a writeup on how you migrate an existing server to the new >> format server? >> >> I did a quick search in the archives, and could not find one, but I might >> have missed a link somewhere. >> >> >> /Peter >> >> ___ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > > > > -- > Ross Bemrose -- Ross Bemrose ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
Re: [hlds_linux] Instructions for migrating an existing TF2 server to beta / new format?
The only one that will take any time is moving maps. Based on what's previously been discussed 1. Install the new TF server into a new directory 2. Move oldserver/orangebox/tf/addons/ to newserver/tf/addons/ 3. Move oldserver/orangebox/tf/cfg/ to newserver/tf/cfg/ 4. Sort through the oldserver/orangebox/tf/maps folder for custom maps and move them to newserver/tf/custom/maps/ (note: /custom is optional here, but Valve's maps still live in tf/maps/ No sense in keeping them together if you don't have to) 5. Harass plugin makers to make VPK files for their models, materials, and sounds. Or just do it yourself; the vpk binary comes with current TF2 Beta clients and servers. Note that you'll still need them loose on the disk on fastdownload servers as it sounds like there are no plans on making VPKs downloadable that way (although possible Workshop support was mentioned...) On Tue, Feb 26, 2013 at 6:47 AM, Peter Reinhold wrote: > Hi all, > > Has anyone done a writeup on how you migrate an existing server to the new > format server? > > I did a quick search in the archives, and could not find one, but I might > have missed a link somewhere. > > > /Peter > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux -- Ross Bemrose ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
Re: [hlds_linux] Instructions for migrating an existing TF2 server to beta / new format?
Based on Fletch's response a few days ago, it appears there is no (automated) migration process for servers. So at the most basic form you'd need to completely reinstall the server, unless you're willing to risk the sideeffects of running VPKs in addition to loose files. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
[hlds_linux] Instructions for migrating an existing TF2 server to beta / new format?
Hi all, Has anyone done a writeup on how you migrate an existing server to the new format server? I did a quick search in the archives, and could not find one, but I might have missed a link somewhere. /Peter ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
