Search Issue Tracker
Fixed
Fixed in netcode-gameobjects-1.12.0
Votes
0
Found in [Package]
netcode-gameobjects-1.9.1
Issue ID
MTTB-372
Regression
No
[GH-2966] Permanently disable "Add NetworkObject Prompt" (Breaks Dynamically spawned Prefabs with nested Prefabs)
[https://github.com/Unity-Technologies/com.unity.netcode.gameobjects/issues/2966]
Feedback
Users should have the option to completely disable the "Add NetworkObject" prompt.
I understand that this solves a lot of issues for users, but in some fairly common cases this will be infuriating and even break the project.
Suggested Changes
Add a setting to Project Settings (it should be project scoped since some projects might not make use of nested prefabs that are dynamically spawned) that completely disables the prompt. Perhaps even add a checkbox to the prompt like a "Do not show this again"
Steps to reproduce:
Scenario: Nested Prefabs
- You have a prefab "Parent" with NetworkObject attached
- You have a prefab "Child" with NetworkBehaviour attached and NO NetworkObject
- You add "Child" to "Parent" prefab
Every time you select "Child" you will get the "Add NetworkObject" prompt, and there is no way to prevent it from continuously prompting this. If you accidentally click {}"Yes"{}, or worse "Yes (Do not show me this message again on this machine)" a NetworkObject will be added to the {}"Child"{}.
Actual results:
If "Parent" is a dynamically spawned prefab, it will not spawn because nested NetworkObjects is NOT supported for dynamically spawned objects.
If you accidentally click "Yes (Do not show me this message again on this machine)" at any point on your machine. This will break any project you have with nested prefabs.
I had the experience of having to go through all of my prefabs and remove the NetworkObject for the nested prefabs and also deal with the prompt appearing multiple times per prefab upon removal. For large projects (like mine) this can take hours.
Expected results:
Users should have the option to completely disable the "Add NetworkObject" prompt.
Reproducible with versions:
NGO 1.9.1
Not reproducible with versions:
N/A
Can’t test with versions:
N/A
Tested on (OS):
Notes:
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader Graph Swizzle Node Input/Output and Mask Update Incorrectly After Undo
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
Add comment