Stim File Archive ((top)) -

Do not leave files loose. Bundle each Stim file and its dependencies into a read-only container. Two excellent options:

A complete Stim archive should include these core file types to ensure the content is usable by others: stim file archive

Use a script to parse the binary header of each Stim file. Look for relative paths (e.g., ..\sounds\beep.wav ) or hardcoded resource IDs. For each dependency found, copy that referenced file into a subfolder named [stim_filename]_deps . Do not leave files loose