From 76bdbc88e73ef81525e423db7856e7c062e99649 Mon Sep 17 00:00:00 2001 From: MrGadget Date: Tue, 19 Nov 2019 09:46:56 -0500 Subject: [PATCH] Update index.md --- doc/General/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/General/index.md b/doc/General/index.md index be8fd7255..dd6bd367e 100644 --- a/doc/General/index.md +++ b/doc/General/index.md @@ -41,14 +41,14 @@ One of the aims of the multiplayer system is for the code for local clients and When you make a single player game In Mirror, you usually use the `GameObject.Instantiate` method to create new game objects at runtime. However, with a multiplayer system, the server itself must “spawn” game objects in order for them to be active within the networked game. When the server spawns game objects, it triggers the creation of game objects on connected clients. The spawning system manages the lifecycle of the game object, and synchronizes the state of the game object based on how you set the game object up. -For more details about networked instantiating and spawning, see documentation on Spawning game objects. +For more details about networked instantiating and spawning, see documentation on Spawning [game objects](../Guides/GameObjects/index.md). ## Players and Local Players Mirror’s multiplayer HLAPI system handles player game objects differently to non-player game objects. When a new player joins the game (when a new client connects to the server), that player’s game object becomes a “local player” game object on the client of that player, and Mirror associates the player’s connection with the player’s game object. Mirror associates one player game object for each person playing the game, and routes networking commands to that individual game object. A player cannot invoke a command on another player’s game object, only their own. -For more details, see documentation on Player game objects. +For more details, see documentation on Player [game objects](../Guides/GameObjects/index.md). ## Authority -Servers and clients can both manage a game object’s behavior. The concept of “authority” refers to how and where a game object is managed. Mirror’s HLAPI is based around “server authority” as the default state, where the Server (the host) has authority over all game objects which do not represent players. Player game objects are a special case and treated as having “local authority”. You may want to build your game using a different system of authority - for more details, see Network Authority. +Servers and clients can both manage a game object’s behavior. The concept of “authority” refers to how and where a game object is managed. Mirror’s HLAPI is based around “server authority” as the default state, where the Server has authority over all game objects. Player game objects are a special case and treated as having “local authority”. You may want to build your game using a different system of authority - for more details, see [Network Authority](../Guides/Authority.md).