How to import Queen Azshara, empress of Nazjatar

Introduction

This is an automatically generated tutorial. It will guide you through the process of importing the model Queen Azshara, empress of Nazjatar of the bundle Queen Azshara, empress of Nazjatar. 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 Queen Azshara empress of Nazjatar.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 naga queen azshara.mdx

Now Click the "Import File" Button:

Next select 'naga queen azshara.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 naga queen azshara.mdx.

Importing body.dds

Now Click the "Import File" Button:

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

Importing extra_eyes2.dds

Now Click the "Import File" Button:

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

Importing face.dds

Now Click the "Import File" Button:

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

Importing glow.dds

Now Click the "Import File" Button:

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

Importing hair.dds

Now Click the "Import File" Button:

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

Importing staff emissive.dds

Now Click the "Import File" Button:

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

Importing staff norm.dds

Now Click the "Import File" Button:

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

Importing staff orm.dds

Now Click the "Import File" Button:

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

Importing staff.dds

Now Click the "Import File" Button:

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