Merge pull request #104 from alex-williams/issue_678_multicannon_fall_off

Adjusted fall-off value for all MC's to 2km where they should be…
Adjusted fall-off value for all MC's to 2km where they should be, from 1.8km, except the 'enforcer' which has no fall off. As there is no current way to suggest infinity/no fall-off, I have set this to 4.5km, which is its maximum range and therefore, more accurate than infinity anyway. This lines up with Cannon fall-off figures, which are also set to their maximum range, rather than infinity.
2025-12-08 15:13:23 +00:00 · 2024-05-14 16:57:56 -04:00 · 2024-05-14 16:42:34 +01:00
1 changed files with 11 additions and 11 deletions
--- a/modules/hardpoints/multi_cannon.json
+++ b/modules/hardpoints/multi_cannon.json
@@ -15,7 +15,7 @@
      "distdraw": 0.06,
      "edID": 128049455,
      "eddbID": 867,
-      "falloff": 1800,
+      "falloff": 2000,
      "fireint": 0.13,
      "grp": "mc",
      "id": "23",
@@ -46,7 +46,7 @@
      "distdraw": 0.07,
      "edID": 128049459,
      "eddbID": 869,
-      "falloff": 1800,
+      "falloff": 2000,
      "fireint": 0.12,
      "grp": "mc",
      "id": "24",
@@ -77,7 +77,7 @@
      "distdraw": 0.03,
      "edID": 128049462,
      "eddbID": 871,
-      "falloff": 1800,
+      "falloff": 2000,
      "fireint": 0.14,
      "grp": "mc",
      "id": "25",
@@ -108,7 +108,7 @@
      "distdraw": 0.12,
      "edID": 128671345,
      "eddbID": 1481,
-      "falloff": 1800,
+      "falloff": 4500,
      "fireint": 0.23,
      "grp": "mc",
      "id": "e0",
@@ -141,7 +141,7 @@
      "distdraw": 0.11,
      "edID": 128049456,
      "eddbID": 868,
-      "falloff": 1800,
+      "falloff": 2000,
      "fireint": 0.14,
      "grp": "mc",
      "id": "26",
@@ -172,7 +172,7 @@
      "distdraw": 0.14,
      "edID": 128049460,
      "eddbID": 870,
-      "falloff": 1800,
+      "falloff": 2000,
      "fireint": 0.13,
      "grp": "mc",
      "id": "27",
@@ -203,7 +203,7 @@
      "distdraw": 0.06,
      "edID": 128049463,
      "eddbID": 872,
-      "falloff": 1800,
+      "falloff": 2000,
      "fireint": 0.16,
      "grp": "mc",
      "id": "28",
@@ -234,7 +234,7 @@
      "distdraw": 0.18,
      "edID": 128049457,
      "eddbID": 1541,
-      "falloff": 1800,
+      "falloff": 2000,
      "fireint": 0.17,
      "grp": "mc",
      "id": "7k",
@@ -265,7 +265,7 @@
      "distdraw": 0.25,
      "edID": 128049461,
      "eddbID": 1543,
-      "falloff": 1800,
+      "falloff": 2000,
      "fireint": 0.15,
      "grp": "mc",
      "id": "7l",
@@ -327,7 +327,7 @@
      "distdraw": 0.24,
      "edID": 128049458,
      "eddbID": 1542,
-      "falloff": 1800,
+      "falloff": 2000,
      "fireint": 0.33,
      "grp": "mc",
      "id": "7n",
@@ -359,7 +359,7 @@
      "distdraw": 0.37,
      "edID": 128681996,
      "eddbID": 1546,
-      "falloff": 1800,
+      "falloff": 2000,
      "fireint": 0.297,
      "grp": "mc",
      "id": "7o",
Author	SHA1	Message	Date
David Sangrey	cfaeb70a1f	Merge pull request #104 from alex-williams/issue_678_multicannon_fall_off Adjusted fall-off value for all MC's to 2km where they should be…	2024-05-14 16:57:56 -04:00
Alex Williams	7e58828577	Adjusted fall-off value for all MC's to 2km where they should be, from 1.8km, except the 'enforcer' which has no fall off. As there is no current way to suggest infinity/no fall-off, I have set this to 4.5km, which is its maximum range and therefore, more accurate than infinity anyway. This lines up with Cannon fall-off figures, which are also set to their maximum range, rather than infinity.	2024-05-14 16:42:34 +01:00