It is time to pick a side on an issue that could affect the quality of Skywind.
Here is the situation...
Skywind can either become standalone or stay dependent on skyrim.esm
Here are some pros and some cons of going standalone.
PRO's
- We don't need to worry about putting too much stress on the engine or worry about mod compatibilities.
- We dont have to "mind the gap" between games. (fixes issue with lore)
- It adds to the experience being forced to start at level 1 (starting at level 40 or 50 ruins the fun and removes alot of the challenges)
- far less to load in Creation kit
- we can change the UI, make our game unique!
Con's
- Character continuity (not being able to go from one story to the other)
- Seperate programs to run
- we have to create a seperate installer
- we have to make seperate paths to meshes and textures such as C:\\Program Files\Morroblivion\skywind\data\meshes\ (make sure it uses this path instead of skyrim's steam paths)
As you can see the pro's outweigh the cons now, however more cons might come into play.
In my personal opinion i believe jumping to standalone is the way to go.
Let us get a poll inserted on this thread please.

Even if they have to be kept
Even if they have to be kept in the same package with an option to start a Morrowind or a Skyrim game on startup of a new character, I think Skywind definitely needs to be standalone. The thought of them possibly crossing over and destroying the lore is enough to give me the OCD shivers :)
Ideally for me the game would be ENTIRELY standalone, with an installer like mentioned in the first post. This means mods can be managed independently also. But I have no idea if this is plausible due to the legal and technical restrictions on such a setup. Is it still possible to get in trouble with Bethesda for such a thing, even if you legitimately own Skyrim? They can get hella tight about their assets