Mjana's Labyrinth - mod author support and discussion

[Trykz]

 

As the title says, this thread is for discussion and support for mod authors building plug-ins under the MjanasLabyrinth.esm master file. Please keep general discussion of the mod in the general users thread, so this thread stays clear for those looking for help with setting up their plug-ins. Thanks, Trykz

-----------------------------------------------------

 

There are a few things mod authors need to know before building under this master file, so I'll cover the basics first:

 

Most importantly, is that it uses a ton of assets only available in the Dawnguard DLC. Thus making Dawnguard a requirement.

 

Next, is the MjanasLabyrinth.esm master file itself. This file holds all of the information that manages the assets contained in the MjanasLabyrinth.BSA archive (NPC hair and FaceGen meshes and textures). This file must NOT be altered in any way. Altering the ESM runs a significant risk of breaking the entire framework, and every plug-in built under it. Do not remove or relocate any assets in the castle OR the labyrinth, or your plug-in will break everyone else's.

 

Finally, is the MjanasLabyrinthUpdater.esp file. This file controls any necessary changes/additions to the MjanasLabyrinth.esm master file, without actually altering it in any way. The only person who should be making changes to this file is me, or anyone I might authorize to make changes to the castle or labyrinth in the future. This file should be the last thing loaded in the user's load order, so the latest changes/additions are reflected for every plug-in. These files should never be re-uploaded by anyone other than me under ANY circumstances.

 

I cannot overstate the importance of not altering these files in any way.

--------------------------------------------------------

Things to know before getting started:

 

In the Skyrim folder (the folder with the Data folder in it), you'll find this file:

 

SkyrimEitor.ini

 

Open this file in Notepad, and add this line to the bottom of the [General] section:

 

bAllowMultipleMasterLoads=1

 

Next, scroll down to the [Archive] section, and find this line:

 

SResourceArchiveList2=Skyrim - Shaders.bsa, Update.bsa

 

Edit this line and add the following:

 

SResourceArchiveList2=Skyrim - Shaders.bsa, Update.bsa, Dawnguard.bsa, MjanasLabyrinth.bsa

 

Save these changes and exit Notepad.

 

This will allow you to load multiple master files and their relevant BSAs into the Creation Kit, as you'll be needing to load a number of master files and archives to build your plug-in under this framework.

 

Getting everything loaded into the Creation Kit:

 

When you open the CK, click File and then Data. A box will open filled with any installed plug-ins and the Skyrim master files. Select and activate the following:

 

Skyrim.esm

Update.esm

Dawnguard.esm

MjanasLabyrinth.esm

 

DO NOT set an active file. Just click the "OK" button in the lower right corner of the window.

 

At this point (once the CK loads everything) you're ready to start building your plug-in. You will be able to call in assets for your plug-in to use from the Skyrim, Dawnguard, AND MjanasLabyrinth archives to use in your plug-in.

 

The castle faction system and jail can be used to protect any NPCs you add the crime faction to, as well as punish the player with jail time or fines from any plug-in that hooks into the labyrinth's faction system. The NPC hair files can also be used to customize your NPCs so they aren't so plain. There aren't many (about 10 or so), but they're better than only having vanilla hairs to work with. You can load in the MjanasPlayground.esp (found here) if you like for examples on how to set up your NPCs to use those assets seamlessly.

 

Hooking into the labyrinth:

 

Hooking into the labyrinth is handled through doors located within the labyrinth cell. When you load the cell to pick a door to use, your view will be of the room directly above the coc marker in the cell. Currently only two doors are in use. The door that leads to the castle, and the one immediately left of it, which leads to my plug-in mentioned above. If you need an example of how to set this up, load in my plug-in and have a look. Pick the door you want to use (and note it's physical location and refid for other mod authors to reference). There are over 50 doors in the labyrinth to choose from, so there should be no issue with availability for quite some time.

 

You can dump users from your plug-in wherever you like. But you MAY NOT use a "2-way" exit into Tamriel worldspace. An example of how to set up a one-way exit is already in place at the bottom of the labyrinth in the cave, meant to show you how to set up such an exit. Plug-ins can lead back into the labyrinth through the same door used to enter the plug-in. But no doors can lead from Tamriel worldspace directly into the labyrinth. This rule is in place as a matter of fairness to other mod authors, and to insure the entirety of the castle, labyrinth, and any hooked in plug-ins remain in constant use.

 

If I find your mod adds an entrance back into the labyrinth from Tamriel worldspace, I'll update the MjanasLabyrinthUpdater.esp and break your mod. Simple as that. My only other rule is that NO mod hooking into the labyrinth contain sexual content between adult and obvious child NPCs. Smack them around, enslave them to clean up and perform work/chores, even kill them if you want. But I'll break any plug-in that adds sexual content that they participate in. If you want that type of thing for your own personal use, that's your business and your right. But you will NOT release it publicly as part of this framework. Doing so would reflect negatively on the entire project.

 

Finally, when you're ready to release your plug-in, PM me with a link that I can add to a file list in the second post of the Mjana's Labyrinth user thread here. All plug-ins created under this framework will be listed there for easy locating and reference, and you can use that thread to correspond with users of your plug-in. I would however, suggest creating a plug-in specific thread for support issues to keep that thread clear for discussion among users.

 

If you have any questions, feel free to post them here and I'll help in any way I can.

 

Thanks,

 

Trykz