Fix indentations (#17481)

* cbt

* AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

* fsadffsda sad

* sadfasd

* jhn

* dsfa

* saf

* safsad

* sda

code/modules/effects/_effect_system_docs.dm

@@ -1,6 +1,6 @@
 /*
 /datum/effect_system
-	var/atom/movable/holder	
+	var/atom/movable/holder
 		- The atom that this effect_system is attached to.
 	var/no_del
 		- If this effect_system should be deleted at end of processing.
@@ -14,7 +14,7 @@
 - Called when the object is queued for update. Overriding procs should call ..()
 
 /datum/effect_system/process()
-- Called when the processor processes this effect. 
+- Called when the processor processes this effect.
 	Return ..() to allow default behavior of self-destroying after one tick.
 	Alternately; EFFECT_HALT, EFFECT_CONTINUE, and EFFECT_DESTROY can be used to tell the processor what to do with the object.
 

code/modules/effects/map_effects/map_effects.dm

@@ -30,7 +30,7 @@
 /obj/effect/map_effect/interval/Initialize()
 	. = ..()
 	START_PROCESSING(SSprocessing, src)
-	
+
 /obj/effect/map_effect/interval/Destroy()
 	STOP_PROCESSING(SSprocessing, src)
 	return ..()
@@ -44,7 +44,7 @@
 	//Not yet!
 	if(world.time < next_attempt)
 		return
-	
+
 	// Check to see if we're useful first.
 	if(!always_run && !check_for_player_proximity(src, proximity_needed, ignore_ghosts, ignore_afk))
 		next_attempt = world.time + retry_delay
@@ -66,4 +66,4 @@
 			continue
 		if(M.z == proximity_to.z && get_dist(M, proximity_to) <= radius)
 			return TRUE
-	return FALSE
+	return FALSE

code/modules/effects/map_effects/portal.dm

@@ -9,27 +9,27 @@ Portals do have some specific requirements when mapping them in;
 	- Each side must face opposite directions, e.g. if side A faces SOUTH, side B must face NORTH.
 	- Each side must have the same orientation, e.g. horizontal on both sides, or vertical on both sides.
 	- Portals can be made to be longer than 1x1 with `/obj/effect/map_effect/portal/line`s,
-	  but both sides must have the same length.
+		but both sides must have the same length.
 	- If portal lines are added, they must form a straight line and be next to a portal master or another portal line.
 	- If portal lines are used, both portal masters should be in the same relative position among the lines.
-	  E.g. both being on the left most side on a horizontal row.
+		E.g. both being on the left most side on a horizontal row.
 Portals also have some limitations to be aware of when mapping. Some of these are not an issue if you're trying to make an 'obvious' portal;
 	- The objects seen through portals are purely visual, which has many implications,
-	  such as simple_animal AIs being blind to mobs on the other side of portals.
+		such as simple_animal AIs being blind to mobs on the other side of portals.
 	- Objects on the other side of a portal can be interacted with if the interaction has no range limitation,
-	  or the distance between the two portal sides happens to be less than the interaction max range. Examine will probably work,
-	  while picking up an item that appears to be next to you will fail.
+		or the distance between the two portal sides happens to be less than the interaction max range. Examine will probably work,
+		while picking up an item that appears to be next to you will fail.
 	- Sounds currently are not carried across portals.
 	- Mismatched lighting between each portal end can make the portal look obvious.
 	- Portals look weird when observing as a ghost, or otherwise when able to see through walls. Meson vision will also spoil the illusion.
 	- Walls that change icons based on neightboring walls can give away that a portal is nearby if both sides don't have a similar transition.
 	- Projectiles that pass through portals will generally work as intended, however aiming and firing upon someone on the other side of a portal
-	  will likely be weird due to the click targeting the real position of the thing clicked instead of the apparent position.
-	  Thrown objects suffer a similar fate.
+		will likely be weird due to the click targeting the real position of the thing clicked instead of the apparent position.
+		Thrown objects suffer a similar fate.
 	- The tiles that are visually shown across a portal are determined based on visibility at the time of portal initialization,
-	  and currently don't update, meaning that opacity changes are not reflected, e.g. a wall is deconstructed, or an airlock is opened.
+		and currently don't update, meaning that opacity changes are not reflected, e.g. a wall is deconstructed, or an airlock is opened.
 	- There is currently a small but somewhat noticable pause in mob movement when moving across a portal,
-	  as a result of the mob's glide animation being inturrupted by a teleport.
+		as a result of the mob's glide animation being inturrupted by a teleport.
 	- Gas is not transferred through portals, and ZAS is oblivious to them.
 A lot of those limitations can potentially be solved with some more work. Otherwise, portals work best in static environments like Points of Interest,
 when portals are shortly lived, or when portals are made to be obvious with special effects.

code/modules/effects/maze_generation/helper_modules/_helper_module_base.dm

@@ -2,13 +2,13 @@
 	name = "maze helper"
 
 /**
-  * Helper handler proc
-  *
-  * This exists as an overridable method so you can do custom helper logic.
-  * An example of this is removing all windows on a tile.
-  *
-  * Arguments:
-  * * blockwise - This will be TRUE if the maze this is running on is a blockwise maze
-  */
+ * Helper handler proc
+ *
+ * This exists as an overridable method so you can do custom helper logic.
+ * An example of this is removing all windows on a tile.
+ *
+ * Arguments:
+ * * blockwise - This will be TRUE if the maze this is running on is a blockwise maze
+ */
 /obj/effect/mazegen/module_helper/proc/helper_run(blockwise = FALSE, obj/effect/mazegen/host)
 	CRASH("spawn_loot() not overriden for [type]")

code/modules/effects/maze_generation/loot_modules/_loot_module_base.dm

@@ -4,13 +4,13 @@
 	var/spawn_probability = 0
 
 /**
-  * Loot spawner proc
-  *
-  * This exists as an overridable method so you can do more than just spawn objects.
-  * An example of this is spawning a specific mob based on a condition.
-  *
-  * Arguments:
-  * * T - The turf loot will be spawned on
-  */
+ * Loot spawner proc
+ *
+ * This exists as an overridable method so you can do more than just spawn objects.
+ * An example of this is spawning a specific mob based on a condition.
+ *
+ * Arguments:
+ * * T - The turf loot will be spawned on
+ */
 /obj/effect/mazegen/module_loot/proc/spawn_loot(turf/T)
 	CRASH("spawn_loot() not overriden for [type]")

code/modules/effects/sparks/spawner.dm

@@ -17,7 +17,7 @@
 		spread = spread_dirs
 	else
 		spread = list()
-		
+
 	..(start_immediately)
 
 /datum/effect_system/sparks/process()
@@ -40,6 +40,6 @@
 				direction = 0
 
 			S = new /obj/effect/visual/sparks(location, src)
-			S.start(direction)	
+			S.start(direction)
 			QUEUE_VISUAL(S)
 			total_sparks++