MM Patch Re-Ordering & Cleanup

- Fix issues with Reviva & certain MAS-supported IVAs missing MASFlightComputer, due to patch ordering in MAS
- Rename some patch file names to reflect proper MM patch ordering within passes
- Reorder some MAS patches due to relying on MASFlightComputer patch order
- Remove unnecessary NEEDS/FOR[AvionicsSystems] in some patches
- Add missing NEEDS or other pass specifiers in some mod support patches
- Rename/Relocate some mod support patch files for clarity/consistency

Author: StoneBlue

GameData/MOARdV/AvionicsSystems/MAS-NavAid.cfg

@@ -1,6 +1,6 @@
 // The MAS support piggyback patch.  Adds a generic MAS module to any part that
 // includes an RPM module.
-@PART[*]:HAS[@MODULE[RasterPropMonitorComputer],!MODULE[MASFlightComputer]]:NEEDS[AvionicsSystems]
+@PART[*]:HAS[@MODULE[RasterPropMonitorComputer],!MODULE[MASFlightComputer]]:FINAL	// Should run very late, to leave room for anything else to patch RPM first
 {
 	MODULE
 	{
@@ -23,7 +23,7 @@
 	}
 }
 
-@PART[JSIPrimitiveExternalCamera]:NEEDS[AvionicsSystems]
+@PART[JSIPrimitiveExternalCamera]:LAST[zzz_AvionicsSystems]
 {
 	MODULE
 	{
@@ -44,7 +44,7 @@
 
 // The JSI to MAS prop upgrade patch.  This Module Manager patch replaces
 // every core RPM-enabled prop with its equivalent MAS-enabled prop.
-@INTERNAL[*]:NEEDS[AvionicsSystems]
+@INTERNAL[*]:FINAL		// Should run very late, to leave room for every IVA mod/patch to run first?
 {
 	// ---=== JSI/RasterPropMonitor Props ===--- //
 

GameData/MOARdV/Patches/MAS_NavAid.cfg …ta/MOARdV/AvionicsSystems/MAS_NavAid.cfgGameData/MOARdV/Patches/MAS_NavAid.cfg renamed to GameData/MOARdV/AvionicsSystems/MAS_NavAid.cfg GameData/MOARdV/Patches/MAS_NavAid.cfg renamed to GameData/MOARdV/AvionicsSystems/MAS_NavAid.cfg

@@ -1,7 +1,7 @@
 // The ASET to MAS prop upgrade patch.  This Module Manager patch replaces
 // every ASET Avionics and ASET Props RPM-enabled prop with its equivalent
-// MAS-enabled prop.
-@INTERNAL[*]:NEEDS[AvionicsSystems]
+// MAS-enabled prop. Should run very late, to leave room for every IVA mod/patch to run first?
+@INTERNAL[*]:FINAL		//<---On patch order: what happens if another mod, patches/edits/clones a prop, and MAS applies this after?
 {
 	// TODOs found in the ALCOR IVA that may or may not be supported already.
 

GameData/MOARdV/FlightSystems/HullcamVDS-MASCamera.cfg

@@ -1,7 +1,7 @@
 // Because the RPM bridge for SCANsat uses a local persistent storage module,
 // but the SCANsat MM patch only applies to RasterPropMonitor, we need our own
 // patch here to get the persistent storage module added to our parts.
-@PART[*]:HAS[@MODULE[MASFlightComputer]]:AFTER[AvionicsSystems]:NEEDS[SCANsat]
+@PART[*]:HAS[@MODULE[MASFlightComputer&!MODULE[SCANRPMStorage]]:FINAL		// Should run very late, after JSI-to-MAS patch, due to MASFlightComputer
 {
 	MODULE
 	{

GameData/MOARdV/FlightSystems/MAS_EngineID.cfg

@@ -0,0 +1,17 @@
+// Add MASIdEngine to supported part modules.
+
+@PART[*]:HAS[@MODULE[ModuleEnginesAJEPropeller]]:AFTER[AJE]
+{
+	MODULE
+	{
+		name = MASIdEngine
+	}
+}
+
+@PART[*]:HAS[@MODULE[ModuleEnginesAJEJet]]:AFTER[AJE]
+{
+	MODULE
+	{
+		name = MASIdEngine
+	}
+}