Ukraine rebels, flattops and battlewagons, ISIS-hunting and Desert Storm nukes: Nine new Command scenarios available

April 9, 2015 · Posted in Command · Comment 

IowaMiguel Molina has posted a new revision of the Command community scenario pack, the compendium of Command scenarios crafted by the user community. The new release contains nine brand-new scenarios:

  • They Came From The Museum, 2015: Soviet/Russian tactical aircraft have a long history of ‘inexplicably’ showing up in various conflicts under the hands of ‘rebel’, ‘advisor’ and otherwise non-official pilots. This scenario assumes that the “little green men” in Ukraine take this strong tradition one step further and piece together a hodgepodge air force from various odd sources, including a number of exhibits from the Luhansk Air Museum. How will these Cold War cast-offs and their mysterious pilots fare against Ukrainian air defences?
  • The Battle of Langkawi, 1973: By 1973, the communist insurgency that erupted in Malaysia has taken control of most of the state of Kedah.  They have captured a number of artillery pieces, armored cars, and other military equipment, including a number of aircraft. An international coalition, led by the UK, and including forces from Australia, New Zealand, and Singapore are assisting Malaysia in its fight against the insurgents. However, the Soviet Union, China, India, North Korea, and Cuba have all  recognized the self-declared People’s Republic of Kedah – and will actively assist it against blockades of its ports in the Kedah region, including the island of Langkawi.
  • The Clash Of Titans II, 2018:  India started the year with intensive naval activity in both Indian Ocean and Arabian sea. The brief Indian incursion into littoral waters of French island Reunion was condemned by French diplomacy. Further diplomatic tension eventually resulted in a double embargo between France and India. A week ago, the French CVBG led by the Charles De Gaulle CV left Toulon naval base and headed to Suez. INS Vikramaditya with its escorts was ordered to head towards the Gulf Of Aden. Politics will continue by other means from now on.
  • Closing the Kurile Gap (The War That Never Was) – US, 1989: The Soviet Pacific Fleet would have faced a difficult problem with geography if the Cold War ever went hot. Their largest base, Vladivostok, faces the Sea of Japan. Any units transiting to the Pacific either need to pass through the narrow Tsushima Strait, flanked by likely-hostile South Korea and Japan, or they need to head northwest and pass through the disputed Kurile Islands. The other major Soviet naval base, Petropavlovsk, opens to the Pacific. However, it is located at the end of the remote Kamchatka peninsula and has long, vulnerable supply lines. This scenario examines the Soviet Pacific Fleet’s ability to break out through the Kuriles, and the US Navy’s role in plugging the gap.
  • Closing the Kurile Gap (The War That Never Was) – USSR, 1989: The Soviet side of the above scenario.
  • Those Who Face Death, 2014: In this hypothetical “from the headlines” scenario ISIS has captured much more intact military equipment from the Iraqi and Syrian Armies; they also have the technical capabilities to put it to use. Expect to see American, Iraqi, Syrian, Iranian military equipment. You are hunting a convoy of artillery and APCs heading to Mosul from the south before turning west towards the Yazidi camp at Mount Sinjar. You will need to airdrop supplies and parachutists to the Yazidi camp to achieve success. You are sending British and American aircraft from bases in Turkey, Kuwait, and Cyprus.
  • Log Bridge, 1989: World War III has been raging. The fighting over Keflavik has been so heavy that what remains of the airfield, currently held by NATO, is unusable.  At the same time, the fighting in Europe has pl aced demands upon available resources that preclude either side sending long range aircraft to attack or defend Iceland.  The fate of Iceland will therefore be decided by a decisive surface battle. The big guns are coming out – literally.
  • Nuclear Storm, 1991: Desert Storm is underway, and the unthinkable has happened: Saddam’s forces have launched chemical attacks on coalition troops, with significant casualties. Now a retaliation is in order – to illustrate within limits that some lines are not to be crossed.
  • No Time for Mischief, 1995: Mischief Reef is in a disputed area of the South China Sea.  In 1995, China angered the Philippines by occupying the reef and constructing structures on it, ostensibly as shelters for fishermen.  In history, the matter did not escalate into violent confrontation. This scenario assumes the government of the Philippines has taken a more aggressive approach, assuming that if worst comes to worst they will be backed up by the United States.

As always, the community scenario pack is available for download at the WarfareSims download section:

Happy Easter! 30% off on Command and any other MatrixGames title

April 4, 2015 · Posted in Command · Comment 

MatrixGames has a generous 30% sale on any single game until April 7th. Don’t miss it!

Covert sub ops, water wars, nuclear feints and Chinese disarming strike: Five new Command scenarios available

March 13, 2015 · Posted in Command · Comment 

