We need to plan out a new system that uses components to control the power.

I have a few ideas

1. Get rid of hierarchy in structures, use a protocol (Virtual class) to determine necessary methods and variables for each structure. This will take a lot of work, but I think it will be worth it, and make our code a LOT cleaner and easier to understand and follow
2. PowerCreateComponent for reactors and other power generating structures
3. PowerComponent for everything else that searches out power and stops when it find some, some meaning a possible PowerStorageComponent.

This should all be relatively simple and use much of the code we have already created.

In the process of doing this would could look through our connection code to make sure that our master finding and all the stuff is working properly. I have noticed a few bugs with it, like turrets firing even after they have been disconnected from reactors, as long as they still have a node connected to them, they will still try to draw power.

We might want to separate out the components further. PowerStorageComponent, for a battery, and so that the structure can hold power. A PowerCreateComponent would require a PowerStorageComponent on the entity, or it wouldn't function and just stop if we did this.

Buildings no longer construct themselves over time. Not sure why. Will have to dig through the code to find out.