We started talking more about how serverside code is going to work. I am assuming the following:

1. People who want serverside code are going to be self hosting all of their servers
2. It will only be on dedicated servers

#if SERVER
    if ( true ) { ... } 
#endif

To a developer - this is how you'll create server-only / private code.

#if SERVER
    if ( true ) { ... } 
#endif

Alternatively, if you have a file called Something.Server.cs - we'll wrap this whole file in a #if SERVER for you - a bit of syntactical sugar.

[AttributeUsage( AttributeTargets.All )]
public sealed class ServerOnlyAttribute : Attribute;


public class YourSharedClass
{
  [ServerOnly]
  private ServerStruct instance;

  private void SomeClientMethod()
  {
    // TODO: Generator walks trees and throws error for this?
    // Or just let C# complain about no field after strip idk
    instance = new();
  }

  [ServerOnly]
  private void SomeServerMethod()
  {
    instance = new(); // Works as normal
  }
}

[ServerOnly]
public struct ServerStruct
{

}

I feel like the attributes could get messy pretty quickly, the `#if server` would simply strip out the block not allowing you to compile(fail fast is favorable).

We're keeping with one project.. I think. It's simpler that way - it's the most pragmatic method

Also if SERVER is defined, I think you can use the [Conditional("SERVER")] attribute possibly?