How to import EngineeringBay

Introduction

This is an automatically generated tutorial. It will guide you through the process of importing the model EngineeringBay of the bundle EngineeringBay. 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 Terran Building Pack (Starcraft 2).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 EngineeringBay.mdx

Now Click the "Import File" Button:

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

Importing engineeringbay_diffuse.blp

Now Click the "Import File" Button:

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

Importing engineeringbay_emissive.blp

Now Click the "Import File" Button:

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

Importing Firebomb.blp

Now Click the "Import File" Button:

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

Importing fx-flare-generic.blp

Now Click the "Import File" Button:

Next select 'fx-flare-generic.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 fx-flare-generic.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 fx-flare-generic.blp.

Importing terranbuild_diffuse.blp

Now Click the "Import File" Button:

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

Importing TerranBuildingFire.blp

Now Click the "Import File" Button:

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