Several systems should be decoupled

[valkyrienyanko]

The following should be converted to NuGet packages:

• Visualize
• Multiplayer Code
• Debugger Plus Addon (currently tightly coupled to setup addon)
• GodotUtils
• MetricsOverlay
• In-Game Console
• Centralized component scripts? Perhaps a part of GodotUtils?
• Script driven options?

Why?

• This template has become a mega project. Not everyone may want to use the entire template. Maybe someone may only want to use for example the Debugger Plus addon. If everything are in separate NuGet packages, I can publish them to NuGet website and people can take what they need.

Separate repos?

• If the modules were placed in separate repos this would make development hard. For example if I wanted to implement something in Template but it required a change in GodotUtils, I would have to update the GodotUtils repo first before I could update the Template repo. So I'm going to keep all the subprojects in one repo for now.

This is definitely something that needs to be done before anything else. I won't add the good first issue label since this is quite involved.

Update 1

The following packages are all now nupkg's:

• GodotUtils
• PacketGen
• OptionsGen
• Visualize

DebuggerPlus has been decoupled into its own addon.

OptionsGen is very template specific, it shouldn't be published to nuget.

PacketGen is tightly coupled to multiplayer. Perhaps multiplayer should be in its own nupkg file, I'm not sure.

GodotUtils and Visualize are good for public external use.

DebuggerPlus could be in its own nupkg, I'm not sure.

MetricsOverlay / In-Game Console could go in their own nupkg, not sure about this either.