How to Upload a Dow 3 Map How to Upload to Steam Workshop

1 Publishing user content (mods and campaigns)
2 User interface
- ii.1 Published items list
- ii.two Item Metadata
- 2.iii Description
- two.iv Tags
- ii.5 Change notes
- 2.vi Image
- 2.7 SteamWorks licence
- two.8 Publish
- 2.9 Options
  - 2.9.1 Other buttons
3 Ho-hum technical stuff
4 Logs
5 Notes

1.24

The purpose of this tools is to publish and manage items in the Steam Workshop. Information technology allows you to upload your mods and change the information that is displayed on their Steam Workshop page. Published mods (and other items) tin exist so subscribed past other players and loaded to the game by Arma 3 Launcher.

The official Publisher was launched July 14, 2014 with the Bootcamp update ane.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, you lot have to have the mod prepared and tested. Kickoff with clicking a button "SELECT MOD FOLDER" and selecting the folder that contains your mod.

Then y'all should name select the name for it (it should be unique and descriptive for users to place it easily) and select it is type:

Mod: a game modification, an addon or a new terrain;
Campaign: a series of continued missions;
Scenario: elementary mission are published directly from Eden Editor and can't be published past Publisher.

Based on the selected detail type, y'all can choose from the multiple tags that are used on Workshop to filter the items. Nosotros recommend to use the tags that the best describes your item. Using misleading tags or all tags will consequence in Workshop moderators changing them or removal of the entire detail from Steam Workshop.

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

Before the mods is published or updated on Workshop, the structure check is done to ensure that the modern tin can be loaded past the game.
Following requirements must exist met in guild to publish the mod:

addons folder needs to exist straight in the root (top level) to be loaded in the game;
addons binder has to incorporate the PBO files;
all signatures demand to be in the same binder every bit their respective PBOs.

Publishing a mod with PBO files outside of addons folder (such as an presence of Optional folder) will produce a warning, because swapping of files in mods acquired through Steam client is non recommended. ^{[annotation 1]}

User interface

Published items list

Displays your new and published items.

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

Detail Metadata

Mod content: Drag and drib a file or a folder onto the box. Remove added items by clicking X.
- Included folders automatically include any files or sub-folders
- Items can contain multiple files and folders
- Particular size is not limited
- Buttons:
  - Add file, Add 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 binder can be included only once (based on its path)
  - Files of the same name but different size can exist included even in the same directory, they will be enumerated (myMod.pbo; myMod.pbo > myMod.pbo; myMod1.pbo)
  - Tooltip shows the full path and size
  - Including but 1 binder volition not promote it every bit 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 architect [Addon Architect]
  - with a multiple files philosophy, signatures tin can at present be included in the workshop items
  - they should to be in the same folder every bit the respective PBO
  - Publisher options now allows auto-including signatures

Author: Reads the author specified in the PBO or from Steam
Name: Name of the Workshop detail.
Size: Size of the item on Steam or a size of the file to exist uploaded (xanthous color).
- Displays file and folder count for an item to be published.
Published: For existing items but, the original published engagement.
Last Update: For existing items merely, the final update time.
Visibility: There are three options to cull from:
- Public - visible to anyone, anyone can subscribe to your item
- Friends - visible only to your Steam friends
- Individual - (Default), visible just to you

Description

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

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

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

Modify notes

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

Annotation: When updating an item, provide data what changed so that users experience informed.

Prototype

Previews an included image to be visible on Steam Workshop.

Predefined: provides a selection of existing images covering principal tags.
Browse: opens file open dialog. Allowed file types are .jpg, .jpeg, .png, .gif, .bmp. Epitome is downscaled to 0,95 MB to see the Steam limit.

SteamWorks licence

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

Publish

Click this button to publish or update your item with the provided files and/or data.

Note: Publishing handles all the data to the Steam Client and displays the progress window. Yous can rail the progress bar, merely be aware that in that location are several steps like compressing and extracting that are handled by the Steam back-end and non communicated over the API - this means the publishing can take longer even on a solid connexion.

Options

Temp folder path: define a temporary folder where mods with multiple files are copied and prepared before their publishing. Provide an accented path or apply [...] to open the Open up binder dialog. Contents of the binder is deleted later on a successful publishing.
- Use default: default temporary folder is user documments dir\AppData\Local\Temp due east.g. c:\Users\cooper\AppData\Local\Temp\
- When adding files, a new binder is created in Temp with the Name of the mod (case: ...\Temp\MyFirstMod ). When such folder already exists, the new folder cannot be created and publishing fails with error. Delight, remove such folder manually earlier retrying.

NOTE: copying big or multiple files between drives tin can take longer

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

Other buttons

Bohemia Interactive - opens visitor page in external web browser
Workshop - open Arma 3 workshop page in external browser
Support - open Bohemia Interactive support page in external browser
Feedback - opens feedback tracker, Arma 3'southward community feedback and event tracking service in external web browser

Boring technical stuff

To be processed later on

Publishing process - Be aware that publishing larger mods tin take upward a while. Here is what has to happen:
- Publisher sends the path to all files and folders in the temp [link] binder to Steam Client
- Steam Client archives 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 can be found in steamapps\common\Arma 3 Tools\Logs
When something goes wrong (in several attempts, considering Steam can have a bad moment sometimes :) ), please, create an issue on the tracker in Tools category and include these logs.

Notes

↑ Steam is managing the downloaded files and keeps them synchronized with data uploaded to Workshop. If the users move the files, Steam will revert these changes with next update making the beliefs of the mod unpredictable. As well historically this kind of manipulation has broken the Steam and forced re-download of the entire modernistic.

pigottwousay.blogspot.com

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

Pigot Twousay