However, the corresponding trigger actions for playing a wav file (http://www.staredit.net/wiki/index.php/Scenario.chk#Trigger_Actions_List) like 8 = Play WAV(Wav, WavTime) expect a duration of milliseconds for the WAV file to be played.
In the default GUI map editor, you can't normally choose a time, and instead it looks like the map editor implicitly gathers the millisecond duration of the file and adds it into the trigger action behind the scenes.
This is unfortunate, because it means to allow creating triggers related to WAV files, you have to have access to full MPQ archive in order to find out the WAV durations.
Am I wrong? Is the WAV duration stored somewhere else in the CHK sections? Would it be hacky to create an extra section in the CHK to store WAV file metadata like duration (or use an not commonly used section)?
Does anyone have insight into the design reasoning of this choice by Blizzard?
None.
does it feel weird tho
