Previously, addons were made by making folders and putting an info.txt inside, this is not needed anymore.
You create a folder with the content (an addon folder reflects the same structure as the game folder itself) and put that into our workshop tool. This tool now generates a VPK file out of that folder and uploads that file with the metadata you provided in the tool to the workshop where it'll be immediately available. Afterwards the tool sends you to the addon's workshop page so that you can edit it further if you want.

• An addon should serve one purpose, so if you for example have a bunch of models: create an addon for each, and not a pack, that's what a collection is for. (The Dev Team might overrule this by creating addons that contain selected models put inside into one for better performance)
  
• addons of the type "map" can consist of a map file (.bsp) with it's content packed inside, or it's content laid out inside the addon folder as this addon is only looked at if the map is running.
  
• addons of the type "playermodel" should as mentioned above, only contain content related to one model, this is to give the end-user a better choice of what they want to have and not waste their bandwidth on something they don't like.

We will make sure that these rules are being followed, for that reason everyone can subscribe to any addon, but only accepted ones will be used by the game.