How to import Statues of Vivec 2

Introduction

This is an automatically generated tutorial. It will guide you through the process of importing the model Statues of Vivec 2 of the bundle Statues of Vivec 2. 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 Statues of Vivec.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 Vivec_Statue_2.mdx

Now Click the "Import File" Button:

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

Importing TX_ASHSHALK_STATUE_01.blp

Now Click the "Import File" Button:

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

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 TX_ASHSHALK_STATUE_01.blp.

Importing TX_STATUE_B_ULAF.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_B_ULAF.blp.

Importing TX_STATUE_B_WRIST00.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_B_WRIST00.blp.

Importing TX_STATUE_UA_C_P.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_UA_C_P.blp.

Importing TX_STATUE_VIVEC_C.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_VIVEC_C.blp.

Importing TX_STATUE_VIVEC_G.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_VIVEC_G.blp.

Importing TX_STATUE_VIVEC_HFINGER.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_VIVEC_HFINGER.blp.

Importing TX_STATUE_VIVEC_HPALM.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_VIVEC_HPALM.blp.

Importing TX_STATUE_VIVEC_HTHUMB.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_VIVEC_HTHUMB.blp.

Importing TX_STATUE_VIVEC_LA.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_VIVEC_LA.blp.

Importing TX_STATUE_VIVEC_LF.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_VIVEC_LF.blp.

Importing TX_STATUE_VIVEC_LL.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_VIVEC_LL.blp.

Importing TX_STATUE_VIVEC_N.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_VIVEC_N.blp.

Importing TX_STATUE_VIVEC_UA.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_VIVEC_UA.blp.

Importing TX_STATUE_VIVEC_UL.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_VIVEC_UL.blp.

Importing TX_STATUE_VIVECHEAD.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_VIVECHEAD.blp.

Importing TX_STATUE_VIVECJEWEL.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_VIVECJEWEL.blp.

Importing TX_STATUE_VIVECJEWEL01.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_VIVECJEWEL01.blp.

Importing TX_STATUE_VIVECJEWEL02.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_VIVECJEWEL02.blp.

Importing TX_STATUE_VIVECJEWEL03.blp

Now Click the "Import File" Button:

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

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 TX_STATUE_VIVECJEWEL03.blp.

Importing TX_W_EBONY_BLADEBASE.blp

Now Click the "Import File" Button:

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

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 TX_W_EBONY_BLADEBASE.blp.

Importing TX_W_EBONY_EDGING.blp

Now Click the "Import File" Button:

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

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 TX_W_EBONY_EDGING.blp.

Importing TX_W_EBONY_QUILLION.blp

Now Click the "Import File" Button:

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

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 TX_W_EBONY_QUILLION.blp.

Importing TX_W_IMPERIAL_BROADSWORD_GUARD01.blp

Now Click the "Import File" Button:

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

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 TX_W_IMPERIAL_BROADSWORD_GUARD01.blp.

Importing TX_W_IMPERIAL_SHORTSWORD_GUARD00.blp

Now Click the "Import File" Button:

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

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 TX_W_IMPERIAL_SHORTSWORD_GUARD00.blp.

Importing TX_W_SPEAR_EBONY_00.blp

Now Click the "Import File" Button:

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

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 TX_W_SPEAR_EBONY_00.blp.

Importing TX_W_SPEAR_EBONY_01.blp

Now Click the "Import File" Button:

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

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 TX_W_SPEAR_EBONY_01.blp.

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.