chillcog/SPT-Server-Build
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added handling of SHOOTING_RANGE_MARK to AddHideoutCustomisationUnlock() Resolves #339

Browse Source
This commit is contained in:
Chomp
2025-06-02 09:43:03 +01:00
parent 360a59a585
commit c42449b150
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Libraries/SPTarkov.Server.Core/Helpers/ProfileHelper.cs
+4 -1
View File
@@ -683,7 +683,7 @@ public class ProfileHelper(
if (fullProfile?.CustomisationUnlocks?.Any(u => u.Id == reward.Target) ?? false) if (fullProfile?.CustomisationUnlocks?.Any(u => u.Id == reward.Target) ?? false)
{ {
_logger.Warning($"Profile: {fullProfile.ProfileInfo.ProfileId} already has hideout customisaiton reward: {reward.Target}, skipping"); _logger.Warning($"Profile: {fullProfile.ProfileInfo.ProfileId} already has hideout customisation reward: {reward.Target}, skipping");
return; return;
} }
@@ -722,6 +722,9 @@ public class ProfileHelper(
case CustomisationTypeId.ENVIRONMENT_UI: case CustomisationTypeId.ENVIRONMENT_UI:
rewardToStore.Type = CustomisationType.ENVIRONMENT; rewardToStore.Type = CustomisationType.ENVIRONMENT;
break; break;
case CustomisationTypeId.SHOOTING_RANGE_MARK:
rewardToStore.Type = CustomisationType.SHOOTING_RANGE_MARK;
break;
default: default:
_logger.Error($"Unhandled customisation unlock type: {matchingCustomisation.Parent} not added to profile"); _logger.Error($"Unhandled customisation unlock type: {matchingCustomisation.Parent} not added to profile");
return; return;