🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
It's time for the first HD Modeling Contest of 2024. Join the theme discussion for Hive's HD Modeling Contest #6! Click here to post your idea!
Okay, to solve this question once and for all. BY protecting your maps that you used in a campaign, it will also protect the campaign itself because when opening campaign, it is the maps being opened.
The MPQ part can contain the following files:
(listfile)
(signature)
(attributes)
war3campaign.w3u
war3campaign.w3t
war3campaign.w3a
war3campaign.w3b
war3campaign.w3d
war3campaign.w3q
war3campaign.w3f
war3campaign.imp
war3campaignImported\*.*
Campaigns have little extra information. You may delete the .imp file. I do not think to slk transformed object editor data will be additive with slks in the individual map file. Besides those two things, there's only alternating the packaging. But yeah, what would be the merit of protecting this rudimentary data?
Okay, one additional thing would be the campaign-spanning imports if you care for that.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.