Jump to content

Volcano

Members
  • Content count

    7,255
  • Joined

  • Last visited

Everything posted by Volcano

  1. 12 OCT scenario: Delaying Action 05t-HN (UK)-4023-OMU //try this again (see above for SCE file), otherwise will move to the next one in the list if there isn't enough people SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. 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.
  2. 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): 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. 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. DO NOT use support vehicles (supply vehicles, bridge layers, maintenance vehicles) for reconnaissance. 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. 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. 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.
  3. 5 OCT scenario: Delaying Action 05t-HN (UK)-4023-OMU SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. 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. Delaying Action 05t-HN (UK)-4023-OMU.zip
  4. 28 SEP scenario: Civil War Dera Ghazi-4019b (same as last week, we will give it another go and if we don't have enough players then we will skip it - see previous post for scenario file) SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. Need THREE COs. Need at least 4-6 players per insurgent side, and Government side needs about 8 players. 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.
  5. 21 SEP scenario: Civil War Dera Ghazi-4019b SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. Need THREE COs. Need at least 4-6 players per insurgent side, and Government side needs about 8 players. 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. Civil War Dera Ghazi-4019b.zip
  6. Well, it was a scenario created about a decade ago, but got tired of playing it on an SB1 map, so I reworked it (updated it). So not really my scenario (not complicated enough for me to make it - I over complicate all my scenarios).
  7. 14 SEP scenario: 6k Front 2013-4010-M1A2-OMU SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. 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.
  8. OK, I made some changes to the scenario. I think a good compromise, Red has MILAN 3ER* missiles, 3.5km, tandem, ~900 RHA, and the quantity light still has the 2x light infantry SPIKE teams on both sides (but they are MR, not LR). There is winning, and there is fun, and we want to try to have both in TGIF scenarios, and I think the Spike is just too OP for the numbers of them there.
  9. 7 SEP scenario: Symmetrical Attack 11-SC-4019a-OMU (again, see 31 AUG scenario post above) SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. So the deal is, we need at least 16 people. If we don't get that many then we will move on to the next scenario (two tries to get sufficient # of people then we move on). 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.
  10. Thanks, it was a tough / fun battle. I will add something in there about the "center" grid squares.
  11. 31 AUG scenario: Symmetrical Attack 11-SC-4019a-OMU SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. 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.
  12. NATO Reticle explained?

    OK thanks for the info.
  13. NATO Reticle explained?

    Can someone please take a screenshot of the reticle that is "calibrated wrong"? It would help to eliminate any possible confusion. At this point I am assuming we are referring to the Commander's Day Sight (F3) and that both the APDS and HE scale is wrong? (I guess no screen shot is necessary if my assumption is correct.)
  14. 24 AUG scenario: TGIF T62 Mission 3-7YKWish_v6 SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. 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.
  15. Nah just damaged vehicles repaired, no reviving.
  16. BTW, not sure if everyone noticed but the deployment area was a repair-all repair zone (it was mentioned in the notes of the briefing). Even I forgot about that and looked over it, so I added some text about it on the map.
  17. 1. Made Green's deployment zone a bit smaller. 2. Made Red's deployment zone a little bigger. 3. Adjusted Blue's tank type (want to try Shot Kal now that we have it, we didn't have it when I first made it), and gave them +1 tank and changed their "Support" vehicle (that deploys with the insurgents/militia) into an ASLAV-25. 4. Enhanced UN side, making them "smarter" and made their counter attack (if their base falls) a little more potent. 5. Utilized a few unused vehicle types on the UN side, like the TAM VC. 6. Added a Mi-8 Hip with commandos to Red (they were originally intended to have it). 7. Corrected a problem on Green side where the ambulance was stuck in a walled compound when it spawned. 8. Corrected the missing ambulance on Orange side. 9. Added a note to the map. 10. Enhanced the civilian side a bit. 11. Changed each side's warlord tank to a T-72B1 with ERA (to encourage it to be used in combat, possibly risking its loss more, rather than it being a crap tank that just sits in the rear). 12. Added a minefield between Green and Red side to make it a bit hindering to just rush at each other from the start. Also added a few minefields between all other sides as well. You can't see the minefield on the map but there is the circular "mined" area graphic in the general area. I think that is about it.
  18. Thanks everyone for playing and CO'ing, I made some small tweaks to help improve it for next time. Also, just FYI, some had mentioned the that the side score didn't add up correctly, but when I looked into this I remembered that it is because the convoy points are "bonus points", which are added on top of the scaled score. So, you have 1,000 normal points, and then another 100 - 200 bonus points added on top (depending on which side you are), so its scaled between 1000, 1100 and 1200 points. So, its normal that they don't add up exactly due to the inclusion of the bonus points. This affects all sides, so since the winner is the side with the most points - it isn't something that hurts one particular side.
  19. 17 AUG scenario: Brush War-4023a-MAD SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. Four COs (Blue vs. Green vs. Orange vs. Red). Need at least 16, preferably 20 people total. If we don't have enough, then we will play the next SCE in the list (and push this one a few weeks). 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.
  20. 10 AUG scenario: TGIF_CUANAVALE_4023_OMU_V1 SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. 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.
  21. 03 AUG scenario: Hasty Defense 01 (US) M60A3-HTH-MAD-4023 SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. 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.
  22. 27 JUL scenario: UN Safe Zone-4019e-OMU-MAD SPECIAL CONSIDERATIONS: Need three COs, Red vs. Orange vs. Blue (UN). Draft? Yes. Random CO selection? Yes. The three people that CO'd the co-op last week are exempt from the random CO selection. 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.
  23. Yes, but I don't want Red to be RU, they are supposed to be CN. The enemy vehicles are modeled after CN side. It would happen in modern warfare that two side's infantry camouflage might be similar. You just have to be more careful as to where friendlies are via the map is all (and the risk of fratricide is always present)...
  24. I can't really do that without splitting the Blue side into several parties. The Blue side is US2000, and the Red slide is China 2000s, and both have a digital camo pattern. That is just how it is now days, digital patterns look similar, although the colors are different (CN has green in it). Of course we need US multicam to replace the ugly obsolete ACU pattern now days though. Theoretically the scenario could be split into multi parties for DK and UK camo patterns on infantry, but I would have to investigate how extensive that would be with the logic, etc.
  25. Thanks, I will have to tweak it a bit for when we play again in 2019 (it hasn't been played since v3.025 and the difficulty could probably be increased a little), plus an end mission message would be nice.
×