From: Bramble Rose Farm, KS
There could be some solution allowing to keep stock and modded data together, but it is not so trivial and easy to implement.
I find no pleasure in reporting the following. It is not so trivial nor easy to implement a user-created scenario that can be played without interfering with or corrupting the data found in either stock scenarios, user-created scenarios, or both. This is a fact regardless of the level of difficulty in finding a solution.
I want to create and distribute new material for this game. I do not want to screw up somebody else's files just because I have a cool, new thing I want to share. I believe that the game system must provide a "lock-and-load-let's play" capability for the casual player. There should be no need for "back-up-your-data" warnings, nor can there be any game directory "exploratory surgery" operations--a popular experience with some mods/new scenarios for other games.
If this requirement can't be met, then I'm O.K. with that. I know this is a complicated game system. It is what it is. Let's acknowledge that it is so and move on if there is nothing that can be done.
As it currently stands, creating and distributing new Scenarios, OBs, Aircraft, Devices, etc., etc. is done at the creator's peril and at the user's displeasure if his favorite self-entered Me-109G statistics get obliterated without warning--for every scenario in his library. These issues will be magnified by each new participant in the process of creating and sharing with the WitE community--"something new"--new data, new OBs, better data, better OBs, that Leader wuz better than currently rated, etc., etc., etc., ad infinitum.
I sit here contemplating the Tscherkassy Pocket, with a stack of newly-purchased books saying, "DO IT!" But I already know that after I've left Hell's Gate, my sceanrio will be broken by something some other well-meaning contributor is doing right now to War in the East. And the intended user? Well...given a page-long README file instructing how to load, back-up, deconflict, he will do the smart thing and move along to play scenarios that are more fun, right now, and less...ummm...conflicting.
Perhaps the WitE development community can address these issues by doing one of three things.
A. Bite the bullet and isolate all data involved in a user-created scenario.
B. Require newly created work to be cleared by a bevy of WitE experts from Matrix before it is distributed to the gaming public, or...
C. Inform the using Public that The current Editor is intended for personal use only (Option C is the current and safe game-play default whether it was intended or not)
I certainly encourage opposing views regarding my premise that there is a data-sharing/confliction problem, and if there is one, whether my set of proposed solutions is correct and/or complete.
So heave-ho! I want to be wrong! I just want to design scenarios--that's my apple cart.