From 927741ea33054f0e8fa9d4d6ad68a8a7e4a426e6 Mon Sep 17 00:00:00 2001 From: "polyxenitopalidou@gmail.com" Date: Wed, 25 Jul 2012 18:44:06 +0000 Subject: [PATCH] =?UTF-8?q?=E2=80=A2Zere=20vill=20be=20order=20in=20mein?= =?UTF-8?q?=20FEA?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit git-svn-id: http://tgstation13.googlecode.com/svn/trunk@4173 316c924e-a436-60f5-8080-3fe189b3f50e --- code/FEA/FEA_system.dm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/FEA/FEA_system.dm b/code/FEA/FEA_system.dm index 9e2c7f38122..f50afad32d8 100644 --- a/code/FEA/FEA_system.dm +++ b/code/FEA/FEA_system.dm @@ -8,7 +8,7 @@ Why are you archiving data before modifying it? This prevents abnormalities like air/fire spreading rapidly in one direction and super slowly in the other. Why not just archive everything and then calculate? - Efficiency. While a for-loop that goes through all tils and groups to archive their information before doing any calculations seems simple, it is + Efficiency. While a for-loop that goes through all tiles and groups to archive their information before doing any calculations seems simple, it is slightly less efficient than the archive-before-modify/read method. Why is there a cycle check for calculating data as well?