From c6251bc15b6ab8f02143ee88eee5eb704449a0c0 Mon Sep 17 00:00:00 2001 From: Chris Langsenkamp Date: Thu, 3 Oct 2019 08:13:39 -0400 Subject: [PATCH] SyncVar Limit is 64 per NetworkBehaviour --- doc/Guides/Sync/SyncVars.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/Guides/Sync/SyncVars.md b/doc/Guides/Sync/SyncVars.md index 6c9f34ff2..fb57e239f 100644 --- a/doc/Guides/Sync/SyncVars.md +++ b/doc/Guides/Sync/SyncVars.md @@ -4,7 +4,7 @@ SyncVars are properties of classes that inherit from NetworkBehaviour, which are The state of SyncVars is applied to game objects on clients before `OnStartClient()` is called, so the state of the object is always up-to-date inside `OnStartClient()`. -SyncVars can use any [type supported by Mirror](../DataTypes.md). You can have up to 32 SyncVars on a single NetworkBehaviour script, including SyncLists (see next section, below). +SyncVars can use any [type supported by Mirror](../DataTypes.md). You can have up to 64 SyncVars on a single NetworkBehaviour script, including SyncLists (see next section, below). The server automatically sends SyncVar updates when the value of a SyncVar changes, so you do not need to track when they change or send information about the changes yourself.