I am glad you solved it. There are some good reasons to use the built-in compiler in TrenchBroom as well. It takes a bit of setup which you can read about more here:

https://github.com/4LT/tb-compile-guide/blob/main/README.md

I personally use q1compile https://github.com/glhrmfrts/q1compile/releases

video here:https://youtu.be/IAhoxXGLce8?si=zEhZvMMaJQns01sm

Lots of options but at least you have it working now necros' GUI is still great! 

What causes a map to have issues such as having the wind sound being heard underwater?

And what causes grenades to bounce off the sky? 

I did some eyeballing and calculations...

Quake unit to meters is a factor of ~20

eg
1000 u = 50m 

Not sure if I need to post here or on "Coding help", I hope it's ok in mapping help.
I have the following:
-1 trigger_counter with target "mdt", targetname "zt", count 3
-1 trigger_relay with target "ds13", targename "mdt", message "Door Unlocked", delay "2"
-3 monster_zombie, each one has target "zt"
-1 door with targetname "ds13", message "Lockdown"

This entire setup works, with some small (but very annoying) problems.
When I try to open the door, the message "Lockdown" is shown, that's perfect.
When I kill a zombie with my weapon (quad shotgun or rocket launcher for example), the message "Only x more to go..." appear.
When all 3 zombies are dead, "Sequence completed" is shown, then, after 2 seconds the message "Door Unlocked" appears and the door ds13 is opened.

My first problem is that if I kill the zombies with a machine (for example a func_door that will crush the zombie), the message "Only x more to go..." doesn't appear.
Even worse, in the end, when the last zombie is killed by crushing it, "Sequence completed" doesn't appear, and also "Door Unlocked" doesn't appear, but (this is nice) the door unlocks.
Why doesn't the messages appear, and what can I do?

The second problem - after the door is opened it stays opened, is there a way to make it close, but be "unlocked"?