From 1ff687f482af087ef04dc24bdd7bdbef6ef7acc0 Mon Sep 17 00:00:00 2001
From: Vera Aguilera Puerto <gradientvera@outlook.com>
Date: Fri, 4 Mar 2022 17:00:35 +0100
Subject: [PATCH] FlammableComponent has an empty Damage field by default.
 Prevents NRE exceptions when admemes are involved, etc?

---
 Content.Server/Atmos/Components/FlammableComponent.cs | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/Content.Server/Atmos/Components/FlammableComponent.cs b/Content.Server/Atmos/Components/FlammableComponent.cs
index 27c60cfe28..7c1799cd71 100644
--- a/Content.Server/Atmos/Components/FlammableComponent.cs
+++ b/Content.Server/Atmos/Components/FlammableComponent.cs
@@ -1,9 +1,4 @@
-using System.Collections.Generic;
-using Content.Server.Atmos.EntitySystems;
 using Content.Shared.Damage;
-using Robust.Shared.GameObjects;
-using Robust.Shared.Serialization.Manager.Attributes;
-using Robust.Shared.ViewVariables;
 
 namespace Content.Server.Atmos.Components
 {
@@ -32,6 +27,6 @@ namespace Content.Server.Atmos.Components
 
         [DataField("damage", required: true)]
         [ViewVariables(VVAccess.ReadWrite)]
-        public DamageSpecifier Damage = default!;
+        public DamageSpecifier Damage = new(); // Empty by default, we don't want any funny NREs.
     }
 }