I agree. For testing at TF2maps it's best to keep on using version numbers and hosting the maps locally, here on our servers. Hosting the maps on the workshop would require someone to do a tf_workshop_map_sync on the servers, and add the map to the rotation file for each new version, but someone could perhaps write some scripts to automate it. Clients would have two copies of each version of your map, but the new BSP compression is very good.
Due to the way the workshop works, you might cause problems for server operators if you use different file names. Maps will update automatically when the server changes level. But the server's map list will still point to the old version of the map. The workshop won't send old versions of maps, and they won't be downloaded from the server because TF2 insists on contacting the workshop for any map that has a workshop/ path prefix. Players will get a missing map error and will be booted off. This will happen to every server, the moment you update your map, and it will not be fixed until server operators realise the change and alter their map lists.
The whole point of the workshop from the point of view of a server operator, aside from making the FastDL server redundant, is that it takes care of map updates. They don't have to bother checking every map in their rotation for updates any more, they can let the workshop take care of it for them. But this system is broken if a map author uses a different file name. If a server operator finds this behaviour annoying because it loses him traffic, he might be inclined to remove a map from his rotation until it arrives at a final, or stable release.
The workshop will be what Valve use to earmark maps for inclusion in to the game. Server operators play a vital role in this system, it's not just about the mappers. Server ops will be browsing the workshop for popular maps to put on their servers, and you can support them by keeping the file names the same. If you are concerned about the time relevance of feedback you receive in the comments on your map's workshop page, remember that if you stick to the same name, the player is most likely to have played the current version at the time he posts his thoughts. There is a section on the workshop map pages where you can post changelogs, so you can easily compare these dates with the dates that the feedback was submitted.
It's probably best to version the maps you release on normal channels like here on the forum and Game Banana, and keep your workshop maps the same filename.
Due to the way the workshop works, you might cause problems for server operators if you use different file names. Maps will update automatically when the server changes level. But the server's map list will still point to the old version of the map. The workshop won't send old versions of maps, and they won't be downloaded from the server because TF2 insists on contacting the workshop for any map that has a workshop/ path prefix. Players will get a missing map error and will be booted off. This will happen to every server, the moment you update your map, and it will not be fixed until server operators realise the change and alter their map lists.
The whole point of the workshop from the point of view of a server operator, aside from making the FastDL server redundant, is that it takes care of map updates. They don't have to bother checking every map in their rotation for updates any more, they can let the workshop take care of it for them. But this system is broken if a map author uses a different file name. If a server operator finds this behaviour annoying because it loses him traffic, he might be inclined to remove a map from his rotation until it arrives at a final, or stable release.
The workshop will be what Valve use to earmark maps for inclusion in to the game. Server operators play a vital role in this system, it's not just about the mappers. Server ops will be browsing the workshop for popular maps to put on their servers, and you can support them by keeping the file names the same. If you are concerned about the time relevance of feedback you receive in the comments on your map's workshop page, remember that if you stick to the same name, the player is most likely to have played the current version at the time he posts his thoughts. There is a section on the workshop map pages where you can post changelogs, so you can easily compare these dates with the dates that the feedback was submitted.
It's probably best to version the maps you release on normal channels like here on the forum and Game Banana, and keep your workshop maps the same filename.
Last edited: