I'm guessing whatever allows access to Arsenal from ammo crates isn't working in dev branch now, for whatever reason. Main menu Arsenal, and use of the Arsenal module work fine, although when you copy paste units changed by Arsenal, they don't keep their changed characteristics.

Problem seems to be solved in the latest version of dev-build.
Ticket can be closed.

Please check again on current dev ver. 1.55.133541. When the arsenal function is executed on a Dedicated server targeting an object that is owned by the server, it does not show up on any clients that approach that object (ammo crate). On a server/client machine it works fine.

Line run on server: 0 = [ "AmmoboxInit",[ hA,true,{ true } ] ] spawn BIS_fnc_arsenal;

Also, using: [ "AmmoboxInit",[ hA,true,{ true } ] ] remoteExec [ "BIS_fnc_arsenal",0 ];
does NOT produce any results either.

"hA" is the name of the crate and the description.ext has been configured to unrestrict remote function execution.

same like here -> http://feedback.arma3.com/view.php?id=26869
You must whitelist all in CfgRemoteExec because og BIS_fnc_mp is now managed over remoteExec or use in CfgRemoteExec the mode = 2, but this open the gates vor script kiddies....

I forgot to add the "NOT" in my comment. My apologies. The above statement has been corrected. My CfgRemoteExec in description.ext is set to mode = 2 and the Bis_fnc_arsenal still does NOT work

This is kind of urgent...

According to the author the issue seems to be resolved.

Should I post a new ticket then?