I see bad UI. To open file user will have to drag it to top of a list or change it load priority to higher than others plugins. Maybe it'll not be a problem.
You can not reasonably edit a file in the middle of a content file sequence. First, that data model of the editor simply does not allow that. Supporting such a feature would increase the complexity by a huge amount. Second, if we were going to do that, this would result in a usability disaster.
Scenario: We have a sequence of 3 content files: A, B and C (in this order). The user is editing B. Now he decides to edit record x. Record x is present in B and C. Unfortunately the modifications in C will overwrite whatever changes the user makes in B. So none of his changes will have any effect on the state of record x as displayed in the editor.
Yes, I read that. It can be fixed by external tool. But more important is that file format will be changed for few headers...
I presume that this is an honest attempt to discuss this topic and somehow the point just got lost. I am sorry, but I think that is the 3rd time that I am having this discussion and I am starting to get a bit irritated about it. I am really the only one here, for whom this is totally obvious?
The files produces by the editor will not be compatible with MW. Saving them in a way that they can be mistaken for MW content files (by giving them the extension esp or esm) is a terrible idea. It would cause confusion to no end.
Any arguments about being able to fix these files by running them through an additional tool (e.g. the original CS) are meaningless, because we still have files coming out of the editor that look like esp or esm files and are not compatible with MW esp and esm files. People will produce these and they will upload these. And then other people will get confused about why their downloaded files are not working in MW (or project ProjectAedra, if that ever finishes).
I don't even want to think about the fallout we would get from that.