Skip to content
View in the app

A better way to browse. Learn more.

HarpGamer

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

kmart494

Members
  • Joined

  • Last visited

Everything posted by kmart494

  1. I fixed the turn files. Please download them again.
  2. Ok. FMP for the Iranian F-4 is listed as 660kts (per Sitrep #48). Since I screwed up the F-4 position, I was going to throw you a bone by letting them go AB and catch up to the Harpoons. I can put them back at FMP if you like.
  3. Your missiles should have reached their targets by now. You have lost contact with them. The helo radar indicates two of the Red ships have speed changes. You have a new air contact on 3D radar. turn_1607_25_blue.txt turn_1607_25_blue_intl.txt
  4. Palang fires her guns at the incoming missile but misses. The missile cruises by the ship, but barely. The missile does not appear to be coming back toward you. Joshan fires her guns at the incoming missile but misses. The missile impacts the ship with a massive explosion. The ship's forward speed has stopped and will sink below the waves at 1628. Gorz fires her guns at the incoming missile but misses. The missile impacts the ship with a massive explosion. The ship's forward speed has stopped and will sink below the waves at 1634. Because the F-4 is less than 60% loaded, I will accelerate it using afterburners. The helo continues toward S008 with radar on. turn_1607_25_red.txt turn_1607_25_red_intl.txt
  5. I apologize for not correctly identifying the signature size of red surface contacts. S010 and S012 should be VSmall.
  6. Tactical Turn 1603 was the turn of launch. No missile movement will occur in that turn since the movement phase has already passed. The launch position is actually 1606 due to launching taking place after 3 minutes of ship movement in the 1603 turn. This turn, 1606.0, is an Engagement Turn and the missiles have only moved for 15 seconds (first movement phase). It's a peculiar way the paper rules deal with invoking a change in turn types. No funny business here!
  7. Dylan, I apologize for misunderstanding your intentions. I calculated it would take 3 minutes for the F-4s to catch up to the fleet, so I was going to move them in 3 minutes before missile launch to maximize stealth and surprise.
  8. You have new air contacts on radar. You also have new ESM bearings. turn_1606_blue.txt turn_1606_blue_intl.txt
  9. The missile contacts have disappeared from the radar scopes. Palang is beginning the ordered turn. Both FFs have fired their Harpoon missiles. They will begin their turns in the next movement phase. turn_1606_red.txt turn_1606_red_intl.txt
  10. Ok. I thought there was an option for the Sov to fire them with a director.
  11. I thought you wanted them to stay out of radar range at Low altitude until the ships were in firing position. The ships have another 6 nm to go. Do you want them to move closer now?
  12. I will let you keep track of which launchers they came from.
  13. Your air search radars are picking up several new contacts around the lead convoy ship. turn_1603_red.txt turn_1603_red_intl.txt
  14. The enemy surface ships have crossed the 30 nm "line in the sand." Stokiy has fired 3 SS-N-22 missiles (one each at the Red ships). At this range, the I/TARH system must be used vs. the weapon directors. Ladnyy briefly sprinted at 19 kts but is now at 16 kts. The current position may pose a weapons danger space for Stokiy. turn_1603_blue.txt turn_1603_blue_intl.txt
  15. Your data for the SS-N-14d is accurate. Also, please note it has a ballistic flight. It fires and flies at Low before going to VLow near the target. So, you guys want the merchants to turn to 240T. I am confused about the warship headings and speed.
  16. It looks like you may not be able to fire more than 3 SM1s due to launcher firing arcs. I would like you to double check that, please.
  17. The Hormone is climbing with its radar on as it circles the convoy. You have several new surface contacts. Also, the Red helo contact has descended to VLow altitude. EDIT: I meant Red helo, not Blue. turn_1557_blue.txt turn_1557_blue_intl.txt
  18. You have a new air contact and ESM bearings. The contact is automatically classified as Blue due to the overwhelming ESM evidence. I want to clarify the attack sequence: DD - fire SM1s at 24 nm at first merchant in line behind the Sov, FFs - fire harpoons at same time as SM1 at the Sov. F-4s - follow harpoons and attack Sov AB-204 - follow harpoons and attack Sov Sound right? Will the F-4s attempt a VLow attack run? If so, the speed is critical to the NOE/VLow crash table. turn_1557_red.txt turn_1557_red_intl.txt
  19. The game advanced a few more minutes past this time. You didn't hear from me because I was interacting with Red side. Still, I will put your helo up ASAP.
  20. Ok. Turns out I had the helo at VLow for detection purposes anyway, so the enemy did not see its launch point.
  21. I can put it at VLow. I just re-read VLow movement rules and helos are exempt from the crash table.
  22. I was using engagement turns to get the aircraft/helo ranges as close as possible. Blue player has not reacted to you yet. So, if you want to continue with the original plan, then you still have the ability to do so.
  23. The F-4 group is at 55 nm from the Sov, the helo is about 15 nm away, and the surface fleet is just outside the pre-planned Harpoon firing range of 30 nm. I am now using Engagement Turns. Do you guys have any last minute changes or regrets? turn_1554_5_red.txt turn_1554_5_red_intl.txt
  24. Your air search radar is picking up a contact. turn_1545_blue.txt turn_1545_blue_intl.txt

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.