Users reporting the same issue on Steam, but with different Workshop item. The only solution is apparently to unsubscribe from ALL Arma 3 Workshop items - rather inconvienient with the amount of modded content used with the game.

It seeemed so to me as well, but apparently it's not so clear cut.

Agreed, however note that some of the duplicate objects come from other DLCs - example being Land_MobileRadar_01_Radar_F which is part of Contact DLC. Quite obviously, DLC objects should retain their duplicates, so that people won't need to buy other DLCs to play SOG:PF.

Stoner 63 in SOG:PF is in rifle configuration that's bottom fed from 30 round magazines and fires from closed bolt (XM22/XM22E1). The 150rd "drum" used in LMG/Commando Stoner 63 (XM207 and Mk 23 Mod 0) was actually a container for ammo belt. Since rifle configuration can't feed from the belt, the whole gun has to be converted from one configuration to another - LMG feeds from side, and fires from open bolt. Convertion can be done in field, but requires a whole lot of additional parts - that's why US military (including USN SEAL teams) issued the guns in specific configurations (XM22 rifle, XM23 carbine, XM207 LMG and Mk 23 Mod 0 Commando), and not as a "DIY kit".

Note: I'm not a dev.

I've found out that head is showing full damage (red colour) - however I haven't seen it showing minor damage (yellow). Task description edited accordingly.

In T147399#2002143, @BIS_fnc_KK wrote:

When you are publishing to workshop you are providing a picture separately AFAIK so what exactly is wrong with showing picture you uploaded to the workshop together with description you have given on the workshop (...) How is that conspiracy against the humanity by evil BI devs?

In T147399#2001916, @BIS_fnc_KK wrote:

If you put mission folder in Missions, it shows fine

A workaround for this issue would be ability to publish scenarios via Publisher tool, not Eden Editor. However, it's impossible for community content creators, as Publisher tool doesn't even have scenario tag option. Apparently it's not a problem for BIS developers, since Old Man is properly tagged as a scenario.