Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.

Two separately project or one in netcode?

Discussion in 'Netcode for GameObjects' started by Roblog, Mar 16, 2023.

  1. Roblog

    Roblog

    Joined:
    Dec 29, 2019
    Posts:
    1
    Hi, . I would like design game that one build will be as server and another build as client.
    And for example server will be destined only for windows and client for android. So what is better solution for do it. It is possible to make two separately project (one for windows as server , one for android as client) or make one project. Main reason why i asking is that i gonna use different asset to build on windows and android and i don't know that make 2 project or 1. I have read that for netcode is better use one project but what about managing asset between android and windows otherwise I've also read that is possible use with 2 project without using network object but just sending custom message between server and client which is enough for my game.
     
  2. CodeSmile

    CodeSmile

    Joined:
    Apr 10, 2014
    Posts:
    2,110
    You can have two projects ONLY if you do not wish to use any NetworkBehaviour and NetworkVariables, only RPC calls and low level Unity Transport messaging will work.

    Still, I would strongly suggest to use a single project simply to reduce friction because you will have shared content between the two and specifically scripts not being in synch for a network game will cause plenty of issues that'll be hard to track down since you need to debug and test two separate projects.

    For Asset Management the workflow is the same as with any multiplatform title, most importantly you'll want to look into Asset Bundles.
     
    RikuTheFuffs likes this.