It is possible to map for tf2 after steampipe if you're prepared. We don't know when the new tools will be ready but if you want to be mapping in the meantime, this is how.
Here are the files you are required to backup for hammer to work after conversion:
- Steam\SteamApps\userfolder\team fortress 2\tf\gameinfo.txt
- Steam\SteamApps\team fortress 2 client content.gcf
- Steam\SteamApps\team fortress 2 content.gcf
- Steam\SteamApps\team fortress 2 materials.gcf
Here are optional folders related to mapping that you might want to back:
- SteamApps\userfolder\Team Fortress 2\tf\maps
- SteamApps\userfolder\Team Fortress 2\tf\materials
- SteamApps\userfolder\Team Fortress 2\tf\scripts
- SteamApps\userfolder\Team Fortress 2\tf\resource
- SteamApps\userfolder\Team Fortress 2\tf\sound
...
(These folders should not be deleted by steampipe but you're never too safe (only the content of the tf folder, not the gcfs, you have to back those). the content of your tf folder is supposed to be available in the SteamApps\common\Team Fortress 2\tf\download folder after conversion)
you may now convert your game to steampipe!
Now that you've been steampiped, first thing you want to do is put all 3 gcfs back at their original location in Steam\SteamApps. Next you want to take your old gameinfo.txt and place it back where it belongs in Steam\SteamApps\userfolder\team fortress 2\tf.
and that's it. There's nothing else to it. hammer is ready to launch!
Now we need to discuss some of the implications of this.
We've gone dark
You can still map for tf2 because we still have the old GCFs that hammer is able to deal with. however, these gcfs will never be updated by valve ever again. this means that our game content files will be outdated sooner or later. when valve will add assets to the game later in future updates, they will not be available straight away in hammer. this is not a huge problem, we'll figure that out once we get there but from now on, we're on our own when it comes to keeping our tools updated.
Compiling maps
Compiling still works fine but we're going to need to adjust our workflow. Just as before, the compiler will drop your BSPs into steamapps\userfolder\team fortress 2\tf\maps (you will need to rebuild this path before compiling). Unfortunately, the tf2 client cannot load maps in this folder anymore so you need to move your compiled maps to the new maps folder. If I am not mistaken, I think valve advises placing them in SteamApps\common\Team Fortress 2\tf\download\maps. I have not messed around with the expert compiler but with some tinkering you should be able to set the bsp output folder to the new maps directory.
custom content
So since the tf2 client and hammer now use 2 seperate folders to collect assets from, you will need to store custom assets in 2 seperate folders at a time. If we take the models folder for example, for assets to be available in hammer you will need them to be in the good old SteamApps\userfolder\team fortress 2\tf\models folder. For the tf2 client to be able to load the same assets you will need the models to be in SteamApps\common\Team Fortress 2\tf\download\models as well. and paking should still work as it used to so there you go.
that about covers it all. I'll update as I find out more relevant information about steampipe
Here are the files you are required to backup for hammer to work after conversion:
- Steam\SteamApps\userfolder\team fortress 2\tf\gameinfo.txt
- Steam\SteamApps\team fortress 2 client content.gcf
- Steam\SteamApps\team fortress 2 content.gcf
- Steam\SteamApps\team fortress 2 materials.gcf
Here are optional folders related to mapping that you might want to back:
- SteamApps\userfolder\Team Fortress 2\tf\maps
- SteamApps\userfolder\Team Fortress 2\tf\materials
- SteamApps\userfolder\Team Fortress 2\tf\scripts
- SteamApps\userfolder\Team Fortress 2\tf\resource
- SteamApps\userfolder\Team Fortress 2\tf\sound
...
(These folders should not be deleted by steampipe but you're never too safe (only the content of the tf folder, not the gcfs, you have to back those). the content of your tf folder is supposed to be available in the SteamApps\common\Team Fortress 2\tf\download folder after conversion)
you may now convert your game to steampipe!
Now that you've been steampiped, first thing you want to do is put all 3 gcfs back at their original location in Steam\SteamApps. Next you want to take your old gameinfo.txt and place it back where it belongs in Steam\SteamApps\userfolder\team fortress 2\tf.
and that's it. There's nothing else to it. hammer is ready to launch!
Now we need to discuss some of the implications of this.
We've gone dark
You can still map for tf2 because we still have the old GCFs that hammer is able to deal with. however, these gcfs will never be updated by valve ever again. this means that our game content files will be outdated sooner or later. when valve will add assets to the game later in future updates, they will not be available straight away in hammer. this is not a huge problem, we'll figure that out once we get there but from now on, we're on our own when it comes to keeping our tools updated.
Compiling maps
Compiling still works fine but we're going to need to adjust our workflow. Just as before, the compiler will drop your BSPs into steamapps\userfolder\team fortress 2\tf\maps (you will need to rebuild this path before compiling). Unfortunately, the tf2 client cannot load maps in this folder anymore so you need to move your compiled maps to the new maps folder. If I am not mistaken, I think valve advises placing them in SteamApps\common\Team Fortress 2\tf\download\maps. I have not messed around with the expert compiler but with some tinkering you should be able to set the bsp output folder to the new maps directory.
custom content
So since the tf2 client and hammer now use 2 seperate folders to collect assets from, you will need to store custom assets in 2 seperate folders at a time. If we take the models folder for example, for assets to be available in hammer you will need them to be in the good old SteamApps\userfolder\team fortress 2\tf\models folder. For the tf2 client to be able to load the same assets you will need the models to be in SteamApps\common\Team Fortress 2\tf\download\models as well. and paking should still work as it used to so there you go.
that about covers it all. I'll update as I find out more relevant information about steampipe
Last edited: