TGIF 2014: scenario list, discussion, and house rules

INTENT:

We are trying something new this year and we put all the "battle tested" scenarios into a list, and then randomly shuffled that list to create a TGIF play list. We are going down that list in order, choosing the next scenario to play from it rather than picking on a whim.

Rather than post the list here (because the list can/will change throughout the year), a post will be created here before each Friday mentioning the scenario that will be played. You can then download the scenario and decide if you want to CO (post here if you want to take it), otherwise whoever volunteers on Friday will be the CO.

CO GUIDELINES:

Basic guidelines as to who can volunteer as CO from week to week. The intent is solely to afford everyone the opportunity to CO:

• No one may volunteer to be a CO back-to-back TGIFs. That is, if Mr. X volunteers to CO this week, he cannot volunteer to CO next week, but he can volunteer the week after that (every other TGIF).
  
• If no one volunteers to be the CO, then anyone can CO at the time of the event. So, in the example above, Mr. X can CO again that next TGIF if no one volunteers during the week.
  

TGIF HOUSE RULES:

There will always be bugs in software and Steel Beasts is no exception. More-so, functionality that exists in the Pro version which has carried over into Pro PE often creates unforeseen situations which allow for abuse and unrealistic behavior. To counter this, there are "TGIF HOUSE RULES" which are basically a set of ethical rules to allow "fair and realistic play" to keep scenarios from bogging down into the morass of shame. The House Rules are as follows (and the list may grow over time):

1. DO NOT adjust the number of rounds per tube when calling off-map artillery strikes, because they currently have unlimited ammunition so it creates ridiculous situations. (Using number of rounds per tube with on-map artillery is fine because they are delivered differently and have finite ammunition.) If you want a long off-map artillery strike, just keep repeating it.
   
2. DO NOT adjust the duration when calling off-map artillery strikes -- for the same reason as rule #1. Also, like rule #1, setting the duration for on-map artillery strikes is OK. If you want a long off-map artillery strike, just keep repeating it.
   
3. DO NOT use support vehicles (supply vehicles, bridge layers, maintenance vehicles) for reconnaissance.
   
4. DO NOT intensely study the enemy's side in the scenario in the Mission Editor. You can open it and look at both sides, but do not touch anything or evaluate the reinforcement criteria, events, conditions, routes and waypoints. Looking at the enemy side to get an idea of what they have is acceptable, especially since you have to do this to figure out which side to CO anyway.
   
5. DO NOT use helicopters with the intent of causing a distraction for the AI. Everyone knows when this is happening, like when empty transport helicopters repeatedly return to "buzz" (fly over) enemy units at top speed again and again. Flying in on troop insertions and back out again is acceptable, as is engaging targets from a battleposition.
   
6. DO NOT hover helicopters at maximum ("Normal") height in battle positions, to use as an ATGM platform or to act as a recon satellite or an AI distraction. This is unrealistic at the moment since the Scenario Designer currently has no way to restrict/limit/cap flight height because he may want to represent certain types of conflicts where long range air defense and air superiority fighters exist. At such time, if ever, that the Scenario Designer can specify a maximum flight height, then we can remove this house rule.
   

NOTE: Failure to abide by the house rules will result in drastic measures by the TGIF coordinators, such as not posting the scenarios in advance, removing features from scenarios (like artillery and aircraft), or in the case of repeated violations, barring certain users from CO'ing. Also, the CO should strive to have all users on his side play within the guidelines of the house rules.

DISCUSSION:

*AFTER* the scenario is played, feel free to post constructive criticism about the scenario here, so that it can be improved. All constructive criticism will be taken into account, but pissing and moaning will be ignored.

Constructive criticism = complaints with specific suggestions

Pissing and moaning = complaints with no suggestions

DISCLAIMER:

Keep in mind that:

• The scenario may change at the last minute depending on TGIF turnout.
  
• Any plan file that you may create may be rendered invalid by last minute adjustments to the scenario (if you are going to CO, it is better to save a plan AND take a screen shot of the plan as backup).
  
• Sometimes this list may not get updated due to real world situations.
  
• This list will continue until we point in time that it is deemed "too much trouble", which is the moment in which we determine that no one new is CO'ing, or the situation is no different than before, or that the matches are becomes unfair (due to both sides studying the enemy situation in advance).
  
