Repository navigation
docs: New page for GhostObject/hybrid objects - #4212
Merged
Merged
Conversation
EmandM
reviewed
Oct 23, 2026
Co-authored-by: Emma <[email protected]>
Contributor
Author
|
FYI I'm logging off for the week and won't be back until Tuesday -- feel free to merge this in my absence once @NoelStephensUnity has reviewed to get it in for the next release. |
NoelStephensUnity
approved these changes
Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose of this PR
Adding a new page to the docs to cover the use of hybrid objects/GhostObjects w/ Unity Netcode. (And also a small fix for a feedback issue we just received that I wanna sneak into the next release)
I'm not 100% on where the new page is in the TOC. I've put it under the network components section, but I initially had it at the very tippy top of the TOC next to the upgrade guide for visibility's sake. Thoughts?
Jira ticket
Changelog
Documentation
Testing & QA (How your changes can be verified during release Playtest)
Built and tested locally
Functional Testing
Manual testing :
Manual testing doneAutomated tests:
Covered by existing automated testsCovered by new automated testsDoes the change require QA team to:
Review automated tests?Execute manual tests?Provide feedback about the PR?If any boxes above are checked the QA team will be automatically added as a PR reviewer.
Up-port
N/A
Backports
N/A - doc for new feature