Why are UnityWebRequest and Multiplayer bunched together?

News & General Discussion
1

I notice that UNET seems to now be the legacy system for all web requests and multiplayer with all such functions bunched together in the docs.

However basic php calls and other web requests (download images. assetbundles etc) are a long way from multiplayer networking are they not?
Many people may require simple web requests and non game projects need this but not multiplayer, so I find it strange they are bunched together and all effectively legacy now (all doc pages have “Note: UNet is deprecated…” at top)

Why is there not a fixed robust http get/post call system? The old WWW legacy system was simple, the new UnityWebRequest makes some things a little harder but is already facing becoming legacy with UNET changing.
Why did Unity not keep 1 web request [get/post/download] system separate to multiplayer?
Is there an alternative .NET system?

2

Why not use HttpClient in System.Net:Http (if you target 4.5 mono)

3

Ummmm no. You’re jumping to conclusions without understanding what you’re reading. The message is clear that Unet is deprecated. They appear to just be a bit overzealous on what pages they have added the message to, where they have placed it on every page in the Multiplayer and Networking section instead of only on Unet specific pages.

The scripting reference is what is most authoritative on whether an API has been marked deprecated or obsolete, and UnityWebRequest has not.

Obsolete Unet API:
https://docs.unity3d.com/ScriptReference/Networking.NetworkTransport.html

UnityWebRequest, not deprecated or obsolete:

1 Like
4

Good, though not good documentation Unity, it was confusing for a bit…

1 Like