Master Files & Moding Mods

[sumoftwosins]

The title might sound confusing, but here is what I want to do:

 

1. Release my mod without all the mini-quests included ( Due to time constraints ).

 

2. At a latter time, release a mod that has the remaining content.

 

2.a. Update the original mod without replacing it.

 

 

So that is what I want to do. Does my original mod need to be converted to an ESM or something? Or if I just create a new mod, load both in geck, and make the changes to the old mod in the new one... will that work?

 

I'd like to know a head of time. I don't want to force everyone who wants to played the new contracts to be forced to start back from scratch.

[phoneyLogic]

Hi there,

 

I have a problem with modding a Plugin for Fallout3 too

 

---

What I know:

Plugins (esp) are not working with other Plugins.

So it is not possible to mod a mod in that way.

 

Masterfiles (esm) are moddable by Plugin.

But you can`t safe a Masterfile in GECK.

---

 

Soo...

because I want to mod a Mod, is there a way to convert a Plugin into a real Master?

 

-> Tried to load TES4Gecko from here: http://www.tesnexus.com/downloads/file.php?id=8665

But unfortunately I do not own Oblivion and it refuses to work without it and I get this:

 

That`s the Main.main.(main) problem

 

Is there a way to get around it?

I don't want to patch my esp, want to make a master.

 

thx

[Yossarian22]

Is there a way to get around it?

I don't want to patch my esp, want to make a master.

 

You can create and convert Plugins/Masters with FOMM

[Cipscis]

Normally, plugin files can't access assets that exist in another plugin file - only those that exist in a master file. However, there is a method known as "mod de-isolation" that will allow you to break this rule and access assets that exist in one plugin file from another plugin file.

 

Basically, de-isolation consists of "esm-ifying" your "source" plugin with a tool like FOSE's Plugin Editor, then create your plugin that uses assets from the "source" file as you normally would, then convert the "source" file back into a plugin file.

 

The basic premise behind this method is that although the GECK doesn't like the idea of creating plugins that are dependent on other plugins, the game engine doesn't actually have a problem with it.

 

Cipscis

[phoneyLogic]

Thanks, you both, I got it working :)

kudos