fix: handle CurrentLoadOutIds missing LoadOuts in missionInventoryUpdate (#1421)

Reviewed-on: #1421
Co-authored-by: Sainan <63328889+Sainan@users.noreply.github.com>
Co-committed-by: Sainan <63328889+Sainan@users.noreply.github.com>

src/services/missionInventoryUpdateService.ts

@@ -414,6 +414,7 @@ export const addMissionInventoryUpdates = async (
                 break;
             }
             case "CurrentLoadOutIds": {
+                if (value.LoadOuts) {
                     const loadout = await Loadout.findOne({ loadoutOwnerId: inventory.accountOwnerId });
                     if (loadout) {
                         for (const [loadoutId, loadoutConfig] of Object.entries(value.LoadOuts.NORMAL)) {
@@ -426,6 +427,7 @@ export const addMissionInventoryUpdates = async (
                         }
                         await loadout.save();
                     }
+                }
                 break;
             }
             default:

src/types/requestTypes.ts

@@ -114,7 +114,7 @@ export type IMissionInventoryUpdateRequest = {
     UnlockWeapons?: boolean; // sent when recovered weapons from zanuka capture
     IncHarvester?: boolean; // sent when recovered weapons from zanuka capture
     CurrentLoadOutIds?: {
-        LoadOuts: ILoadOutPresets; // sent when recovered weapons from zanuka capture
+        LoadOuts?: ILoadOutPresets; // sent when recovered weapons from zanuka capture
     };
 } & {
     [K in TEquipmentKey]?: IEquipmentClient[];