Door Markers

Here I explain how to link one or more doors from an exterior cell to an interior cell.

1. Give each door you add a unique ID Name. (Do this before you try to link any doors in your cell - otherwise you get random results. So name all doors in your interior cell and any doors in your exterior cell that you have placed - regardless of whether you plan to link-to them or not. Make sure the names mean something to help you identify them when you link-to them.)

a. Once you add the door to the cell (world or interior) then double-click the door.

b. At the top of the window that appears is space for you to enter a unique door ID Name.

2. Go to one of the doors you plan to link and double-click it. (I normally go to my exterior cell door.)

3. Select Teleport tab.

4. Select Cell and select the cell you want to teleport to. (So if in exterior cell I would select my interior cell.)

5. Now a list of doors for that cell should show up in the Reference space, but mine never do and I get a blank area here.
So how do you solve that?

a. Go up and click on the Linked Door: Reference In Window button.

b. Now you have a red cross hair icon and use that to double-click the door you are linking-from in this cell (the same door you double-clicked to start all this).

c. Now you may have to go to 4 and do that again. The key is you want to be able to see the drop down list in the Reference space list of doors.

d. Now you can finally see the Reference space list of doors for the cell you want to link-to - the doors should be named so you can easily identify them.

6. It might be good at this point to click "OK" and make sure you can see the door marker you just added to this current cell - if you can't see it you might try the whole process again with the door out from the house - sometimes it gets lost in the house mesh.

7. Ok so now what? While you are here position the door marker so it faces out from the door you are linking-from and then double-click the door marker (it is yellow with an arrow coming out of it).

8. The question window that pops up asks: View Door Reference for this Door Marker? Click Yes.

9. You are teleported to the other door you just linked-to (for me the interior door - up till this point I've only been in my exterior cell).

10. Now you should be able to see the linked-to door's door marker (it is yellow with an arrow too). If you can't see it, it might be in the mesh or behind something else - it should be there - search for it you will find it - if anything just zoom in on it.

11. Position linked-to door marker so it is facing out from the door. (Note on door marker placement: Leave a little space between it and the door, I think if it gets too close you fall through the world, floor, etc.)

Repeat this for each door you plan to link. And save and save and save (just in case :) )

Hope this has helped.

Whist34 00:07, 19 April 2006 (EDT)

WARNING

(added 8/4/2006 by COMPUTWITCH, A different wikki user)

After 3 days of fighting the construction set and looking thorough the help forums, I finally found out that you CANNOT directly link together doors to create teleportation between structures that have been created and saved in different .esp files (also referred to as plugins or mods.) You can only link doors between cells that have been created and saved as part of the existing, active .esp file, then link the door(s) from your .esp file structure(s) to the door(s) placed in an existing space inside the original oblivion gameworld. (What you can see and access with no plugins running, such as a piece of wilderness or an existing gameworld structure such as a house, shop, or cave/dungeon/ruins)

Also, you cannot add a room containing a door to your existing .esp file structure, link it to an unused door in your existing structure, then save the room addition and teleport link as a seperate .esp file, effectivly creating a plugin to a plugin. The oblivion plugin manager programming specificly prohibits crosslinking mods or running a plugin to a plugin (to a plugin to a plugin.....)in order to maintain, as much as possible, both master file and plugin stability and compatibility.

For instance, if you make or download a house mod and name it "My house 1" and add a spare door to it that goes nowhere, then at a later date make or download another house mod and name it "My house 2", and add a spare door to it going nowhere, then load up either of the house mods as the active file and attempt to link the two doors together with a teleport marker, it will not work. What will happen is when you load the mods back up in the editor, you will get several missing object errors, then several more errors stating somthing to the effect of "myhouse 1 is not a previous, unique object. previous object is type CELL. myhouse1 will be renamed myhouse1COPY001. continue playing? Yes/No/Yes to all". This error will appear between 2 and 4 times, listing both of the mods you linked and and/or listing the doors you tried to link. If you try to play the mods, the game will either crash on startup or ignore the doors you created.

This problem has plagued many of the people (myself included) I have seen posting in the help forums who have downloded a number of house mods and then tried to link them together directly via added doors or link them to the catacomb mod that is currently available, (On August 5, 2006) at www.oblivionsourse.com.

There is, fortunatly, a workaround to this problem that provides a good solution without having to copy the entire .esp file you are trying to create a link to, merging it with the current one, deleting or moving the old .esp file, then restoring the lost links, lighting, etc. (see note at end of workaround section)

For information on how to add a room to your existing .exp file (mod) without crosslinking it, go HERE

NOTE: There is an Article in the questions section concerning the actual merging together of mods which may be of interest to people who would rather merge the .esp files of the houses they are trying to connect together to create a single mod, making direct linking of the doors possible, rather than try to implement a workaround solution such as the one linked to here.