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.

Leaderboard

Popular Content

Showing content with the highest reputation on 06/03/2024 in Posts

  1. View File A Passage to Pakistan, May 1984. Hypothetical Scenario. A Passage to Pakistan, May 1984. Hypothetical Scenario. A Harpoon Commander's Edition scenario for EC2003 Battle for the Middle East Battleset and the HCDB2-170308 new standard 1980-2025 Platform Database. This scenario is designed with advanced Scenario Editor and to be run with HCE 2015.008+ or later. This scenario is designed to be played from the Blue/US-Pakistani side or from the Red/Indian side. You should play a few times first the Blue side to avoid spoilers, and only later play the Red side. Image: The US Navy guided missile destroyer USS Kidd (DDG-993) underway on November 1, 1982, before her year long New Threat Upgrade (NTU) modernization completed September 1989, adding a long range air search radar SPS-49(V)5 in the foremast and replacing Standard SM-1MR by SM-2MR, and other changes. Later commissioned on November 3, 2006, as Taiwanese ROCS Tso Ying (DDG-1803) and yet in service. Photo by an US serviceperson on duty, and in consequence on public domain, took from Wikipedia Commons. This scenario is inspired and based in the Article by Paul French "Harpoon Scenario: Indian Interception", published in the Harpoon SITREP 66, April 2024. The initial idea is very simple (read SITREP 66 for more details): very limited US and Pakistani forces should escort three merchants loaded with vital and urgent assets from the Gulf of Aden to near Karachi in a limited time. Its task must be prevented by Indian forces. Good sailing and good luck. Enrique Mas, June 2, 2024. Submitter broncepulido Submitted 06/02/2024 Category Middle East  
  2. It's been a long time since I timed out with no side meeting minimums VCs. Quite a good fun little scenario Broncepulido, I'll keep better eye on my AA screen next go (helo got my best sub as Kidd ran out of forward SAMs)
  3. Notes on some platforms: - Indian Ka-25BSh helicopter entry 8633 lacks the carrier capable flag in the DB, can't be used on ships. I employed instead USSR Ka-25BSh helicopter entry 8632. - Indian Vikrant 91 ship entry 2390 is incapable to operate Alize ASW aircrafts, lacks the Small Aircraft flag runway (or mostly all the Alizes should be classified as STOL aircrafts). I employed instead the very similar Australian HMAS Melbourne 80 ship entry 3516. - US Kidd-class DDG should be equipped at this date (1981 to 9/1989, pre-NTU upgrade) with SM-1MR missiles, and not with SM-2MR (and devoid of SPS-49 radar). Could be employed the equivalent mounts number 61006 and 61007 employed by the Virginia (82) CGN, ship entry number 3974. - Paul French remembers on his original article Indian Alizes were without ASW capability from 1982. On this scenario is employed the Indian Alize aircraft entry 11587, as if that capability was emergency restated, but basically for more gameplay. Could be used French Alize 97 aircraft entry 11173 devoid of ASW capabilities, but as explained above is for more gameplay. - Indian Sea Harrier Mk51 83 aircraft entry 10499 is replaced with British Sea Harrier FRS.1 81 aircraft entry 11033, with very limited strike and air-to-air capabilities, as the Indian ones in 1984 (the main difference is only the use of AIM-9G in lieu of Magic I).
  4. I got the same result. The procedure to reproduce appears to be: Launch a group with atleast 2 units each unit of at least 2 plane. After they are formed up either; 1/ order group land then split the group into two groups each of one unit or at least 2 planes or 2/ split group and order to land at least the original group (now a single unit or more than 1 plane) THEN at a point after the first plane of the original group has landed, but not the complete group, save the game. When the game is opened the original group will NOT continue to land planes. The group created by the split doesn't seem to be effected, it does'nt seem to matter what order the RTB and group split orders are executed. I tested using Erics files as a start and used GE 2024.002

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.