Update PA admin warnings (#28911)

With singulo fixed, PA strength 3 and below (level 2) are now safe.
Update the admin logging to reflect this.

(cherry picked from commit dc0327c3c0c7834823aeaf7e11eef6993e5fdc77)
This commit is contained in:
Partmedia
2024-06-13 12:15:15 +10:00
committed by Spatison
parent 044e0d1dc0
commit e93f886ff7
2 changed files with 5 additions and 6 deletions

View File

@@ -160,11 +160,10 @@ public sealed partial class ParticleAcceleratorSystem
var impact = strength switch
{
ParticleAcceleratorPowerState.Standby => LogImpact.Low,
ParticleAcceleratorPowerState.Level0 => LogImpact.Medium,
ParticleAcceleratorPowerState.Level1 => LogImpact.High,
ParticleAcceleratorPowerState.Level2
or ParticleAcceleratorPowerState.Level3
or _ => LogImpact.Extreme,
ParticleAcceleratorPowerState.Level0
or ParticleAcceleratorPowerState.Level1
or ParticleAcceleratorPowerState.Level2 => LogImpact.Medium,
ParticleAcceleratorPowerState.Level3 => LogImpact.Extreme,
};
_adminLogger.Add(LogType.Action, impact, $"{ToPrettyString(player):player} has set the strength of {ToPrettyString(uid)} to {strength}");

View File

@@ -108,7 +108,7 @@ public sealed partial class CCVars
/// Minimum particle accelerator strength to create an admin alert message.
/// </summary>
public static readonly CVarDef<int> AdminAlertParticleAcceleratorMinPowerState =
CVarDef.Create("admin.alert.particle_accelerator_min_power_state", 3, CVar.SERVERONLY);
CVarDef.Create("admin.alert.particle_accelerator_min_power_state", 5, CVar.SERVERONLY); // strength 4
/// <summary>
/// Should the ban details in admin channel include PII? (IP, HWID, etc)