31–40 of 277 posts
Earlier quoted context omitted.
It basically signals to me they don't give a fuck about you; it's Unity-first, and you can deal with it. Take it or leave it. After being burnt by the Source Engine, I'll never use Unity again after having read this.
What happened with Source?
I feel like people are missing the mark here, complaining about commercial game engines. SpatialOS was basically re-distributing Unity under a SaaS model. Unity is in the right here. Edit: Have heard some pretty good points about the ambiguous wording of the ToS (such as theoretically making the distribution of a Unity-made game through a storefront illegal). It will be interesting to see if this ToS change sticks.
From Ars https://arstechnica.com/gaming/2019/01/unity-engine-tos-chan...
> The newly updated clause 2.4 of the Terms of Service now specifically excludes "managed service[s] running on cloud infrastructure" which "install or execute the Unity Runtime on the cloud or a remote server."
Earlier quoted context omitted.
I think using Open Sourced Engines is the proper response to this. Why reinvent the wheel unless you have your own use case.
Open source engine suck big time, and I'm not even talking about the tooling part which is an even bigger problem, video game engine are usually not something you can do well on your own without large resources.
"Worryingly, this change occurred during an open commercial negotiation with the company to find a way to do more together."
So they had an ongoing negotiation and Unity just went ahead and made the change? Yikes.
Also kudos to Improbable for setting up an emergency fund for partners affected by this.
Earlier quoted context omitted.
What happened with Source?
Valve pretty much abandoned developing everything but Steam. You'll still see a few token projects come out of Valve, but it seems like they've basically turned into Steam, Inc.
Earlier quoted context omitted.
Open source engine suck big time, and I'm not even talking about the tooling part which is an even bigger problem, video game engine are usually not something you can do well on your own without large resources.
Godot and Phaser are not "Suck Big Time" engines. It depends what you are making, but again there is no reason why we must be stuck with closed source engines.
The game engine world is really different from what you usually read on HN like libraries, frameworks, DBs, languages ect ... it's a closed world where everyone built something custom.
These terms are incredibly vague. Makes it sound like you cannot run your own dedicated server for multiplayer without being in breach of the new terms. If Unity forces their new multiplayer hosted service on their users, I (and I foresee many others) will immediately start transitioning to Unreal.
Ref: https://unity3d.com/legal/terms-of-service/software (sec 2.4)
EDIT: after reading the actual terms it seems like even game developers can’t do this without violating terms. Unity really wants this to be something they wholly own. Yikes
I feel like people are missing the mark here, complaining about commercial game engines. SpatialOS was basically re-distributing Unity under a SaaS model. Unity is in the right here. Edit: Have heard some pretty good points about the ambiguous wording of the ToS (such as theoretically making the distribution of a Unity-made game through a storefront illegal). It will be interesting to see if this ToS change sticks.
Your right. This is about the hosting company running Unity software on the cloud -- something that clearly needs to be licensed by Unity. From Ars https://arstechnica.com/gaming/2019/01/unity-engine-tos-chan... > The newly updated clause 2.4 of the Terms of Service now specifically excludes "managed service[s] running on cloud infrastructure" which "install or execute the Unity Runtime on the cloud or a remote serve…
Earlier quoted context omitted.
No, Spatial was not doing that, they are an integration with Unity. Developers still needed to install Unity with a license, get the SpatialOS framework running as their net code, and then write a game.
I'm not so sure. Maybe I am misunderstanding but the terms prohibit the "use [of] a managed service running on cloud infrastructure...to install or execute the Unity Runtime on the cloud or a remote server". Which leads me to believe they are installing or running the Unity Runtime on their servers? If not I'd love a better explanation :)
If I write a licensed Unity app and run it on SpatialOS, well, that's now no longer allowed.