Adds support for machinery to be bigger than 1x1

[DGamerL]

What Does This PR Do

Adds support for machinery to be bigger than a 1x1
Also removes an unneeded variable on /obj/structure/filler

How does this system work

Add the component to the machinery on Initialize(), and add a list like the one below as the second argument. This list is a representation for a coordinate map around the machinery, and can be any size (3x3, 5x5, 7x7) as long as it has an uneven length and is square.

	list(
			list(0, 0, 0,   0, 0),
			list(0, 0, 0,   0, 0),
			list(0, 0, MACH_CENTER, 0, 0),
			list(0, 0, 0,   0, 0),
			list(0, 0, 0,   0, 0)
		)

If you want to make specific turfs dense, you just have to change the int to 1, which will make a filler turf there.
All these filler turfs are automatically cleared upon Destroy and don't need any special overrides to be cleared out.

Why It's Good For The Game

This allows us to make bigger machinery in various special shapes with a lot of freedom

Testing

No rubber duckies for testing sadly, you're gonna have to trust that I touched these machines

I also tested the gravity generator, just didn't take a picture

---

Declaration

• I confirm that I either do not require pre-approval for this PR, or I have obtained such approval and have included a screenshot to demonstrate this below.

---

Changelog

Big thanks to beaglegaming for Component'izing it when I didn't have motivation to do so!
NPFC

[MLGTASTICa]

* Moving it to `/obj/machinery`, which _technically_ is fine but it'd give every piece of machinery a nested list with 25 integers, which can clutter VV a decent amount

Why not just initialize the list only when needed? as in all the big machines just having a set filler proc() in their initialize, this way you avoid both unnecesarry subtypes and provide the functionality for all machinery, powered or not , at no RAM cost other than a variable declaration.

[DGamerL]

* Moving it to `/obj/machinery`, which _technically_ is fine but it'd give every piece of machinery a nested list with 25 integers, which can clutter VV a decent amount

Why not just initialize the list only when needed? as in all the big machines just having a set filler proc() in their initialize, this way you avoid both unnecesarry subtypes and provide the functionality for all machinery, powered or not , at no RAM cost other than a variable declaration.

Very good point, I'm gonna do this

[DGamerL]

@MLGTASTICa it is done

[lewcc]

This will be pretty nice to have, excited to see it.

Got some comments on loading the map in, just to make sure it's as safe as can be. Working with nested lists in byond feels like it's worth double-checking.

[Daylight2]

Does this mean that you don't have to interact with the bottom left corner of grav gen anymore? Technology has come so far.

[DGamerL]

Does this mean that you don't have to interact with the bottom left corner of grav gen anymore? Technology has come so far.

Yup! Added the grav gen to this PR!

[lewcc]

Looks good, thanks for adding the sanity checks. Just one little thing.

Stale