How to import Void Elf Shield Maiden

Introduction

This is an automatically generated tutorial. It will guide you through the process of importing the model Void Elf Shield Maiden of the bundle Void Elf Shield Maiden. Please note that all the screenshots in this tutorial were made using a Mac, however it should be no problem to interpret what is equivalent on a Windows or Linux machine.

Extract and Access

I am assuming that you have already downloaded the file Void Elven Units and Heroes.zip and know where it is located on your hard drive. The file is compressed as a zip archive. Most modern operating systems allow you to unzip the archive by double clicking it and dragging the contents out to the desktop (or any other place).

When you have extracted the archive, it should look like this:

Open World Editor and click Module -> Import Manager:

This is the Import Manager. From here you can add and remove custom files from your map file:

Importing VEShieldMaiden.mdx

Now Click the "Import File" Button:

Next select 'VEShieldMaiden.mdx' in the folder which you extracted from the zip archive:

The file has been properly added to the map archive:

Done, you have imported the file VEShieldMaiden.mdx.

Importing VESMHD.dds

Now Click the "Import File" Button:

Next select 'VESMHD.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file VESMHD.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file VESMHD.dds.

Importing VESMHD1.dds

Now Click the "Import File" Button:

Next select 'VESMHD1.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file VESMHD1.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file VESMHD1.dds.

Importing VESMHD2.dds

Now Click the "Import File" Button:

Next select 'VESMHD2.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file VESMHD2.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file VESMHD2.dds.

Importing VESMHLD.dds

Now Click the "Import File" Button:

Next select 'VESMHLD.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file VESMHLD.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file VESMHLD.dds.

Importing VESMMD.dds

Now Click the "Import File" Button:

Next select 'VESMMD.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file VESMMD.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file VESMMD.dds.

Importing VESMMD2.dds

Now Click the "Import File" Button:

Next select 'VESMMD2.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file VESMMD2.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file VESMMD2.dds.

Importing VESMMD3.dds

Now Click the "Import File" Button:

Next select 'VESMMD3.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file VESMMD3.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file VESMMD3.dds.

Importing VESMMD4.dds

Now Click the "Import File" Button:

Next select 'VESMMD4.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file VESMMD4.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file VESMMD4.dds.

Importing VESMME.dds

Now Click the "Import File" Button:

Next select 'VESMME.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file VESMME.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file VESMME.dds.

Importing VESMME2.dds

Now Click the "Import File" Button:

Next select 'VESMME2.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file VESMME2.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file VESMME2.dds.

Importing VESMME3.dds

Now Click the "Import File" Button:

Next select 'VESMME3.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file VESMME3.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file VESMME3.dds.

Importing VESMME4.dds

Now Click the "Import File" Button:

Next select 'VESMME4.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file VESMME4.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file VESMME4.dds.

Importing VESMSD.dds

Now Click the "Import File" Button:

Next select 'VESMSD.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file VESMSD.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file VESMSD.dds.

Importing VESMSE.dds

Now Click the "Import File" Button:

Next select 'VESMSE.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file VESMSE.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file VESMSE.dds.

You're done

You have now imported your model. Don't be afraid when you place the object and it appears to be a purple cube. Just close the map, re-open it and it will look fine in the World Editor.

If you did exactly as this guide told you and it did not work properly. Please make a thread in the Modeling & Animation Forum containing the following:

And we will do what we can to help you.