BTW the only workaround I have at the moment is to continue to generate different keys until I get one that works with the mod combination that was having an issue, and then re-release with the mod signed with that new key.

It seems that the number of dashes (- or _ characters) in the mods have an effect. I'm unable to generate a local key like 'Ares_1_5_0.bikey' or 'Ares-1-5-0.bikey' that avoids the issue. Using 'Ares150.bikey' seems to work tho.

Ignore the 'keys.zip. It's from a messed up upload. Follow instructions in description.

It seems like the '-' theory is busted, I found some more keys that don't work in combination with the newly renamed .bikey file (without the dashes in the name). It has to be something internal to the game since the keys work fine in isolation. For some reason it seems to happen more often with map packs that we try.

I'm not sure if it has something to do with the way the key is generated or something. No matter what, there's an issue in the game where some key combinations hang the server.

It appears the issue isn't always related to the mouse pointer. A JONeill's video shows it can happen even when you don't leave the pointer on an object. Sometimes things work pretty well, sometimes they seem to always stack up. I'm able to repro it 100% when leaving the mouse pointer on top of an object when I release it however (even when it's working normally otherwise).

I think this actually has to do with dragging any objects on top of another. Rotating is fine as long as you don't end with the mouse on another object.

The same thing happens when moving objects. It looks like (maybe?) they added a 'feature' where dragging one object on top of another would snap it to the same position. However, it looks like the snapping code doesn't take into account the current selection (which should be excluded from the 'things to snap to' list, but isn't). This means that when you release the mouse button, if your mouse happens to be over top of ANY other object (even an object in the set of things you are rotating) it stacks EVERYTHING you had selected into that position.

This is crazy annoying - especially since there is no 'undo' feature and you can undo a huge amount of work by having everything collapse into a black hole with one mis-click.

Is this just a case of waiting for some period and then the serverCommandAvailable function works to detect if you're an admin again, or does it have to be called from a UI handler?

I'm trying to work around http://feedback.arma3.com/view.php?id=21163 by detecting if the unit is an admin in script without any UI necessary and only allowing Zeus in that case - I was planning to do use the serverCommandAvailable command to detect admins (of any type) by whether they could #kick.

Is there a pure-script workaround for this?

Better version of example.

Also it appears you cannot load a saved Virtual Arsenal loadout that contains a composite weapon even if that weapon is in the box.