Sure! Easy but there are some new functionalities coming with the launcher, BattleEye and the way the addons are managed on Steam.
First, Launcher has taken the control of the game, checking plenty of updates prior to launch game. Why not?
But there is no more possibility to test easily an addon project. You need to upload a private version of it. It's heavy!
More! if Arma is launched via the launcher, you can't choose extensions in the config menu (no access to enable/disable extensions)
Second, the Publisher is always this non-coherent, messy tools, trying to fix folders and adding weird legacy.bin???
Is there anybody to explain clearly what/where/when folders or files should be present to have a coherent addon?
AIM IS SIMPLE: a pbo in "addons" subfolder of @myAddon , a bikey in "keys" subfolder, a bisign probably in "addons" subfolder (not sure it's the good place), and, if you please, cherry on cake, a pdf or doc or txt file for easy finding documentation in an "Idontknowwhatwhere" subfolder (or directly in @myaddons).
I never success to do this simple thing. If you do it yourself in Arma3 folder, be sure next time you launch via Steam launcher, the mess wiil be back.
Trying to publish leads to a "fix it" proposal for a missing or incorrect path addons folder (what root??). But addon works... Is it serious?
Recently, using launcher leads to a systematic error for a bisign key test failed on addons which had no problem since then... But addons work... once again seriously?
Subsidiary question: Still how many versions of Publisher to obtain a simple efficient tool ???