How to import Void Defender

Introduction

This is an automatically generated tutorial. It will guide you through the process of importing the model Void Defender of the bundle Void Defender. 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 VEDefender.mdx

Now Click the "Import File" Button:

Next select 'VEDefender.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 VEDefender.mdx.

Importing VEDefDDMD.dds

Now Click the "Import File" Button:

Next select 'VEDefDDMD.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 VEDefDDMD.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 VEDefDDMD.dds.

Importing VEDefDDMO.dds

Now Click the "Import File" Button:

Next select 'VEDefDDMO.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 VEDefDDMO.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 VEDefDDMO.dds.

Importing VEDefMCMD.dds

Now Click the "Import File" Button:

Next select 'VEDefMCMD.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 VEDefMCMD.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 VEDefMCMD.dds.

Importing VEDefMCMO.dds

Now Click the "Import File" Button:

Next select 'VEDefMCMO.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 VEDefMCMO.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 VEDefMCMO.dds.

Importing VEDefMD.dds

Now Click the "Import File" Button:

Next select 'VEDefMD.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 VEDefMD.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 VEDefMD.dds.

Importing VEDefMD1.dds

Now Click the "Import File" Button:

Next select 'VEDefMD1.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 VEDefMD1.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 VEDefMD1.dds.

Importing VEDefMD2.dds

Now Click the "Import File" Button:

Next select 'VEDefMD2.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 VEDefMD2.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 VEDefMD2.dds.

Importing VEDefME.dds

Now Click the "Import File" Button:

Next select 'VEDefME.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 VEDefME.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 VEDefME.dds.

Importing VEDefME1.dds

Now Click the "Import File" Button:

Next select 'VEDefME1.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 VEDefME1.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 VEDefME1.dds.

Importing VEDefMO.dds

Now Click the "Import File" Button:

Next select 'VEDefMO.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 VEDefMO.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 VEDefMO.dds.

Importing VEDefMO2.dds

Now Click the "Import File" Button:

Next select 'VEDefMO2.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 VEDefMO2.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 VEDefMO2.dds.

Importing VEDefWMD.dds

Now Click the "Import File" Button:

Next select 'VEDefWMD.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 VEDefWMD.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 VEDefWMD.dds.

Importing VEDefWMD1.dds

Now Click the "Import File" Button:

Next select 'VEDefWMD1.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 VEDefWMD1.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 VEDefWMD1.dds.

Importing VEDefWMD2.dds

Now Click the "Import File" Button:

Next select 'VEDefWMD2.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 VEDefWMD2.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 VEDefWMD2.dds.

Importing VEDefWMD3.dds

Now Click the "Import File" Button:

Next select 'VEDefWMD3.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 VEDefWMD3.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 VEDefWMD3.dds.

Importing VEDefWMD4.dds

Now Click the "Import File" Button:

Next select 'VEDefWMD4.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 VEDefWMD4.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 VEDefWMD4.dds.

Importing VEDefWMD5.dds

Now Click the "Import File" Button:

Next select 'VEDefWMD5.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 VEDefWMD5.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 VEDefWMD5.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.