<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: ShipIt | Unity Toolkits</title>
    <description>The latest articles on DEV Community by ShipIt | Unity Toolkits (@shipitunity).</description>
    <link>https://dev.to/shipitunity</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4171638%2F432f01c1-4f46-43a6-9510-dca3d3a3902e.png</url>
      <title>DEV Community: ShipIt | Unity Toolkits</title>
      <link>https://dev.to/shipitunity</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shipitunity"/>
    <language>en</language>
    <item>
      <title>Backend or Netcode? A Responsibility Map for Unity Multiplayer</title>
      <dc:creator>ShipIt | Unity Toolkits</dc:creator>
      <pubDate>Thu, 12 Nov 2026 13:51:54 +0000</pubDate>
      <link>https://dev.to/shipitunity/backend-or-netcode-a-responsibility-map-for-unity-multiplayer-3p2k</link>
      <guid>https://dev.to/shipitunity/backend-or-netcode-a-responsibility-map-for-unity-multiplayer-3p2k</guid>
      <description>&lt;p&gt;A save service, a session service, and netcode can all handle state or move information. That overlap makes it easy to ask the wrong question: “Which one should handle multiplayer?”&lt;/p&gt;

&lt;p&gt;It helps to split the problem into three jobs: &lt;strong&gt;durable data&lt;/strong&gt;, &lt;strong&gt;session coordination&lt;/strong&gt;, and &lt;strong&gt;real-time game synchronization&lt;/strong&gt;. A project may use one provider for more than one job, but the responsibilities remain distinct.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Durable data: what should remain after play?
&lt;/h2&gt;

&lt;p&gt;This layer stores information that needs to survive a session: player preferences, saved progress, account-linked inventory, or results that matter across matches. Unity describes &lt;a href="https://docs.unity.com/en-us/cloud-save" rel="noopener noreferrer"&gt;Cloud Save&lt;/a&gt; as a place for player and game data that can be accessed across devices. That is a persistence job; it does not, by itself, decide what a player is allowed to earn or equip.&lt;/p&gt;

&lt;p&gt;For every important write, ask two questions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Does this need to persist beyond the current session?&lt;/li&gt;
&lt;li&gt;Who is allowed to write it, and what must be checked first?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A player changing a sound preference may be a low-risk write. A competitive reward or paid entitlement can require a stronger authority and review path. The right enforcement depends on the game and the service configuration. A database rule or cloud function is a tool for enforcing a rule; it is not proof that the rule is complete.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Session coordination: who is playing together?
&lt;/h2&gt;

&lt;p&gt;Before a match starts, a game may need to create a session, let players join, keep track of membership, or share connection details. Those tasks help players meet and connect. They do not automatically simulate the match.&lt;/p&gt;

&lt;p&gt;Unity's &lt;a href="https://docs.unity.com/en-us/mps-sdk/sessions-overview" rel="noopener noreferrer"&gt;Multiplayer Sessions documentation&lt;/a&gt; describes sessions as a coordination point for connected players and connection setup. Unity's &lt;a href="https://docs.unity.com/en-us/engine/7000.0/manual/building-blocks/multiplayer/sessions" rel="noopener noreferrer"&gt;Sessions building block documentation&lt;/a&gt; explicitly separates sessions from gameplay synchronization. This is a useful boundary: a lobby can say who is in a match, while a networking and game-simulation design determines how the match proceeds.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Real-time synchronization: what must agree during play?
&lt;/h2&gt;

&lt;p&gt;Movement, attacks, collisions, and other moment-to-moment actions belong to the active simulation and its networking model. &lt;a href="https://docs.unity.com/en-us/multiplayer/netcode/netcode" rel="noopener noreferrer"&gt;Unity Netcode packages&lt;/a&gt; support real-time synchronized gameplay. Netcode moves or reconciles information among players. The game still needs a deliberate authority model: which machine or service decides the result, how clients predict or display it, and what happens when messages arrive late or out of order.&lt;/p&gt;

&lt;p&gt;There is no single authority model for every Unity game. Unity documents both Netcode for GameObjects and Netcode for Entities. Its &lt;a href="https://docs.unity.com/en-us/mps-sdk/manage-session-network-connection" rel="noopener noreferrer"&gt;session connection options&lt;/a&gt; include direct and client-hosted connections, and allow custom network handlers. Pick based on the game's fairness needs, player count, target platforms, latency expectations, operating capacity, and budget.&lt;/p&gt;

