# Data types

The client and server can pass data to each other via [Remote Actions](communications/remote-actions), [State Synchronization](synchronization) or via [Network Messages](communications/network-messages)

Mirror supports a number of data types you can use with these, including:

* Basic C# types (byte, short, int, long, uint, ushort, ulong, float, double, char, string, etc.)
* Built-in Unity math types (Vector3, Quaternion, Rect, Plane, etc.)
* Built-in Unity types that are structs under the hood (Color, Sprite, Texture2D, Ray, etc.)
* URI
* `NetworkIdentity`, `NetworkBehaviour`
  * **These should not be used in SyncVars or Sync\* Collections or Rpc's because they'll be null on the client if the corresponding object hasn't already been spawned.**
* Game object with a `NetworkIdentity` component that have been network spawned
  * **Not** prefabs!
  * See important details in [GameObjects](gameobjects) section below.
* Structures with any of the above
  * You must replace the whole struct value, not just change its properties
  * It's recommended to implement IEquatable to avoid boxing, and to have the struct readonly because modifying one of properties does **not** cause a resync
* Classes as long as each field has a supported data type
  * You must replace the whole class value, not just change its properties
  * **These will allocate garbage** and will be instantiated new on the receiver every time they're sent.
* ScriptableObject as long as each field has a supported data type
  * **These will allocate garbage** and will be instantiated new on the receiver every time they're sent.
  * See details in the [ScriptableObjects](#scriptable-objects) section below.
* Arrays of any of the above
  * Not supported with [Sync\* collections](synchronization)
* ArraySegments of any of the above
  * Not supported with [Sync\* collections](synchronization)

## Game Objects <a href="#game-objects" id="game-objects"></a>

Game Objects in SyncVars, SyncLists, and SyncDictionaries are fragile in some cases, and should be used with caution.

* As long as the game object _already exists_ on both the server and the client, the reference should be fine.

When the sync data arrives at the client, the referenced game object may not yet exist on that client, resulting in null values in the sync data. This is because internally Mirror passes the `netId` from the `NetworkIdentity` and tries to look it up on the client's `NetworClient.spawned` dictionary.

If the object hasn't been spawned on the client yet, no match will be found. It could be in the same payload, especially for joining clients, but after the sync data from another object.\
&#x20;It could also be null because the game object is excluded from a client due to network visibility, e.g. [`Interest Management`](../interest-management).

You may find that it's more robust to sync the `NetworkIdentity.netID` (uint) instead and do your own lookup in `NetworkClient.spawned` to get the object, perhaps in a coroutine:

```csharp
    public GameObject target;

    [SyncVar(hook = nameof(OnTargetChanged))]
    public uint targetID;

    void OnTargetChanged(uint _, uint newValue)
    {
        target = null;
        
        if (NetworkClient.spawned.TryGetValue(targetID, out NetworkIdentity identity))
            target = identity.gameObject;
        else
            StartCoroutine(SetTarget());
    }

    IEnumerator SetTarget()
    {
        while (target == null)
        {
            yield return null;
            if (NetworkClient.spawned.TryGetValue(targetID, out NetworkIdentity identity))
                target = identity.gameObject;
        }
    }
```

## Custom Data Types <a href="#custom-data-types" id="custom-data-types"></a>

Sometimes you don't want mirror to generate serialization for your own types. For example, instead of serializing quest data, you may want to serialize just the quest id, and the receiver can look up the quest details by the id in a predefined list or database.

Sometimes you may want to serialize data which uses a different type not supported by Mirror, such as DateTime.

You can add support for any type by adding extension methods to `NetworkWriter` and `NetworkReader`. For example, to add support for `DateTime`, add this somewhere in your project:

```csharp
public static class DateTimeReaderWriter
{
      public static void WriteDateTime(this NetworkWriter writer, DateTime dateTime)
      {
          writer.WriteInt64(dateTime.Ticks);
      }
     
      public static DateTime ReadDateTime(this NetworkReader reader)
      {
          return new DateTime(reader.ReadInt64());
      }
}
```

...then you can use `DateTime` in your `[Command]` or `SyncList`

## Inheritance and Polymorphism <a href="#inheritance-and-polymorphism" id="inheritance-and-polymorphism"></a>

Sometimes you might want to send a polymorphic data type to your commands. Mirror does not serialize the type name to keep messages small and for security reasons, therefore Mirror cannot figure out the type of object it received by looking at the message.

> **This code does not work out of the box.**

```csharp
class Item 
{
    public string name;
}

class Weapon : Item
{
    public int hitPoints;
}

class Armor : Item
{
    public int hitPoints;
    public int level;
}

class Player : NetworkBehaviour
{
    [Command]
    void CmdEquip(Item item)
    {
        // IMPORTANT: this does not work. Mirror will pass you an object of type item
        // even if you pass a weapon or an armor.
        if (item is Weapon weapon)
        {
            // The item is a weapon, 
            // maybe you need to equip it in the hand
        }
        else if (item is Armor armor)
        {
            // you might want to equip armor in the body
        }
    }

    [Command]
    void CmdEquipArmor(Armor armor)
    {
        // IMPORTANT: this does not work either, you will receive an armor, but 
        // the armor will not have a valid Item.name, even if you passed an armor with name
    }
}
```

CmdEquip will work if you provide a custom serializer for the `Item` type. For example:

```csharp

public static class ItemSerializer 
{
    const byte WEAPON = 1;
    const byte ARMOR = 2;

    public static void WriteItem(this NetworkWriter writer, Item item)
    {
        if (item is Weapon weapon)
        {
            writer.WriteByte(WEAPON);
            writer.WriteString(weapon.name);
            writer.WritePackedInt32(weapon.hitPoints);
        }
        else if (item is Armor armor)
        {
            writer.WriteByte(ARMOR);
            writer.WriteString(armor.name);
            writer.WritePackedInt32(armor.hitPoints);
            writer.WritePackedInt32(armor.level);
        }
    }

    public static Item ReadItem(this NetworkReader reader)
    {
        byte type = reader.ReadByte();
        switch(type)
        {
            case WEAPON:
                return new Weapon
                {
                    name = reader.ReadString(),
                    hitPoints = reader.ReadPackedInt32()
                };
            case ARMOR:
                return new Armor
                {
                    name = reader.ReadString(),
                    hitPoints = reader.ReadPackedInt32(),
                    level = reader.ReadPackedInt32()
                };
            default:
                throw new Exception($"Invalid weapon type {type}");
        }
    }
}
```

## ScriptableObjects <a href="#scriptable-objects" id="scriptable-objects"></a>

People often want to send scriptable objects from the client or server. For example, you may have a bunch of swords created as scriptable objects and you want put the equipped sword in a syncvar. This will work fine, Mirror will generate a reader and writer for scriptable objects by calling ScriptableObject.CreateInstance and copy all the data.

However the generated reader and writer are not suitable for every occasion. Scriptable objects often reference other assets such as textures, prefabs, or other types that can't be serialized. Scriptable objects are often saved in the in the Resources folder. Scriptable objects sometimes have a large amount of data in them. The generated reader and writers may not work or may be inneficient for these situations.

Instead of passing the scriptable object data, you can pass the name and the other side can lookup the same object by name. This way you can have any kind of data in your scriptable object. You can do that by providing a custom reader and writer. Here is an example:

```csharp
[CreateAssetMenu(fileName = "New Armor", menuName = "Armor Data")]
class Armor : ScriptableObject
{
    public int Hitpoints;
    public int Weight;
    public string Description;
    public Texture2D Icon;
    // ...
}

public static class ArmorSerializer 
{
    public static void WriteArmor(this NetworkWriter writer, Armor armor)
    {
       // no need to serialize the data, just the name of the armor
       writer.WriteString(armor.name);
    }

    public static Armor ReadArmor(this NetworkReader reader)
    {
        // load the same armor by name.  The data will come from the asset in Resources folder
        return Resources.Load(reader.ReadString());
    }
}
```
