• 🏆 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!

Idea

Status
Not open for further replies.
Level 26
Joined
Aug 18, 2009
Messages
4,097
I have organized files including imports on the file system. You can use those path tree as an indicator or drop additional information in the specific directory. Wc3 expects to have some resources on fixed paths, which makes it kinda mandatory then. Everything is pulled in via compiler. That's fairly easy to do using postproc and libs for example. You do not even necessarily have to adjust the .imp file if you do not need to have it shown up in import manager and repeat the process every save.
 

Dr Super Good

Spell Reviewer
Level 64
Joined
Jan 18, 2005
Messages
27,198
In theory any old MPQ editor should work, such as MPQEdit. The problem is it seems WorldEdit somewhere stores a list of all imports, which the MPQ editor will not modify. As such when you open the map in World Edit after importing with MPQ Editor it will load all the imports, but fail to show them in the import manager and fail to retain them when saving.

If one could find the file which retains the import list, or how the import list is generated, then one could create a hybrid MPQ editor which updates the import list so that imports appear in World Edit correctly.

If you are going third party editor then one might as well use a flat directory structure and archive it all only on build. This is what the StarCraft II editor does with its map components save format. Imports then can be managed effortlessly from the file system and do not even need any special handling or inclusion instructions.
 
Status
Not open for further replies.
Top