DayZ Animation Pipeline

Produce and modify DayZ animations end to end. DayZ has two parallel animation systems, and the single most common failure is conflating them. This skill keeps them straight, tells you exactly which parts run where, and refuses to confabulate the reverse-engineered formats.

Dependencies

# py3d = DayZ fork of the pack, >= 1.6.0 (sealed wheel vendored in this skill).
# NEVER `pip install py3d` (PyPI = point-cloud lib) NOR git+upstream (without guards).
command -v python3 >/dev/null 2>&1 || { echo "ABORT: python3 is required to install the sealed DayZ py3d wheel" >&2; exit 1; }; python3 scripts/install_py3d.py
python3 -c "import py3d; assert getattr(py3d,'IS_DAYZ_FORK',False) and tuple(map(int,py3d.__version__.split('.')))>=(1,6,0), (py3d.__version__, py3d.__file__)"

Only the .p3d scripts need py3d; the SEAnim/RTM writers are pure Python. The assert is not decoration: without it a wrong py3d installs silently and every geometry read returns plausible garbage.

The seam: what runs in the sandbox vs what needs Windows/GUI (anchor 1)