• If this list turns into a mud flinging contest, because someone was sour about losing or in order to insult a scenario designer then posting the scenario early will end.
  
• The scenarios that appear in this list are either new, classics, or at least played frequently and deemed "balanced". If you have a scenario that you think should be added to the play list then PM or create a post here about it.
  

28 FEB scenario:

!Kursk 2013 v5a

NOTE: To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase.

Thanks, you two have CO positions this week.

Speaking of which, I think we should establish some general guidelines to picking CO position, that is, if someone picks it one week, then they cannot volunteer for it the next week (but they could still CO if no one chooses to CO).

OK, I just posted some basic guidelines in the first post. I don't think it is anything unreasonable, but this way we give everyone a shot.

AFAIK, this scenario will be played in version 3.011 tonight.

Thanks to the two COs for co'ing last night. I think what I will try to do is post the next mission here at the beginning of the week after TGIF, leaving some time for people to discuss the previous scenario for a few days (if anyone wants). In other words, I will try to post the next mission here everyone Monday or Tuesday of the week.

7 MAR scenario:

Symmetrical Attack (smaller) 05-HN-3011

NOTE: To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase.

Scenario posted.

Don't forget, Brun and dta Delta CO'd last week, so they are unable to volunteer this week, unless no one takes it by Friday (then anyone can volunteer). They can volunteer next week though (every other week).

Now, don't be shy, any fresh blood volunteers?

Thanks to Paladin and Rotar for CO'ing and for all the feedback on the scenario.

I will make some improvements to that scenario for next time; I will probably just take the supply trucks away so the Apaches cannot resupply, plus fix all the spawning problems (vehicles spawning in buildings and on hill tops). At least the side on the receiving end could take comfort in the fact that it would have so many Hellfires (and the scenario was too small to resupply anyway).

Scenario for next week will be posted here this coming Monday or Tuesday again (unless I forget).

14 MAR scenario:

6k Front 2013-3002a-M1A2-OMU

NOTE: To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase.

Scenario posted. Remember that Paladin and Rotar cannot volunteer to CO this one because they CO'd last week.

Could I also suggest:

1) sending a message ~5 minutes before arrival of a particular wave of reinforcements notifying where they will be spawning, so the CO has time to plot routes to where needed.

2) perhaps 1-2 MANPADS teams to give the Apaches further pause if the opponent's Tunguskas are taken out.

3) spawn the Apaches on the ground, rather than default altitude (or, if that's not possible, give them a short initial route the the flight altitude set to ground level).

4) instead of using an MBT as the command vehicle, use a M113A3DK OPMV. It's a shame to have a prime MBT skulking around in the rear to avoid the radio-damage penalty. The use of the M113 is more akin to a TOC, which in real life would be the C2 node collecting and disseminating contact reports and SITREPS and the loss of which would have an effect similar to damaging radios in SB.

Thanks for the suggestions. Unfortunately I have to keep changes to this scenario to only very important issues, because there are about five of them that have to be changed. With that in mind...

Re: #1, it says in the briefing how often the reinforcements show up (ie. every 30 minutes), so it should be possible to deduce the arrival without a message -- we never needed it before. I don't think I will do this because it would involve creating six events, x5 scenarios (30 events).

Re: #2, not a bad idea, I may put two or three in the HQ area.

Re: #3, I spawned them at NOE height now, and in low ground (not on hills, that was an accident on my part when I swapped maps). In other words, that issue should be fixed.

Re: #4, I don't like that idea personally, the co tank is what you make of it. It can work just like an M113 OPMV if you just show a little self restraint, but the idea is that you only use it as a last resort to defend the HQ. If it does die and you lose radios, then that is the intent, because it allows a cut-off-the-head strategy. If a side is aggressively using the CO and not in last resort situations, or it is killed by a helicopter, then well, that is just how it goes (and a reward for them killing it).

And I'm still woozy from the rout last week anyway.

What I was suggesting was a message indicating *where* each wave will be spawning, since it appears the location was randomized. It was clear to me from the briefing when they were coming.

Ah well, that would be even worse. It would be 3 waves, x3 possible locations, x5 scenarios = 45 events.

17 MAR scenario:

UN Safe Zone-3011a

THREE COs are needed for this one: Blue, Red, Orange.

Disclaimer: the scenario is NEW, and as such may have rough edges!

NOTE: To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase.