[Import] Map saved as folder breaks import paths?

Status
Not open for further replies.
Level 5
Joined
Aug 15, 2012
Messages
139
v1.31.1.12164 (Classic)

I've saved my map as a folder.

1619292597358.png


Normal:
1619292704050.png


Menu on (F10):
1619292713670.png


It seems like the slashes being / instead of \ in the path prevents it from working.

Saving the map as a .w3x instead of a folder and manually changing the path of the DISBTN so that it has \ as a separator makes it work again. But is there a way to make it work, while still saving the map in a folder? Outside of this problem, it's been much more convenient to use than the old import manager.
 
I normally upload my stuff to root, but if you need to bulk upload stuff to a sub folder I guess you can first use the import manager to create the sub folder, then save your map as a folder and dump all your files into the folder that was created by the import manager.

I too have had problems with just dumping files and folders into the map folder, with the "/" instead of "\".
 
Level 5
Joined
Aug 15, 2012
Messages
139
Putting files in a folder created by the import manager didn't fix it for me unfortunately - the new path got generated with the wrong slash

EDIT: Even when I'd correct the path manually in the import manager, the DISBTN shows up green in game, as long as I'm working with a map folder. However, it at least starts working if I just save the map to a file from that state.

Moreover, if I actually set a unit's icon to a path of, for example Icons\BTNHorse.blp (with a \), with the exact same path set in the import manager, even the enabled icon shows up as green. If the unit's icon is set to Icons/BTNHorse.blp (with a /), the enabled icon works regardless of whether the path in the import manager has \ or /. Same thing happens with custom models. It's a bit of a mess.

It seems like the way to go is to not use any \ paths while working on a map folder during development, then at release, replace / with \ and then save as a *.w3x file.

I've just realized that I actually haven't tried models with custom textures yet, I wonder if that will get broken as well.
 
Last edited:

Dr Super Good

Spell Reviewer
Level 64
Joined
Jan 18, 2005
Messages
27,285
Try with 1.32.10 (latest). This could be a bug that was fixed as the feature was quite new back then.

This could be a conflict of path separator. Especially if using an operating system which uses a different file path seperator from what Warcraft III does. Windows 10 should be robust to both styles of file path separator by default, but if forcing the use of UTF16 long file paths then it only supports the Windows separator format.
 
Status
Not open for further replies.
Top