Jump to content
Sign in to follow this  
Volcano

TGIF 2019: scenario list, discussion, and house rules

Recommended Posts

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). EXCEPTION: if a scenario requires more than two COs (i.e. because it has more than two sides) then there is no restriction on volunteering back-to-back with the previous 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.   //no longer necessary, now all off-map artillery barrages are capped at a 2 minute max duration.
  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.   //no longer necessary, now all off-map artillery barrages are capped at a 2 minute max duration.
  3. DO NOT use support vehicles (supply vehicles, bridge layers, maintenance vehicles) for reconnaissance.
  4. DO NOT study the enemy's side in the scenario in the Mission Editor AT ALL. 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, banning certain users from CO'ing, or from participating in TGIF. Also, the CO should strive to have all users on his side play within the guidelines of the house rules - since bad behavior of the side reflects badly on the CO.

 

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 specific 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 the TGIF scenario listing may not get updated due to real world situations.
  • This TGIF scenario listing 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 becoming unfair (due to both sides studying the enemy situation in advance).
  • If this TGIF scenario listing 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 listing 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.

Share this post


Link to post
Share on other sites

Whoops, forgot it was 2019. Here is the new TGIF thread for your pleasures.

 

New TGIF scenarios will be posted here.

Share this post


Link to post
Share on other sites

11 JAN scenario:

 

Air Assault 02-4023b

(Or something smaller, if we don't have at least 16)

 

SPECIAL CONSIDERATIONS:

  • Draft? Yes. Green and Red draft, then Green side has two or three volunteers that will go to Blue side, who will support Green.
  • Random CO selection? Yes. Three sides (Green & Red). Blue CO is volunteer from Green side.

NOTES:

  • Avoid studying the enemy's side; only gather intel from the briefing and exposed enemy unit icons (enemy intel), and briefly looking over both sides to figure out which one you want to CO. Anything beyond that ruins the fog of war element.
  • To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase. You may briefly look at both sides like this to see which side you want to play or CO on. As CO, once you choose a side, go to that side and create your plan.
  • Remember to play within the TGIF House Rules and SB.com community rules.

Air Assault 02-4023b.zip

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×