Jump to content

Recommended Posts

Arma 3 Publisher on development branch has been updated to version 1.5.138025

 

What is new?

 

Tag selection UI has been updated and item types are now clearly separated

The tag overhaul has begun and as a first step we've updated the user interface to separate the item types. For now we have two types: Mod and Campaign that match the existing tags on Steam Workshop. The major change is that Campaign type will allow you to select scenario related tags: scenario type, game play type and map.

In the future we want to move further down the rabbit hole, create more separate categories, update existing tags and clean up Steam Workshop.

 

Mods with an invalid mod structure can no longer be published

From now on Publisher won't allow you to publish mods that do not meet the basic requirements for Arma 3 mods (like not having *.pbo files in Addons folder) at all. You will now see the warning/error when you update the mod content in Publisher, but you have to fix all errors to publish the item.

The automatic fix for invalid mod structure was removed and will be replaced with a set of new features in the future. Now you have to prepare a mod with valid structure to publish it to Steam Workshop yourself. 

 

Fix for Steam error code 9 when publishing

You might have encountered error 'Steam error 9' when publishing your mods. That might happen when the publishing process took too long and the item was removed by a background clean-up process that removes forgotten zombie items after failed publishing. This is now fixed.

 

Also an Armilion (or two) of smaller improvements and fixes...

 

BvdUGXs.png

  • Like 2

Share this post


Link to post
Share on other sites

please document in the BIKI in technical terms (aka very specific) what these are:

> basic requirements for Arma 3 mods

and

> invalid mod structure

quite helpful would be an overview what is different (new, changed, removed) when you try to update a mod.

with large mods right now you can only select the modfolder and hope you didnt mess up somehow.

therefore an overview to double check before the files get uploaded would be very helpful.

probably as option/optional as for simple mods/missions probably not needed

Share this post


Link to post
Share on other sites

please document in the BIKI in technical terms (aka very specific) what these are:

> basic requirements for Arma 3 mods

and

> invalid mod structure

 

They're already on https://community.bistudio.com/wiki/Arma_3_Publisher. The documentation will be updated (or entirely reworked as I look at the state of it) to reflect the recent changes soonTM  :icon_twisted:

 

quite helpful would be an overview what is different (new, changed, removed) when you try to update a mod.

with large mods right now you can only select the modfolder and hope you didnt mess up somehow.

therefore an overview to double check before the files get uploaded would be very helpful.

 
I'm afraid that this can't be done as we no longer have that information as it is now hidden inside Steam publishing process. We could fake it to a some degree, but you'd have to have the mod subscribed at the same time and it still might be inaccurate.

Share this post


Link to post
Share on other sites

Arma 3 Publisher on development branch has received the X-Mas Update!

 

DbMEou7.png

 

What is new?

 

Detection and check of game extensions

Arma 3 engine capabilities can be extended through the game extensions. In short the game extensions are stored in dynamically linked libraries (or DLLs) and called from in-game scripts, missions and mods by the name of the file. With the introduction of the 64-bit game version, the matter complicates a bit: on Windows, the DLL can be only 32-bit or 64-bit, nor both at once, and the program (the game) can only load the matching DLLs (so the 32-bit game can use only 32-bit DLLs, 64-bit game only 64-bit DLLs). In short: 64-bit game can't load 32-bit extensions and vice versa.

 

So how are 64-bit extensions going to work?

The call of the extension from SQF will remain the same. So far the extension was called from scripts by the DLLs name (without the .dll extension), that remains the same for 32-bit game. For 64-bit game, the extension has to the file with suffix _x64 (e.g. MyExtension_x64.dll). That will allow you to have both 32-bit and 64-bit DLLs for one game extension.

 

How this relates to Publisher?

Publisher will check the DLLs in the mod and mark its compatibility with 32-bit and 64-bit version accordingly. It will also prevent the upload of corrupted DLLs.

There rules these:

  • If no game extension is present, the mod is not marked - thus compatible with both game versions automatically.
  • If only 32-bit game extensions or 64-bit game extensions are present, the mod is marked with the respective version.
  • If both 32-bit and 64-bit game extensions are present, Publisher expects them to be in pairs (for every extension.dll there must be extension_x64.dll) to be marked as compatible with both game versions.
  • To promote mods that support 64-bit game, they will be marked with a new Workshop tag.
  • The DLLs, that are not the game extensions, won't be considered in the check. So your game extension can use any 3rd party DLLs without being bound by these rules.
  • Also any DLLs is expected to be a valid DLL and the bitness to match the extension name (e.g. 32-bit DLL named MyExtension_x64.dll is not allowed).

 

Detection and validation of mod signatures

Publisher will now check the PBO signatures (.bisign files) in the mod. It will warn you, if the signature files doesn't match the PBOs or you're missing some. Publisher will also prevent you from uploading the mod with corrupted signatures to Steam Workshop.

 

Extended metadata for Arma 3 Launcher

Both changes in the game extensions detection and signatures detection will reflect in Arma 3 Launcher and in its server browser. We aim to provide the users with better information when they are downloading the mods (whether it will be compatible with the mods they already have - before they download the it) and to improve detection of matching mods (by utilizing signatures even more).

 

Social links

You can now edit a social media links that appears on the Steam Workshop page directly from Publisher.

 

Formatting toolbar

Description text box has now a toolbar that allows you to add Steam formatting markup - you can create headings, emphasize text or insert links to other web sites.

 

 

If you find any issue with new version of the Publisher, please report an issue on our Feedback Tracker or contact me directly here on forum.

Edited by BIS_Wizard
Added screenshot. Added description for additional new features.
  • Like 4

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×