Volcano

31 JUL scenario: CENTRAL GOLAN V3 SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. Minimum # players: 12 NOTES: Remember to play within the TGIF House Rules and SB.com Community Rules.

Scout teams are allowed to be given UAV (micro) and UGVs, while normal rifle teams cannot (only PL units can be given this equipment). They also have a different map icon (obviously). So really, its more about them having a different map icon, so you can be immediately aware that you shouldn't route them around like normal infantry, and instead use scout tactics, and so you also know that they are the go-to unit to use the UAV and UGV (if they are equipped with one).

24 JUL scenario: !Battle for Schwaben Creek Valley T-72 v15-4162-OMU SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. Minimum # players: 9 NOTES: Remember to play within the TGIF House Rules and SB.com Community Rules.

17 JUL scenario: Brush Fire-Town Dispute-UN-4167-MAD SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. Minimum # players: 11 (Lubango: 4 vs. Luena vs. UN: 3) NOTES: Remember to play within the TGIF House Rules and SB.com Community Rules.

This page will answer all your questions and more... https://www.steelbeasts.com/sbwiki/index.php?title=T-72A/M1 https://www.steelbeasts.com/sbwiki/index.php?title=T-72B1_(m.1984) Just search for a keyword of what you are curious about (like "smoke" or "HMG" in this example). Its a good place to learn what you want, but then to continue reading and learn more than what you want to know. 🧐

While you're there, buy Serbia '14, I know the designer. 😎

10 JUL scenario: Allied Force MTC 01-smaller-4167 SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. Minimum # players: 9. Blue (2) & Green (3) vs. Red (2) & Orange (2). NOTES: Remember to play within the TGIF House Rules and SB.com Community Rules.

3 JUL scenario: !OBJ PV - MP-smaller_4167 SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. Minimum # players: 8. NOTES: Remember to play within the TGIF House Rules and SB.com Community Rules.

...and besides, what better way to celebrate 4th of July US Independence than to (virtually) BLOW sh*t up!!! Much safer than fireworks anyway. 😎

Thanks for playing. Of course it can be a bit frustrating to play for red, but that is to be expected and was still a good fight. Made quite a few small improvements... -Added GLs, unit quality, and PL/PSG medics to infantry. -Added +20 min -Slightly adjusted capture condition of the ADA circle. Should be good after that. Smaller version seems better too.

26 JUN scenario: Where the Victoria Crosses Grow 2013-smaller-4167 SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. Minimum # players: 10. NOTES: Remember to play within the TGIF House Rules and SB.com Community Rules.

Just FYI regarding last TGIF: The issue with the ICM damaging (collapsing) bridges has been fixed for the next patch. In the mean time, we will have a TGIF house rule that ICM should not be called on bridges.

Infantry are buildings are not fired upon by the AI until they shoot first, or until friendlies enter the building to clear it. This allows the possibility of ambushes, because the infantry in SB cannot behave like real infantry would. Real infantry would not sit in a window, they would hide further back in the room and open fire. Also, just because someone is visible in a window, you cannot easily tell if they are armed or not. Once the occupants open fire, they become known and a valid target to all. The exception to this is infantry located on the roof of a building. Otherwise everyone everywhere would know that infantry were in a building and open fire on them from long range and then that would be a complaint too. It makes more sense to give the infantry the advantage of surprise when they are located in a building. Hope that helps.

FWIW, I happened to save the AAR from last TGIF (Bridge Crossing Heavy) and it opens fine for me in 4.167. You might want to check the log to see if it says anything when you get this problem (better to exit SB and then look at the log).

Don't blame the software because someone forgot to publish a map. It happens. There are conditions that avoid this built into the software; the map is not allowed to be "packaged" for deployment to a server if it is unpublished (an error will occur). However if someone is sharing the files manually then its always a possibility that the map can be unpublished by accident.