* Create Network Scene Checker Component
* Move objects to subscene in client
* Remove OnStartClient
* Rewritten with static dictionary
* Updated doc
* renamed image
* Replaced image
* fixed image name
* Changed to short-circuit return in Update
* Changed to using string for key since additive scenes may be unloaded
* Added null check
* Removed commented line
* Update Assets/Mirror/Components/NetworkSceneChecker.cs
Co-Authored-By: vis2k <info@noobtuts.com>
* Moved initializer to declaration
* Removed [Scene, SerializeField]
Co-authored-by: vis2k <info@noobtuts.com>
* test
* new docs
* adjust CheckForHookFunction to expect two hooks
* update example
* update example
* update example
* update test
* update example
* SyncVar.set: store value in oldValue variable
* SyncVar.set: pass old value to hook too
* TODO
* SyncVar deserialize store value in oldValue variable (for simple types)
* SyncVar deserialize: pass old value to hook too (for simple types)
* add test for GameObject type
* fix comment
* SyncVar deserialize: set value before calling hook
* add TODO
* SyncVar.set: set value before calling hook
* replace tests
* GO test
* SyncVar deserialize: move oldvalue code higher up so it applies to GO/NI too
* syntax
* SyncVar deserialize: pass oldValue to hook (GO/NI types)
* SyncVar deserialize: set netid before calling hook (GO/NI types)
* update comment
* update comment
* update comment
* shorter
* comment, TODO
* put oldValue code into separate cases again
* fix SyncVarEqual comparing the same two __goNetId values
* get rid of tmpValue
* fix weaver tests
* remove TODO
* SyncVar deserialize simple types: get rid of tmpValue here too
* remove tests
* Create DevelopmentServer.md
This guide focuses on helping people try out their projects on a dedicated server so a more realistic test can be performed to see if everything works correctly.
This focuses on the free/trial aspect from the chosen providers and tries to make it very clear to readers that "free" is relative and Mirror can not be held responsible if they go above the providers limits.
It is mainly a guide on setting up the dedicated server through different providers to test your Mirror project.
Question:
Should I put it all under each other or should each provider/possibility be a different page like synchronization/GameObjects?
For example:
Overview
AWS
Azure
Google
* Make dedicated servers a submenu
* Add files via upload
* Move AWS inside it's own folder
* Update index.md
Changed the imgur links to the github images in the AWS folder so offline access is possible
* Update index.md
As suggestion from SoftwareGuy from suggestion: https://github.com/vis2k/Mirror/pull/1365#discussion_r361819820
I have made this in a bullet point so it's more clearly visible
* Update index.md
* Update index.md
* Update index.md
Added the changes as SoftwareGuy mentioned
* Update index.md
Another update to the formatting.
Changed some parts to titles so it's easier to navigate through the right hand side on github pages.
Some more formatting done
* Update index.md
Changed the titles from the 7 steps to include the step number for easier following
* Update index.md
Forgot this one: https://github.com/vis2k/Mirror/pull/1365#discussion_r361819874
Co-authored-by: Paul Pacheco <paulpach@gmail.com>
In the example while reading the guides it just seemed easier to put the variables at the top (as you read the OnStartServer method you see a variable and try to find what it is, but it's further down.
Easier to understand in my mind. Not sure if it's a huge issue for others
* Update SyncVars.md
* Update doc/Guides/Sync/SyncVars.md
Co-Authored-By: Paul Pacheco <paulpach@gmail.com>
* Update SyncVars.md
- Removed starting time from video URL.
* Resize image and move to the top
* Make video bigger
* feature: SyncList.Callback passes old and new entries instead of only passing one entry which is sometimes the old, sometimes the new entry. This is more consistent and it's very useful to know the previous value in a hook for OP_SET and OP_DIRTY.
* update tests
* update docs
