Unlike most Source SDK 2013 engine branch mods/games, Obsidian Conflict uses an "add-ons" folder, instead of "custom". The reasons for this are numerous, and outside the scope of this guide.

It provides the same functions as add-ons placed on the custom folder in SDK 2013, but with the following caveats:

• VPKs aren't supported
  
• Each add-on requires an info.txt file in order to be loaded, as it controls several options that addons uses

An example of an info.txt is like so:

If your add-on is supposed to override content, change "override" to "true".
You don't need to have "dependencies" if your addon doesn't require them in order to work.

For Workshop add-ons, their file structure follows as with other Source games / mods.
The info.txt file isn't required, as their settings are controlled by other means instead.

For the time being, you will need to use this Crowbar prototype, in order to upload content into our Workshop:

With this version of Crowbar open, head to the "Publish" tab and select at "Game", "Obsidian Conflict", then follow the next steps:

• Under the table list of addons, you will see at left "Add Item". Press it
  
• In the "Content" tab, proceed to fill up all the needed fields and options
  
• At the "Tags" tab, make sure you check the right ones, as it will help later people searching the addon
  
• In "Options" tab, if your add-on overrides content, check their checkbox. Likewise, if your add-on requires mounts to be played with, check the mounts needed
  
  NOTE: DO NOT CHECK "HL2". This was an oversight while suggesting options, and Zeqmacaw has been notified for a corrected version later on release.
• Add a version number. "1.0.0" does the job for an initial release

Once you are all set, press "Publish" at the "Content" tab, to upload the add-on into Workshop.
And done! You might need to tweak later your add-on at the Workshop settings, but the main work is completed and ready to be suscribed and used in game.