Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.1p1
Issue ID
959228
Regression
No
[UNET] "Auto Create Player" on the NetworkManager is not server autoritative
Steps to reproduce:
1. Open user attached project
2. Build and run the project
3. Select "LAN Server Only" in the build
4. Open "Offline" scene, select the "Camera" game object
5. Enable "Auto Create Player" in the editor and join the server
6. Notice in the inspector that the Client has a player object even tho the server has "Auto Create Player" disabled.
Expected result: "Player" game object should not appear if "Auto Create Player" is selected on the client side and not on the server side
Reproduced in: 2018.1.0a1, 2017.3.0b5, 2017.2.0f3, 2017.1.1p1, 5.6.4p1, 5.5.4p4
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Missing or broken path ()" is shown when opening the "Open Recent Scene" dropdown on a newly created project
- Foveation is not applied to final Blit Passes when camera Post-Processing is disabled in URP & SRP
- Caret is not being offset when content on a GUISkin is offset
- [Android][Vulkan] Application crashes with out of memory when warming up a specific shader on some of the Adreno devices
- Unity Editor hangs on a fresh import when using "-CacheServerWaitForUploadCompletion" command line argument
Resolution Note:
Mass closure of UNET Bugs.
As UNet is Deprecated we are moving to low maintenance mode, where critical issues can get fixes.
Closing this bug as part of cleaning-up the Bug List.
If you feel this bug is really a road-blocker, you can reopen the bug and we will work this one.