It protects your map form anyone to open. Even if I do use that option, it still increases my map size.
Not simple english to me.
No since they will be in exactly the same state before you do this as after and the optimizer will still mangle them because software is dumb (well it is only as smart as the people who program it sadly and it seems Vexorian forgot .wav files need special handling).
You could try Audacity. Not sure it can produce WC3 compatible MP3s as personally I have never tried it but a glance at the feature list shows ability to import and export (with a plugin downloaded separately) in the appropriate formats. People usually avoid putting sounds into maps because they take up too much file space.
So they are still larger after the map is put through the optimizer than before? This would make no sense as MP3s cannot be compressed anyway.
That is because most of the data is already in a highly compressed form. It cannot be made much smaller, even with slightly better compression algorithms.
I have never heard of this problem in WC3 before. In what way are they required for the functioning of the script? Does the thread crash without them? As far as I was aware sounds were not deterministic so did not alter trigger operation at all next to some handle creations.
Or remove content. Those are your only options. You should never have designed the map to depend on so many resources in the first place as the 8 MB map file size limit is well known in every mapping community and has been around for years. Be lucky they raised it a couple of years ago as before then it was only 4 MB (half the current limit).
WC3 can have at most 16 terrain tiles. Not 100s.
The models themselves usually are not the problem. It is any custom textures they use and sound as that often contains far more information. Also direct WoW port models are excessively large as they were never designed with space constraints in mind which is why people re-master them for WC3 by reducing their geometry, making them share textures which are already in game and cutting out pointless animations.
We are telling you the solution. You need to either cut content or substitute content which is more space efficient. Using models with in game textures instead of custom textures saves a ton of space. Using no WoW imported models and only using WC3 optimized models saves a ton of space. Converting all sounds to highly compressed MP3 or preferably using as few sounds as possible saves a ton of space.
Easiest way is Fourier Transform it into frequency domain, cut out all frequencies past 8KHz (make the nyquist frequency 8KHz) and then transform back into time domain with inverse Fourier transform. The result is that of a perfect filter so there is no need for anti-aliasing filter bandwidth.
Well WoW models are not an option then as they look far too modern for WC3. Also there is a huge difference between the 800 MB Blizzard had for content and the 8 MB you have.
You need to delete geometry (and/or animations) from it. Unless you have experience with modelling this can be very difficult to do and in any case will take quite a few hours of time.
