Iran Strike, 2022 (Updated August 8, 2025)

[Kushan04]

One issue that still bugs me tho is that F-15As at Tel Nof AB are still using the 1995 entry of the platform although a much more recent (2021) and capable variant is available in the DB. Would be nice if that could be fixed in future versions of the scenario.

Are you using the current version? I just checked the latest beta and they are the 2021 variant.

One more thought: Maybe include a special actions option that removes most of Syrian AD/EW assets from the map to reflect the state of Syria's air defense after the fall of the Assad regime. Cheers

There's definitely some changes that I'll have to make. Going to let things settle a bit before I do anything and I've got some other things on my plate right now.

Not a bad idea for a special action. I may also just take that into account when I get around to updating the 2025 version of the scenario.

[Vici Supreme]

Are you using the current version? I just checked the latest beta and they are the 2021 variant.

Huh okay. I loaded the one scenario that was included in the steam community scenario pack, assuming it was the most recent version of the scenario. Manually downloading yours now. Thanks for pointing out!

[Kushan04]

Are you using the current version? I just checked the latest beta and they are the 2021 variant.

Huh okay. I loaded the one scenario that was included in the steam community scenario pack, assuming it was the most recent version of the scenario. Manually downloading yours now. Thanks for pointing out!

The very latest version of all my scenarios is always here on the forum. I usually, but not always, only post "betas" here to the forum and the "stable" version to Steam and the CSP.

[Nikel]

A little error in the briefing pdfs in v5, they are the 2025 files.

[Kushan04]

I've been thinking about the US strike on Fordow - using one MOP to blow the lid off and then firing other MOPs down the hole.

I think this could be done in CMO by having one aim point unit at the start, it would reward no points when destroyed. After it was destroyed, the real target facility would be created where the original aim point unit was.

Is this something that you would like to see in Iran Strike, or is that too much?

[boogabooga]

I've been thinking about the US strike on Fordow - using one MOP to blow the lid off and then firing other MOPs down the hole.

I think this could be done in CMO by having one aim point unit at the start, it would reward no points when destroyed. After it was destroyed, the real target facility would be created where the original aim point unit was.

Is this something that you would like to see in Iran Strike, or is that too much?

You can't setup a ToT strike mission that way.

How many MOPs does it take now to destroy the object(s) that represent Fordow in your scenario? As long as it takes about 14 total, I think this sort of detail is abstracted in the armor penetration mechanics.

[Kushan04]

You can't setup a ToT strike mission that way.

How many MOPs does it take now to destroy the object(s) that represent Fordow in your scenario? As long as it takes about 14 total, I think this sort of detail is abstracted in the armor penetration mechanics.

I've been thinking about this concept a little more. Don't think I'm going to put it into Iran Strike (for now anyway). I think the scale of Iran Strike is to high for that sort of detail. As yopu suggested, I'll double check the numbers so the approximate numbers of MOPs used is represented. May need to increase the number of B-2s as well, can't remember what the cap is off the top of my head.

I do plan to explore this idea further in a dedicated Midnight Hammer scenario. To get around the ToT issue, I think there could be two units on top of each other. The "cover" unit and a generic aim point. The generic aim point would allow you to plan the ToT strike. When the cover unit is destroyed, it would be swapped for the now exposed lower unit. I think I may be able to have a script that will get any mission the aim point is assigned to and then reassign the new unit to it/them. In theory since the location is the same, nothing else should need to be done. If I can get that to work, would that be acceptable?

[Kushan04]

Decided to redo the setup menu. I wanted to reduce the complexity but maintain all of the same options/settings. Need to make the category segments more clear - probably make the header text larger and make the border lines thicker.



I simplified the selection for Iranian Aircraft/SAMs/Radars. All of the same options are still available but instead of having a selection for every combination, you select what combination of settings you want. The glossary sections contain additional information on the various settings and like the Gameplay Notes can be expanded/collapsed. There are fail safes in place to prevent trying to upgrade/place units while not having any options selected.

[Knightpawn]

That looks great. Is it a custom set up menu coming with the scenario itself?

[Kushan04]

That looks great. Is it a custom set up menu coming with the scenario itself?

Yes, it's already in the latest beta updates, along with the deployment map when playing as the US and US-Israel sides. Dotting some I's and crossing some T's, then I'll post it to the CSP and update the Steam version.

[Kushan04]

Posted the next v5 beta. Unless something comes up this week, this will be final and I'll post it to Steam later this week.

Change Log:
• Updated scenario to DB512.
• Updated possible Iranian SAM options.
• Added Iranian nuclear facilities to the USA and USA-Israel deployment menus. This is intended to aid in planning by providing basic facility information - description, facility type, and components.
• Revised Scenario Setup and Israel Political and Strategic Actions menus. The menus have been simplified while maintaining all of the options in previous versions.
• Added new scenario setup option to control the presence of the Syrian IADS. Only relevant when playing as Israel or USA-Israel sides, the Syrian IADS has always been removed when playing as the USA.
• Added new scenario setup option to control the density of AAA and SAMs.
• Reworked random SAM placement to have better distribution between medium and long-range systems.

[Kushan04]

One more very minor update.

Version 5.0.0 Beta 11 (July 29, 2025):
• Fixed F-15C deployment to Ali Al Salem Air Base.
• Re-added Muwaffaq Salti Air Base when playing as the USA or USA-Israel and using the 2024 strike option.

[Kushan04]

Found a few issues with the last beta, fixed, should have the currently final version posted Monday.

Started working on updating Iran Strike, 2025. Making some changes to the deployment map. The current iteration has the deployment information on a right side panel. This has a couple of UI annoyances. To fix it I'm thinking of doing a new popup window (similar to the enlarged map when playing as the US-Israel). After a little back and forth with ChatGPT this is what I came up with as a prototype. Depending on how it turns out, I'll eventually implement back into 2022.

[Twistedpretzel]

The beta 11 build available in the first post has a comma missing from line 6659 of "Scenario Lua initialization 05" causing the deployment menu action to fail.

local AirBases = {
{number=1, name='Prince Sultan AB', tankerFlightNo=11, tankerCallsign='MOBILE'},
{number=2, name='Al Udeid AB', tankerFlightNo=41, tankerCallsign='SHELL'},
{number=3, name='Al Dhafra AB', tankerFlightNo=AlDhafraTankerFlightNo, tankerCallsign='TEXACO'},
{number=4, name='Diego Garcia', tankerFlightNo=11, tankerCallsign='EXXON'},
[{number=5, name='Ali Al Salem AB'}
{number=6, name='Muwaffaq Salti AB'}

Edited for clarity - Should be

local AirBases = {
{number=1, name='Prince Sultan AB', tankerFlightNo=11, tankerCallsign='MOBILE'},
{number=2, name='Al Udeid AB', tankerFlightNo=41, tankerCallsign='SHELL'},
{number=3, name='Al Dhafra AB', tankerFlightNo=AlDhafraTankerFlightNo, tankerCallsign='TEXACO'},
{number=4, name='Diego Garcia', tankerFlightNo=11, tankerCallsign='EXXON'},
[{number=5, name='Ali Al Salem AB'},
{number=6, name='Muwaffaq Salti AB'}

[Kushan04]

Version 5 has been posted to the first post and Steam!

I've also posted aa demo video of the USA deployment video to YouTube: https://youtu.be/7RtEJ5SlBYo?si=rR1kRge7pvmX_tYc

The beta 11 build available in the first post has a comma missing from line 6659 of "Scenario Lua initialization 05" causing the deployment menu action to fail.

Thanks, I caught that the other day. It's been fixed.