From eab5c8c2ada667f2663c86f9c40ef6cacf86c32a Mon Sep 17 00:00:00 2001 From: wrexbe <81056464+wrexbe@users.noreply.github.com> Date: Sun, 28 Nov 2021 22:26:10 -0800 Subject: [PATCH] Don't log empty radiation/explosion damage (#5610) --- Content.Shared/Damage/Components/DamageableComponent.cs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Content.Shared/Damage/Components/DamageableComponent.cs b/Content.Shared/Damage/Components/DamageableComponent.cs index 82c87b802a..74388a6253 100644 --- a/Content.Shared/Damage/Components/DamageableComponent.cs +++ b/Content.Shared/Damage/Components/DamageableComponent.cs @@ -98,7 +98,7 @@ namespace Content.Shared.Damage var actual = EntitySystem.Get().TryChangeDamage(OwnerUid, damage); // should logging be disabled during rad storms? a lot of entities are going to be damaged. - if (actual != null) + if (actual != null && !actual.Empty) EntitySystem.Get().Add(LogType.Radiation, $"{Owner} took {actual.Total} radiation damage"); } @@ -123,7 +123,7 @@ namespace Content.Shared.Damage var actual = EntitySystem.Get().TryChangeDamage(OwnerUid, damage); // will logging handle nukes? - if (actual != null) + if (actual != null && !actual.Empty) EntitySystem.Get().Add(LogType.Explosion, $"{Owner} took {actual.Total} explosion damage"); } }