How to Download and Upload Mods to Arma

Contents

• 1 Publishing user content (mods and campaigns)
• 2 User interface
  • two.1 Published items list
  • 2.2 Item Metadata
  • 2.3 Description
  • ii.4 Tags
  • 2.5 Change notes
  • 2.6 Image
  • 2.7 SteamWorks licence
  • 2.8 Publish
  • ii.9 Options
    • 2.9.ane Other buttons
• 3 Boring technical stuff
• 4 Logs
• five Notes

1.24

The purpose of this tools is to publish and manage items in the Steam Workshop. It allows you lot to upload your mods and modify the information that is displayed on their Steam Workshop page. Published mods (and other items) tin can be then subscribed by other players and loaded to the game by Arma 3 Launcher.

The official Publisher was launched July xiv, 2014 with the Bootcamp update 1.24. http://arma3.com/news/bohemia-interactive-deploys-arma-3-bootcamp-update.

Publishing user content (mods and campaigns)

To publish the content to Steam Workshop, yous have to have the modernistic prepared and tested. Commencement with clicking a push "SELECT MOD Folder" and selecting the folder that contains your modern.

Then you should name select the proper noun for it (it should be unique and descriptive for users to place it easily) and select it is type:

• Modern: a game modification, an addon or a new terrain;
• Entrada: a series of connected missions;
• Scenario: simple mission are published directly from Eden Editor and can't be published by Publisher.

Based on the selected item blazon, you tin choose from the multiple tags that are used on Workshop to filter the items. Nosotros recommend to use the tags that the all-time describes your item. Using misleading tags or all tags will outcome in Workshop moderators irresolute them or removal of the unabridged item from Steam Workshop.

If yous're updating the existing item, you should fill the change notes to let your users know what'south new.

Earlier the mods is published or updated on Workshop, the construction check is done to ensure that the modernistic tin can exist loaded past the game.
Following requirements must exist met in society to publish the mod:

• addons folder needs to be directly in the root (pinnacle level) to be loaded in the game;
• addons folder has to contain the PBO files;
• all signatures need to be in the same folder as their respective PBOs.

Publishing a mod with PBO files outside of addons folder (such as an presence of Optional folder) will produce a alert, considering swapping of files in mods acquired through Steam customer is non recommended. ^{[note one]}

User interface

Published items list

Displays your new and published items.

• Unpublished particular: Select this item when you want to publish a new detail in the Workshop.
• Listing of published items: lists all your existing items. Publishing with a selected item on this list will overwrite all data and meta-information on Steam with your local copy. Scenarios published from the game's editor are too listed.
• Search field: allows full-text search in the list
• Web: opens the workshop page of the selected published detail. Not available for the unpublished item.
• Delete: removes the item from the workshop. Use carefully, does not have disengage.

Particular Metadata

• Modernistic content: Drag and drib a file or a binder onto the box. Remove added items by clicking X.
  • Included folders automatically include any files or sub-folders
  • Items tin incorporate multiple files and folders
  • Item size is not express
  • Buttons:
    • Add file, Add together folder: opens windows dialog to select files or folder
    • Clear all - removes all included files and folders from the mod content box
  • Behavior
    • A file or a folder can be included just in one case (based on its path)
    • Files of the same name but different size tin be included even in the same directory, they volition exist enumerated (myMod.pbo; myMod.pbo > myMod.pbo; myMod1.pbo)
    • Tooltip shows the full path and size
    • Including merely one folder will not promote information technology equally root, the input field is the root and will be published equally @name
  • Signatures
    • signatures are required for multiplayer with mods and can be generated in Addon builder [Addon Builder]
    • with a multiple files philosophy, signatures can now be included in the workshop items
    • they should to exist in the aforementioned folder every bit the respective PBO
    • Publisher options now allows auto-including signatures

• Writer: Reads the author specified in the PBO or from Steam
• Proper noun: Name of the Workshop item.
• Size: Size of the item on Steam or a size of the file to be uploaded (yellow color).
  • Displays file and folder count for an detail to be published.
• Published: For existing items only, the original published date.
• Terminal Update: For existing items but, the final update fourth dimension.
• Visibility: There are three options to choose from:
  • Public - visible to anyone, anyone tin can subscribe to your particular
  • Friends - visible just to your Steam friends
  • Private - (Default), visible only to y'all

Clarification

Text field for your description of the published item. Limit: 8000 bytes (~ 8000 characters]

NOTE: If your mod requires other content to run properly (dependency), it is a good practice to listing all the required content here including a links how to get information technology and a proper load order, if necessary.

In addition, required items present in the workshop can exist defined from the folio of your item (Add/Remove Required Items).

Tags

Steam tags used for categorizing content. Expert tags improve content discovery.

Annotation: It's better to tag your content sparsely (with tags from the same category) and utilize your tag to cover the most prominent qualities or elements. More tags = more defoliation for the subscribers.

By Steam category: Information Type - specifies information type.

• Mod - for single or multiple PBOs. Needs to exist loaded on the game start. Content with tag Modern is displayed in Arma 3 Launcher.
• Server - special server blazon addon.

Note: Modern and Scenario tags are mutually exclusive.

