Really? Oh, heh, I should've paid attention to the specs more... now I remember...
The third long in the Actions part of a trigger is the string ID for the sound.
Thanks for the reminder, Heim

Does this mean that technically, the "WAV " section is not even required for Starcraft, and that it's only a waste of space in everyone's map to just make it a little easier on StarEdit identifying wav strings?
EDIT: I successfully removed the entire "WAV " section from a working map. Starcraft loaded it with no trouble whatsoever, StarEdit, SCXE, and SCMDraft choked on it and refused to open it, whilst StarForge opened it like a breeze.
UED77
[right][snapback]263195[/snapback][/right]
you probably triggered some aspect of protection detection then.