J16Miguel Molina has posted a new revision of the Command community scenario pack, the compendium of Command scenarios crafted by the user community. The new release contains all existing scenarios updated to the latest databases accompanying the v1.07 release, plus five brand-new scenarios:

  • Probe of Feint, 1963: As Red China edges closer to a usable nuclear weapon, many actors, including the United States, watch with increasing alarm. Eventually pre-emptive action is decided upon – but in a way that will not be obvious…
  • Water Wars, 2017: For over 100 years Bolivia has tried to reacquire territory  lost to Chile in a series of conflicts in the late 19th century, particularly the valuable province and port of Antofagasta, which provides access to the Pacific. In December of 2015 the ICJ delivered a shocking verdict that Chile had illegally acquired the land from Bolivia and must provide them sovereign access to the sea in the form of a “national corridor” some 20kms wide.  Chile immediately responded negatively. In retaliation, Bolivia built a dam diverting the Silala river, a waterway vital to Chilean economy. The matter will no longer be settled on the courts or negotiating tables…
  • Angamos Goes The Distance, 1980: A Peruvian submarine must conduct a covert extraction of Peruvian government personnel (i.e. spies) from Chile. The Chilean navy will shoot unidentified intruders first and ask questions later.
  • Andaman Sea Clash, 2005: In 2004, tensions between Thailand and Myanmar increased.  During the summer of that year, a Thai fishing boat was sunk by a Burmese patrol boat. Seven months later tensions have remained high and Thailand has started to conduct regular patrols in the Andaman Sea to protect Thai fishing boats.  Myanmar has not protested this action, but has made it clear that it will not tolerate Thai fishing boats violating its territorial waters or its protected fisheries.
  • Operation Fei Lian, 2019: The baloon is going up in the Korean peninsula – but it’s not the conflict that everyone planned and prepared for. Radical elements of the North Korean military are attempting a coup, and back-channel talks with the Chinese leadership lead to Beijing decide to support the rebels. As the General in command of the Shenyang military district, you are ordered to destroy the North Korean air force as well as the NK “strategic” nuclear forces, using the PLAAF assets in your command.

As always, the community scenario pack is available for download at the WarfareSims download section:

Lucky Seven: Command v1.07 has been released

March 9, 2015 · Posted in Command · Comment 

NORADCommandCenterSo, the cat is officially out of the bag. The full release notes are available here.

We’ve talked extensively about the significant enhancements that the new v1.07 update brings to Command, but here’s a quick refresher on the biggies:

  • Weapon Release Authorization (WRA): All the endless arguments about how the AI pilots should double-tap MiG-29s while using cheap ammo against easy targets (etc. etc. etc.) are officially over. You are now in complete control. So no excuses when the enemy whips you :)
  • Mission Editor 2.0: Putting up a complex multi-group, multi-axis strike package is now easier than ever. The enemy AI may also use this against you ;). Plus a lot more customization options for all mission types.
  • Scenario Attachments (aka auto-bundling): Hesitant to spice up your scenario with map overlays etc. because so far it required manual action by the player? No more. Map graphics, custom Lua scripts, import files and even more attachment types coming soon. Get cracking!

Some smaller but also significant bits in this release as well:

  • Tons of UI enhancements such as discrete range rings for anti-ship and land-attack weapons, even more hotkeys, redesigned manual weapon allocation window, contact filter-out (even more map declutter) and much more.
  • Lots and lots of additional Lua scripts.
  • Better performance on scenarios that use zones (ie. most scens out there).
  • Massive overhaul of AAW missile endgame logic; target speed matters more, and the evasion bonus must now be earned instead of automatically granted.
  • Bigger effect of crew proficiency on damage control & underway repairs (remember the Shinano?)
  • Improvements to submarine battery recharge rates.

Plus of course the customary mile-long list of small fixes, DB additions and tweaks.

And we’re not over yet…

New in v1.07: Scenario Attachments (a.k.a. auto-bundling)

February 16, 2015 · Posted in Command · Comment 

prod_icon256Ever since Command’s initial release, the players have been asking us for an automated, reasonably idiot-proof way of bundling various content items (primarily map overlays but also other types) together with their scenarios and have them referenced correctly regardless of the scen file’s actual location.

Scenario Attachments, a.k.a. auto-bundling, is our response to this request. It is one of the flagship new features of the v1.07 update.

Scenario attachments are “things” (anything from a single file to a massive directory tree) that you can provide as attachments to a scenario (similar to attaching a file to an email message) and then use them via a new Lua command “ScenEdit_UseAttachment”. What exactly happens when you use them obviously depends on the attachment type. When a scenario packaged with attachments is loaded, its attachments are transparently copied to the local repository and can then be re-used on any other scenario (much like .inst files). The use of a single-point repository solves the “I moved my scen file around and now it cannot find its attachments” problem (this may be familiar to anyone who moves saved web pages around in the file system without their accompanied images etc.).

Here is a concrete example:

a) Author-A constructs a scenario and wishes to enrich it with imagery of an area. From the “Editor” menu, he selects “Scenario Attachments”. This brings up a window listing the attachments currently associated with the scenario:

Here we see we can construct a new attachment, use an existing one or modify (rename/delete) any already on the repository. Clicking on the “Create new of type: [...]” will prompt us to locate the source material for the attachment, in this case a geo-referenced image file (map overlay). Clicking on “use existing” brings up another window which lists all attachments already available on the local repository:

Selecting the desired attachment and clicking on “Use selected” will add the attachment to the scenario.

We can then select, from the “Editor” menu, the command “Package scenario for distribution”. A file-dialog will pop up to prompt us for where to save the packaged scenario file. The “packaging” is essentially the process of properly bundling the scenario with the selected attachments on a single zip file, so that they can be correctly identified and loaded (automatically) by end users.

Author-A then distributes the bundled scenario as usual. User-A unzips the bundle file to “\Scenarios” (or anywhere else) and loads up the scenario. Under the hood, the program sees the unzipped “attachments” folder side-by-side with the scenario file and automatically copies the attachments (each one on its dedicated folder, uniquely identified with a GUID) to the user’s local repository.

To use a referenced attachment, you can use the new Lua command “ScenEdit_UseAttachment”, which accepts either an attachment’s name or its GUID. So in this case, by bundling an image overlay to a scenario and creating an “on scen load” event that triggers its use, we can display map-overlay images to the end user without any manual action of his own.

Of course this infrastructure is meant to eventually exploit multiple attachment types, ranging from media files (audio, video etc.) to pre-fab Lua scripts, arbitrary text or binary files etc.

Next Page »