Can I delete missions without problems?

[Swant]

I like to set up my own missions, so I usually delete all the premade missions and reference points when starting a new scenario (my side only).
Is there any potential problems doing so?
I'm talking about mission triggers, allied AI and things of that nature

[BeirutDude]

ORIGINAL: Swant

I like to set up my own missions, so I usually delete all the premade missions and reference points when starting a new scenario (my side only).
Is there any potential problems doing so?
I'm talking about mission triggers, allied AI and things of that nature

Short Answer: Generally ok to delete them.

Longer Answer: Be carful the Reference Points (RPs) aren't used for assigning Victory Points or other scenario critical function! Whenever I design I assume the player will delete any missions I up. Sometimes the scenario situation just needs some missions for the story line. Example: A CVG without an ASW Mission off the Kola Peninsula is just unrealistic. If a mission is scenario critical the designer(s) should state so in the Scenario Description.

[Swant]

Ok good to know, thank you.
I remember that in your scenario Curacao Crisis (very good by the way) you stated in the briefing not to delete some RPs

[DWReese]

I agree with Al that in general you can delete the missions with no harm to the scenario.

That being said, you may find that some of the missions that have been set up by the authors are pretty useful to have around. Rather than delete them, you may find it advantageous to adjust them to your liking, as opposed to deleting them completely. US carrier groups will always have CAP and AEW. Deleting those to just create them once again takes time. If you want fewer (or more) units on CAP, then you could just adjust it. You can move the reference points around rather than deleting them and creating them once again.

When I create a scenario I create it to be played from both sides, so I will have missions set up for each. I don't believe that any scenario designer takes offense to the game player ever deleting any of their missions, but I would recommend that you do so only after deciding that you really don't want the mission. Otherwise, just change it to what you do want.

In answer to you question, I agree will Al, for the most part you can eliminate almost everything without causing an issue.

[Swant]

I agree that the missions usually are very usefully. That's one of the reason I like to delete them before looking to closely. As a challenge.
When finish a scenario I like to compare my choices with the choices made the designer.
I often find that mine are inferior

[BeirutDude]

Command is so rich in detail and ways to do things that you never stop learning. I've been playing (and designing) for years and I learn something new every day. By far this has to be the most complex, flexible and immersive simulation out there. So we're all learning from each other here on the boards!

[Swant]

Definitely!

[kevinkins]

To be clear, deleting missions for the AI side would not work at all. But I am sure you are talking about the player side's missions. Without missions, the AI will not be instructed to do anything. It's not uncommon to reprogram the entire scenario leaving the OOB basically the same. But the AI side has to have orders.

[KnightHawk75]

ORIGINAL: kevinkins

To be clear, deleting missions for the AI side would not work at all. But I am sure you are talking about the player side's missions. Without missions, the AI will not be instructed to do anything. It's not uncommon to reprogram the entire scenario leaving the OOB basically the same. But the AI side has to have orders.

Yup don't touch the AI side(s) missions etc.
Read author's notes\scene briefings fully - generally if RP's or mission need to stay around (or stay around for awhile) they are mentioned. My general rule of thumb is let the scene play for 10 seconds before changing stuff, some authors do initial setup\randomization\spawning in the first couple seconds of a scene instead of on-load.

[BeirutDude]

...some authors do initial setup\randomization\spawning in the first couple seconds of a scene instead of on-load.

Indeed I do this a lot for both variable entry (I like it for subs) and teleporting units that have a mission assigned (SAG ASW Missions for example). So that is a good rule of thumb. If I need you to run it I try to make sure I mention it in the notes, but I also noted that people get impatient and don't read everything.

[boogabooga]

ORIGINAL: BeirutDude

ORIGINAL: Swant

I like to set up my own missions, so I usually delete all the premade missions and reference points when starting a new scenario (my side only).
Is there any potential problems doing so?
I'm talking about mission triggers, allied AI and things of that nature

Short Answer: Generally ok to delete them.

Longer Answer: Be carful the Reference Points (RPs) aren't used for assigning Victory Points or other scenario critical function! Whenever I design I assume the player will delete any missions I up. Sometimes the scenario situation just needs some missions for the story line. Example: A CVG without an ASW Mission off the Kola Peninsula is just unrealistic. If a mission is scenario critical the designer(s) should state so in the Scenario Description.

You can create a new allied side that just has the reference points. They player can't modify or delete them, but they are still active in the trigger logic.

[BeirutDude]

You can create a new allied side that just has the reference points. They player can't modify or delete them, but they are still active in the trigger logic.

How does that work for the side's missions, do the RPs need to assigned via Lua?

[Gunner98]

ORIGINAL: BeirutDude

You can create a new allied side that just has the reference points. They player can't modify or delete them, but they are still active in the trigger logic.

How does that work for the side's missions, do the RPs need to assigned via Lua?

It doesn't work for mission but this method works for triggers quite well and I try to have all triggers on a non-player side so that they cannot be deleted, unless the player deliberately switches sides and does so.

The fundamental question if I understand it - can you delete missions and RPs for a player side without affecting the scenario. I think generally yes, as has been said above. Two caveats:

1. some early scenarios or scenarios by some designers do have triggers on the player side - so it is worth thinking that through.
2. some RPs are used as markers to give the player an indication of where on the map something should be done - these are often also triggers. They are often labeled to indicated their purpose and they are usually also locked.

As for player side missions - I sometimes throw up my hands in frustration. If I put them in, players complain. If I don't put them in, players complain. So on this subject I tend to just do what I think is right. Grumbling ends....

[BeirutDude]

It doesn't work for mission but this method works for triggers quite well and I try to have all triggers on a non-player side so that they cannot be deleted, unless the player deliberately switches sides and does so.

Got it. Going to check that out for future scenarios! Like I said in another post, we're all learning something about this game every day! Thanks guys!

As for player side missions - I sometimes throw up my hands in frustration. If I put them in, players complain. If I don't put them in, players complain. So on this subject I tend to just do what I think is right. Grumbling ends...

I feel your pain here!!!!! See my post comments on "Command Scenario Mission Creep" as well! This why I started saying in my descriptions, "You have to stop somewhere!"

[kevinkins]

There is no perfect solution. However, a lot of missions used for playtesting should be removed before the the scenario is released. Leaving a few missions like an initial CAP or ASUW are OK. But the briefing might want to explain why they remain. And they should never put the player side into an ambush. In the end, it's up to the player to configure their missions. But giving newer players a bit of a head start is not a bad idea.

[jannas34]

Good luck getting this fixed

[Stanley_The_Rolmate]

message deleted

[jannas34]

the game sucks ass and the matrix splash screen makes sure you cant get a refund

[jannas34]

LOL mr angry deletes his message!

ORIGINAL: jannas34

the game sucks ass and the matrix splash screen makes sure you cant get a refund