I don't like this idea one bit, I really think this would be incredibly negative to multiple facets of Command and would cause more harm than any amount of good it would provide. This is just my opinion of course and I'm not very good at expressing everything I'm thinking in a clear manner sometimes but I'll do my best.
There's a balance as to what should be optional, I personally think it's in a good place right now currently. Having every significant platform change that increases realism and accuracy be an optional setting I think would hold back growth and feature implementation in some respects and could be incredibly damaging to community content which is the foundation of a platform like CMO and has been since the Harpoon days.
Having a community-created scenario selection where every scenario uses a different set of realism and feature variables or just general features such as the new missile system would be an absolute disaster in my opinion.
From a player perspective you'd be having to learn multiple tactics and systems that behave incredibly differently per scenario (Ship OODA Values, Missile system, Radar rework.). It would be incredibly counter intuitive for a new player to learn, example: "Sometimes your Amraams will work like this but sometimes they won't, good luck." Instead of just being "Amraams work this way consistently in CMO because that's the way they do in real life." The latter phrase is how most features and additions to CMO should be viewed and looked at.
For an advanced player it's already going to be bad enough switching from and trying to determine which ship OODA values are in use in a scenario as it's possible to upgrade a scenario to the latest DB without the new values. I understand some features and changes HAVE to be optional because they can drastically alter the playability and balance of older scenarios unintentionally and preserving community scenario content is absolutely paramount for the longevity and growth of the game.
Then there's the fact that you'd be fielding a billion reports of issues with a scenario that's not really an issue it's just now you have 200+ scenarios that can use a different set up of the new realism system reworks and features.
I want and expect as a player that for the most part (some special setting aside; Submarine Communications, Terrain Features etc) that the realistic environment I play in has logic, rules and performance that's consistent. I shouldn't have to worry about, learn about,and execute fundamental changes in the way my F-14s engage with missiles each scenario because things like that should NOT vary based on scenario, they should function consistently based on realism with me having to make choices based on operational and tactical considerations in the scenario, and not which missile model the creator decided to use.
Then you'd have to worry about future features, and those future features would have to fit in and work with the various different models and feature sets that can be used optionally in a scenario. The way even simple features are added would have to be changed because you'd no longer be building features and changes based on consistent realistic variables but a multitude of them that may or may not be in operation depending on the scenario creator.
I won't get into the headache this would cause keeping the CSP in relatively functioning order and being able to make changes and fixes for the scenarios to make sure they still work correctly even for those creators that are no longer in the community.
Changes and fixes are implemented now for those creators no longer in the community because we know the realism or feature changes that broke or unbalanced them are feature that are activated globally for the platform and will remain so going forward. So the only change that can possibly work to fix that scenario is a change that ensures it's functioning and balanced based on the newly added feature or system rework. If those changes are optional we have no idea what the designers intent would be anymore.
There's certain changes that need to be optional to preserve community content, that's perfectly understandable and should absolutely be the case considering how important community content is.
Changes that rework a function, sensor, weapon or other system that drastically increases the functional realism of the platform and the environment/rules/logic of the platform should be implemented globally, universally and consistently. That type of implementation is required to build upon those changes. We won't see growth and evolution of those changes or at least as much if there's multiple optional variations of those changes. I.E the option of the Missie model. Eventually you'd have to pick and implement one as the primary model anyway if you want to improve and build off of it.
Players should know they are operating under the most realistic systems in the most realistic environment available, that generally shouldn't change based on what the scenario designer decided for all the reasons I stated above and more.
Feature A shouldn't function as X or Y based on what the scenario designer decided, it should function as realistic as the platform allows with scenarios built around that.
If something like the missile changes are causing frustration, misunderstanding, feelings that things aren't working right, etc even though it's suppose to be a positive addition to the game that drastically increases realism, we as a community should have open and constructive communication with the dev team as beta feedback allows to further explore what the issues are, and what tweaks or changes can be made to improve the transition and implementation of the system for the community and get it to a place we feel comfortable with.
I feel like people are asking for the missile system to be implemented optionally because it just doesn't
feel like a good change right now. As realistic as it's repeated to be it's causing players a lot issues and unintended behavior that just isn't fun at the moment. Those should be addressed rather than making things optional.
We've had changes in the past implemented globally and it's been just fine. The bottom line is that I personally and respectfully think making things like realism changes to missiles,radar and tracking, sonar and anything else is a bad idea for many reasons.
We'd no longer be operating (or learning as a new player) in an environment where systems and features function with the intended realism consistently and regardless of scenario but an environment where the implementation of realistic mechanics and features may or may not be present or even partially present.
One last thing, respectfully of course.
I agree. Every time you guys add any new realism related features, please make them optional. Some of us enjoy a more casual gameplay experience
Choice is always better but one of those choices in a platform devoted entirely to realism shouldn't be the omission of realism, those looking for a more casual experience have more than enough options while playing a scenario in the editor.
This isn't an elitist "Mah realism" thing. It's that taking the casual approach to a platform built from the ground up based entirely on the standards of it's global and consistent implementation of realism aka. regardless if scenario, can severely hurt the game and especially it's community content far more than the addition of major realism changes.
Missiles should work like missiles, and tracking should work like tracking the same way in every single scenario. A consistent environment with consistent rules and logic in a platform like this is probably one of
the most important things.
Saying that all future realism changes should be optional is in my opinion not a very good and destructive idea.
Excuse the spelling and Grammer, I'm away from my computer and had to type all this on my cellphone. I did go back and try and clean and it up but you'll probably find errors and issues still.
Regards,
Greg.