OpenWF/SpaceNinjaServer
21
23
Fork 24
Code Issues 23 Pull Requests 5 Actions Packages Projects Releases Activity

chore: clarify log output related to saveLoadout
All checks were successful
Build / build (pull_request) Successful in 51s
Details

Browse Source
This commit is contained in:
Sainan 2025-07-01 10:08:13 +02:00
parent 5a5f6106a3
commit 06135e8d50
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
src/services/saveLoadoutService.ts
View File

@ -167,8 +167,13 @@ export const handleInventoryItemConfigChange = async (
inventory.LotusCustomization = equipmentChanges.LotusCustomization;
break;
}
case "ValidNewLoadoutId": {
logger.debug(`ignoring ValidNewLoadoutId (${equipmentChanges.ValidNewLoadoutId})`);
// seems always equal to the id of loadout config NORMAL[0], likely has no purpose and we're free to ignore it
break;
}
default: {
if (equipmentKeys.includes(equipmentName as TEquipmentKey) && equipmentName != "ValidNewLoadoutId") {
if (equipmentKeys.includes(equipmentName as TEquipmentKey)) {
logger.debug(`general Item config saved of type ${equipmentName}`, {
config: equipment
});
@ -216,7 +221,7 @@ export const handleInventoryItemConfigChange = async (
}
break;
} else {
logger.warn(`loadout category not implemented, changes may be lost: ${equipmentName}`, {
logger.error(`loadout category not implemented, changes will be lost: ${equipmentName}`, {
config: equipment
});
}