Mod Blazon - specifies mod type based on information technology is content

• Animation - modifies animations in game
• Boat - modifies boats in game
• Entrada - several (connected) missions
• Graphic symbol - modifies characters in game
• Equipment - modifies equipment in game
• Helicopter - modifies helicopters in game
• Mechanics - modifies game mechanics, user interface or other similar elements in game (scripts)
• Plane - modifies planes in game
• Audio - modifies sounds or music in game
• Structure - modifies structures (buildings, props) in game
• Terrain - modifies terrains in game
• Tracked - modifies tracked vehicles in game
• Weapon - modifies weapons in game
• Wheeled - modifies wheeled vehicles in games

DLC

• KartsDLC - modernistic recommends owning Karts DLC
• HelicopterDLC - mod recommends owning Helicopter DLC
• MarksmenDLC - mod recommends owning Marksmen DLC

Meta

• Dependency - mod requires other user mods
• Drove - mod created as a part of larger, but non inter-dependent, drove or theme

Review These tags are added automatically past Publisher when corresponding weather are met. They cannot be removed by the user. Their purpose is to make administering workshop easier.

• Tag Review - added when the item has over 7 tags. The aim here is to reduce the number of tags per item to improve discoverability.
• Content Review - added when the item contains a file blazon that could contain malicious content. Included extensions are .exe, .dll, .cmd, .com, .bat, .py, .ps, .jar, .lib, .src.

Change notes

Text field, limited to 8000 bytes (~ 8000 characters). Only relevant when updating an existing item with a PBO.

Note: When updating an item, provide data what changed so that users feel informed.

Image

Previews an included epitome to be visible on Steam Workshop.

• Predefined: provides a selection of existing images roofing primary tags.
• Scan: opens file open dialog. Allowed file types are .jpg, .jpeg, .png, .gif, .bmp. Image is downscaled to 0,95 MB to meet the Steam limit.

SteamWorks licence

Checkbox - Before publishing, each author must explicitly agree with SteamWorks license. The whole text of the license is bachelor online. When agreement was non confirmed, Publisher provides an fault dialog on Publish try.

Publish

Click this button to publish or update your particular with the provided files and/or information.

Note: Publishing handles all the data to the Steam Client and displays the progress window. Yous can track the progress bar, simply exist enlightened that in that location are several steps similar compressing and extracting that are handled past the Steam back-terminate and not communicated over the API - this means the publishing can accept longer even on a solid connectedness.

Options

• Temp binder path: define a temporary binder where mods with multiple files are copied and prepared before their publishing. Provide an absolute path or use [...] to open the Open folder dialog. Contents of the folder is deleted after a successful publishing.
  • Use default: default temporary binder is user documments dir\AppData\Local\Temp e.k. c:\Users\cooper\AppData\Local\Temp\
  • When adding files, a new folder is created in Temp with the Proper name of the mod (example: ...\Temp\MyFirstMod ). When such folder already exists, the new folder cannot be created and publishing fails with fault. Please, remove such folder manually before retrying.

NOTE: copying large or multiple files between drives can accept longer

• Auto-include signatures
  • When a PBO is being added to the modern content, Publisher searches the source binder for a relevant signature (<pbofilename>.<cord>.bisign) and adds it to the modern content. If more than then ane signature files match the condition, all of them are included.
  • When a PBO is being removed from the mod content, Publisher automatically removes the matching signature, if present.
  • Default: on
• Open up workshop page afterwards publishing
  • When publishing is successful, Publisher automatically opens the published item'southward workshop folio. Usable for visual checks and subscribes.
  • Default: on
• Use Steam Customer instead of web browser
  • When opening workshop pages using the Web push button or automatically after publishing, opens the webpage in Steam Customer instead of the default web browser
  • Default: on (Steam Client)

Other buttons

• Bohemia Interactive - opens visitor folio in external spider web browser
• Workshop - open Arma 3 workshop folio in external browser
• Support - open Bohemia Interactive support folio in external browser
• Feedback - opens feedback tracker, Arma 3'due south customs feedback and result tracking service in external web browser

Boring technical stuff

To be processed after

• Publishing process - Exist aware that publishing larger mods tin have up a while. Here is what has to happen:
  • Publisher sends the path to all files and folders in the temp [link] folder to Steam Client
  • Steam Customer athenaeum the files locally into one archive
  • Steam Client uploads to SteamWorks database
  • Workshop stores the information and sends Publishing successful callback
  • Publisher receives the callback and lists the file as published

Logs

Publisher logs tin can be found in steamapps\common\Arma 3 Tools\Logs
When something goes wrong (in several attempts, because Steam can take a bad moment sometimes :) ), please, create an issue on the tracker in Tools category and include these logs.

Notes

1. ↑ Steam is managing the downloaded files and keeps them synchronized with information uploaded to Workshop. If the users move the files, Steam volition revert these changes with next update making the behavior of the mod unpredictable. Too historically this kind of manipulation has broken the Steam and forced re-download of the entire mod.

sandersherat1964.blogspot.com

Source: https://community.bistudio.com/wiki/Arma_3:_Publisher

Share this post