Version: DayZ Server 1.30 (PC, Windows), offline CE mission dayzOffline.chernarusplus. Mods: @CF and @VPPAdminTools only. Nothing that touches CE or loot.
A <proxy> inside a <dispatch> in mapgroupproto.xml places its item correctly relative to the parent object only when the third rpy value is exactly 0. With any non-zero third value, even 0.002, the item's rotation no longer follows the parent. The parent's yaw is added to the item's pitch, so the same proxy comes out tilted differently on each parent instance. Proxy positions are unaffected and stay correct.
Expected: each pot sits upright, with its yaw equal to its table's yaw: (45, 0, 0) and (-110, 0, 0).
Actual: with a non-zero third value, each pot's world orientation is roughly (yaw = proxy middle value, pitch = -first value - table yaw, roll ~ third value). It ignores the table's yaw and tilts by it instead. With the third value at exactly 0, both pots are correct.
Measured on two tables, items logged by server script (GetOrientation, WorldToModel):
Proxy rpy -0.002 -0.009 -0.002 (Pot): table yaw 45 -> item ori (-0.011, -44.998, 0.003); table yaw -110 -> (179.986, 69.998, 179.994), i.e. pitch 110
Proxy rpy -90.002 2.174 -0.003 (Mackerel): table yaw 45 -> (2.177, 45.002, 0.004); table yaw -110 -> pitch -159.998
Proxy rpy 0 -0.009 0 (Pot): correct, table-relative for both
Proxy rpy 89.27 -90.97 0 (KitchenKnife): correct for both
Proxy positions were correct to under 1 mm in every case.
Workaround: keep the third rpy value exactly 0. Items that need a real roll, such as a fishing rod lying on its side, can't be posed correctly.