How do you organize code for your NetCode projects?

[teal oxide]

As title^^

- Client
    - Movement
        - Authoring
        - Baking(?)
        - Systems
        - Components
- Server
    - Movement
- Mixed
    - Movement

vs

- Movement
    - Client
        - Authoring
        - Systems
        - Components
    - Server
    - Mixed

vs

- Movement
    - Authoring
        - Client
        - Server
        - Mixed
    - Systems
    - Components

Or other suggestions or comments on pro cons?^^

[glass oasis]

The benefit of splitting is the ability to use asmdefs and to only include some of them in your build. With option #1 you can only ship your Client+Mixed code to the players, and only include Server+Mixed code for the server build.

[teal oxide]

Yeah, that's what I've been doing so far as well. But considering one tries to make Movement self contained in its assemblies (I guess 3 of them for each client server mixed). One can get an easier overview of the parts than moving through three expansions of bunch of modules? One would still have the three asmdef for client server mixed that links to all the modules in the end.

[jaunty hawk]

I use the first. Use asmref to build for client, server, or both.

My opinion, stop thinking about it. Code until the mechanic works then figure out how to organize it at the end.

Reorganizing is far easier than coding the mechanic. Focus on coding, then do file organization last.