&lt;h2&gt;
  
  
  Trace one player flow
&lt;/h2&gt;

&lt;p&gt;Consider a match that awards a persistent reward:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A session service helps the players find or join the match.&lt;/li&gt;
&lt;li&gt;The active game simulation processes inputs and determines what happened.&lt;/li&gt;
&lt;li&gt;If the reward matters to competition or an economy, the appropriate trusted authority checks the result.&lt;/li&gt;
&lt;li&gt;The accepted result is written to durable data so it remains available after the match.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;In a casual local game, some of these responsibilities may be intentionally simpler. In a competitive or economy-driven game, they may need stronger separation. The important point is to choose that boundary deliberately instead of assuming that “the backend” or “the network” handles everything.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick responsibility checklist
&lt;/h2&gt;

&lt;p&gt;For one player action, write down:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Question&lt;/th&gt;
&lt;th&gt;Likely responsibility&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Must this value survive a session or device change?&lt;/td&gt;
&lt;td&gt;Durable data / backend&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Does it describe who is in a match or how they connect?&lt;/td&gt;
&lt;td&gt;Session coordination&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Must it be synchronized while the match is actively running?&lt;/td&gt;
&lt;td&gt;Networking and game simulation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Could a modified client gain an unfair or valuable result by changing it?&lt;/td&gt;
&lt;td&gt;Define a trusted validation authority&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;What happens after disconnect, retry, or duplicate submission?&lt;/td&gt;
&lt;td&gt;Specify behavior across the responsible layers&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;These are prompts, not a drop-in architecture. Some features cross layers: a match result may be produced by the simulation, validated by an authority, and then saved by a backend. Name each handoff in the design.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep the boundaries visible
&lt;/h2&gt;

&lt;p&gt;The backend is not automatically your real-time netcode. A lobby or session is not the match simulation. Replicating an object does not automatically validate a reward. And adding a server does not, by itself, make every game rule secure.&lt;/p&gt;

&lt;p&gt;Before choosing services, sketch one flow from player input to the state other players or future sessions will see. Mark who owns each decision and what should happen when a step fails. That small map usually exposes missing responsibilities earlier than comparing long feature lists.&lt;/p&gt;

&lt;h3&gt;
  
  
  References
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.unity.com/en-us/cloud-save" rel="noopener noreferrer"&gt;Unity Cloud Save&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.unity.com/en-us/mps-sdk/sessions-overview" rel="noopener noreferrer"&gt;Introduction to Multiplayer Sessions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.unity.com/en-us/engine/7000.0/manual/building-blocks/multiplayer/sessions" rel="noopener noreferrer"&gt;Multiplayer Sessions building block&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.unity.com/en-us/multiplayer/netcode/netcode" rel="noopener noreferrer"&gt;Unity's Netcode packages&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.unity.com/en-us/mps-sdk/manage-session-network-connection" rel="noopener noreferrer"&gt;Network connection options&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;ShipIt builds tools for Unity developers. &lt;a href="https://shipitunity.com" rel="noopener noreferrer"&gt;Website&lt;/a&gt;&lt;/p&gt;

</description>
      <category>backend</category>
      <category>unity3d</category>
      <category>gamedev</category>
      <category>multiplayer</category>
    </item>
    <item>
      <title>A Unity backend you own: C# tooling for Supabase</title>
      <dc:creator>ShipIt | Unity Toolkits</dc:creator>
      <pubDate>Thu, 12 Nov 2026 06:44:58 +0000</pubDate>
      <link>https://dev.to/shipitunity/a-unity-backend-you-own-c-tooling-for-supabase-40ai</link>
      <guid>https://dev.to/shipitunity/a-unity-backend-you-own-c-tooling-for-supabase-40ai</guid>
      <description>&lt;p&gt;Why the data path matters more than the SDK: identity, RLS, cloud saves, realtime, and SQL tooling from a Unity 2022.3+ project.&lt;/p&gt;

</description>
      <category>unity3d</category>
      <category>gamedev</category>
      <category>supabase</category>
      <category>csharp</category>
    </item>
  </channel>
</rss>
