Jump to content


  • Content Count

  • Joined

  • Last visited

About DerKommissar

  • Rank
    Inconsequential Rambler

Profile Information

  • Location:
    RL Cadia

Recent Profile Visitors

1,362 profile views
  1. I've been experimenting with my own dynamic campaign system, and I couldn't get around that you can't load/import OOBs. I believe persistent OOBs are already in the editor, and especially in the scripted campaigns. Just one button that loads an OOB from a save file into the QB force builder, would open up a world of possibilities.
  2. Just tried to play the South African campaign. Can confirm this, on my end -- as well.
  3. Thanks for sharing. Lots of historical proof for Sun Tzu's universal formula. "In reality, there are no major cities that have been destroyed by war. Groningen and Aachen — and even Berlin, Stalingrad, Hiroshima, and Carthage for that matter — were all back in business soon after being blasted to smithereens in warfighting that verged on the exterminatory. Sometimes, nature may destroy a city, but man, despite his best efforts, does not." Does he consider Warsaw destroyed after German reprisal? The elephant in the room is collateral damage. "Military operations invariably have an impact on the urban landscape — even small arms can be devastating to structures — and there is no straightforward, correct answer to whether and to what extent it is acceptable to damage a city in pursuit of a political objective." I think that's a uniquely modern problem. The political reality of today is that the effect of any firing solution can be recorded and reported. The practical reality is that artillery and precision bombing are fundamental tools against a fortified defender. The defender can use civilian infrastructure as a human shield, and blame any collateral damage on the attacker. It's a catch 22: follow rules of strict engagement, relinquish your force multipliers and get bogged in destructive attritional warfare. Gaza, Libya, Syria and Yemen come to mind.
  4. Sure thing, bud. Appreciate the interest, and I could always use play testers. I have a couple of options: a. I can set you up with a new task force, next turn (Turns = Time of Day). This turn is half way done, as 2 out of 4 QBs have been completed. b. You can assume command of either one of the BLUFOR Task Forces, next turn. I already fought their respective, generated, QBs. c. Take control of one of the REDFOR Task Forces in QB. I haven't started playing Task Force C or D, but their QB settings are ready to go.
  5. Open image in new tab to see OOB details. Note that the 3 cannon support won in the Operational layer are added on top of the UKR Task force Point pool. 6391+871 = 7262 Breakthrough! A stunning success by the UKR Task Force. HQ will be pleased. Net Points Gained = 1000 - 118 = 882
  6. Just when I was looking into presents for my younger brother. How good is the quality of the plastic? I've got bad memories of bad-fitting Megablocks.
  7. US Task Force A AAR The Player can determine the size of the Battle and the Battlefield in the QB Menu. Other factors are dependent on Actions, Operational Map and Conditions. Legend: Green options are chosen by the Player. Blue options are chosen by the Operational Map. Orange options are chosen by the Day's Forecast. Red Options are chosen by the success of Actions. The US Task Force A Player picks 6400 Points worth of Forces and 473 Points worth of Fortifications. They decide to keep their 1 Apache Support, for now. The Defensive has been a minor success. The Net Points (412 - 205 = 207) will added to the Task Force A Player's Point pool, as well as the accomplishment of Operational Objective 1. In the event of a defeat, the Net Points are negative and will be subtracted from the Player's Points, as well as the Objective's success.
  8. US Task Force A Plan(7000 – 600 = 6400 Points) *These are the Player's orders. Everyone starts with 7000 Points, in this Campaign. This can be spent to accomplish operational tasks like requesting support, digging in, logistics, movement or securing the perimeter. The remaining amount of Points (6400) is the maximum amount of points used to purchase forces in Quick Battle, for the Player's side.* Orders: Defend Area 1 *The Player picks an Operational Objective to pursue. Their Victory Points in Quick Battle will contribute to its completion.* Actions: *The Player plans out their Operational actions here. They can pick as many as they want, and invest any number of Points in their success.* 1. Request Attack Helicopter Support (x2) (400 points) *US Player has decided to bid 400 of their total Points into obtaining a support of 2 Apaches in 1 Quick Battle.* DC: 800. Roll: 343 + 400 = 743/800 *The GM decides the Difficulty Check, which determines how high the roll must be to ensure the Player's success. The Player's invested points are added on top. For this one the roll is between 1 to 800, and the Player must get 800 for a full success.* Obtained 1 Apache support for 1 battle *The GM declares the result of the Action. The result was a partial success.* 2. Construct Fortifications (200 points) *The Player can invest in digging in.* DC: 400. Roll: 273 + 200 = 473/400 *Digging in is easier than receiving attack helicopter support.* Obtained 473 points worth of Fortifications for 1 battle *The success is directly proportional to the outcome of the roll.* UKR Task Force B Plan(7000 – 600 = 6400 Points) *This is Player 2's plans. This would be its own post on the forum.* Orders: Attack Area 2 Actions: 1. Advance 1 kilometer (100 points). DC: 100 *Advancing a square kilometer on the map takes a Difficulty Check, as well.* Roll: 29 + 100 = 129/100 Advanced 1 Kilometer 2. Secure 2 square kilometers (200 points). DC: 400 *In order to turn the square kilometer to your side's control. A Security DC is required.* Roll: 354 + 200 = 554/400 Secured 2 square kilometers 3. Request artillery battery support (300 points). DC: 600 Roll: 513 + 300 = 813/600 *Great success!* Obtained 3 heavy guns for 1 battle *Engel Matrix is the basis for this system. The Player is encouraged to use creativity and attention to detail when laying out their plans.* RUS Task Force C Plan(7000 – 500 = 6500 Points) Orders: Attack Area 2 Actions: 1. Advance 2 kilometers North (100 points) DC: 200 Roll: 79 + 100 = 179/200 Advanced 1 Kilometer 2. Secure 4 square kilometers (400 points) DC: 800 Roll: 371 + 400 = 771/800 Secured 3 square kilometers RUS Task Force D Plan(7000 – 400 = 6600 Points) Orders: Attack Area 3 Actions: 1. Advance 2 kilometer (100 points). DC: 200 Roll: 170 + 100 = 270/200 Advanced 2 Kilometers 2. Request Close Air Support (300 points). DC: 600 Roll: 17 + 300 = 317/600 Obtained 1 Hind support Operational Map *Note: Each square kilometer is occupied by Non-Player forces, that are represented by the Faction's colour.* Legend: Light Blue: US, Dark Blue: UKR, Red: RF
  9. 11 July 2017 Dawn Forecast: TimeAndDate.com Conditions: Overcast, Dry BLUFOR Operational Objectives (roll 36-72, roll 32-66): 1: Defend Area (Grid: 39, 36) 2: Attack Area (Grid: 59, 39) 3: Defend Area (Grid: 56, 55) REDFOR Operational Objectives (roll 36-72, roll 32-66): 1: Attack Area (Grid: 68, 64) 2: Attack Area (Grid: 61, 59) 3: Attack Area (Grid: 70, 51) Operational Map (Open Image In New Tab for greater resolution)
  10. Quick Battle Campaign: Donetsk (Prototype) This is a field trial for an operation-based Quick Battle generator. After taking into consideration all the great systems that were recommended to me by the community, I've finally settled on an implementation. This thread will contain both the operational mechanics and the Quick Battle AARs. I apologize for the lack of flavour text, as this is a test. The objective of this trial is to get the balancing right, both for the QB settings and the Operational Metagame component. I'm starting this demo with 4 players (1 US, 1 UKR, 2 RF). You are welcome to participate as one of the players, and play against CPU, or a partner. If so, please post below -- as well as any questions you may have. Note: BLUFOR and REDFOR sides will be able to see eachother's "hands" in this trial. This way it is easier to compare, for balance.
  11. Thanks for the tip, I may have tested it out by sending a Bradley IFV hurling through into the enemy line. Once the FAST order was completed, they saw a tandem warhead RPG pointed at them and retreated. They survived. TCs have self-preservation instincts, apparently. Now that you mention it, in most tank combat footage I've seen (Syria, Iraq) -- AFVs almost never pop smoke. Even under fire. Be it an M1, Leo 2, BMP2 or T-72 -- they all carry smoke discharges, why not use them? Training issues are something one does not consider.
  12. I've been messing around with CM:BS Quick Battles for my campaign system prototype. When a T90 emerges from a hilltop and begins to identify targets and compute firing solution, an M1A2 SEP or a M2A2/M2A3 gets a LASER WARNING. They automatically pop IR blocking smoke and reverse. This can save your skin, as I've seen T90s penetrate M1A2's lower glacis and cupola. However, I've had AFVs reverse in a weird way that exposes their side armour to the T90s. This happens often when there are trees, buildings or the edge of the map behind my AFV. The AFV will steer to the side, and become more vulnerable as a result. Sometimes, the automatic smoke launchers are triggered for a trivial threat -- leaving those charges spent, while a serious threat approaches. Is it possible to prevent my AFVs from automatically reversing and/or popping smoke on LASER WARNINGs? Or is this immutable TC protocol IRL?
  13. In a recent quick battle, I had T90AM APS explode 3 TOW-2Bs in short succession. I've also seen top ERA stop a Javelin. They also managed to take out all three of my M1A2SEPs, which were at the back of the map, behind foliage, in low-light conditions. I've also seen a T90A destroy a Bradley, while its TOW was still in the air. Also, hidden in foliage and low-light conditions. IDK how it is from the Russian side. But from the American side, I've learned not to underestimate T90s -- especially the AM variant with APS. They're not equal to the M1A2SEPs, but they can certainly kill them. I did take screenshots, and may post an AAR -- documenting my experiences.
  • Create New...