> For the complete documentation index, see [llms.txt](https://docs.coherence.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coherence.io/0.9/tutorial-project/network-playground/physics.md). # 2. Physics ## Physics This scene will show you how to use **coherence** to sync GameObject transforms and Physics objects across the network. In this example, each Client will have its own player character to move. Left-clicking on the map will make the Entity move to that location. Right-clicking will spawn local physics-based objects that all player characters can interact with. Each Client will only have control over its local Entity. ![](/files/-MWdlaGRA0E8iTQ-4SJS) ### General setup In the *Hierarchy* of the scene you can see three core Prefabs: `Core Scene Setup` and `Coherence Setup` are present in all scenes and described in detail on [Start Tutorial](/0.9/tutorial-project/network-playground.md) page. `Coherence Entity` is the Prefab that will change per scene with different functionality. It has a standard `CharacterController`and `Rigidbody` as well as an `Agent` script which will handle movement functionality through the `Input Manager` in the `Core Scene Setup` Prefab. `Coherence Connection Events` handles overall scene connectivity. Additionally, it removes all Entities with `coherenceSync` from the scene to demo disconnecting/reconnecting via the interface without refreshing the scene. ### In this scene... `Coherence Entity Character` (remember to always change the Prefab, not the instance) is located in the *Resources* folder. The `UnityEngine.Transform` and `position` are ticked to sync. All other settings (persistence and authority) use the default settings. This Entity will be session-based, no authority handover and no adoption will take place, when a Client leaves. The `On Network Instantiation` event is used to change the color of the mesh. The `Physics Entity Spawner` is a simple script to instantiate a `Coherence Entity Physics` Prefab with a coherenceSync component that replicates the transform and position. The component also changes the material based on whether it is locally simulated or synced over the network. ![](/files/-MWd5LU_vVRoUkYFsulF) ### Build and try You can build this scene via the *Build Settings*. Run the local Replication Server through the *Window > Coherence > Settings* window and see how it works. You can try running multiple Clients rather than just two and see how replication works for each. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.coherence.io/0.9/tutorial-project/network-playground/physics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.