That was quick, wow. From Tim Sweeney: "Haha, actually though I first heard of this controversy at 1pm, Herman @ Improbable and I agreed on the fund at 6pm, live edited the announcement in Google docs till 7:30pm, released at 8pm." https://twitter.com/TimSweeneyEpic/status/108360085780606156...
I find that a bit dishonest tbh. Epic clearly sees the opportunity to gut punch it's competitor and use it to their advantage and lure devs away from Unity while getting good press in the process. Not so long ago Epic was selling their Engine for hundreds of thousands of USD while Unity was already way more accessible to indie devs. They are insanely rich from Fortnite fame right now, so for them this is peanuts.
Unity has done an incredible job of making game development accessible. So much so that when I wanted an extra 30 days on their trial period, I reached out over Skype and was answered within minutes by the founder (who was CEO at the time) and issued a new license key.
Unreal adapted to that market change - they didn't do it half-assed either, they did it properly and with conviction. Their success with Fortnite isn't a one-off, it's come from an astute market awareness and adaptability.
The fact that they turned this fund into reality so quickly is exactly why Fortnite and the Unreal engine is a success.
It's impressive that they managed to build that Battle Royale mode so quickly and efficiently (although obviously it was helped by the fact that they could build on top of their pre-existing Fortnite game) but I think you're downplaying the luck factor. Or rather, if you don't think it's a one-off, do you really think that they will be able to replicate this level of success "at will" in the future?
And if so, why didn't they have the same amount of success and "market awareness" in the past? Remember Paragon?
>Paragon was a free-to-play multiplayer online battle arena game developed and published by Epic Games. Powered by their own Unreal Engine 4, the game started pay-to-play early access in March 2016, and free-to-play access to its open beta started in February 2017. Epic Games shut down its servers on April 27, 2018.
I definitely think that the Fortnite people were at the right place at the right time, they saw an opportunity and jumped on it. They saw PUBG had great potential but was struggling to deliver a polished multiplatform experience. They had this brand new Fortnite game that they could mod a BR mode into relatively easily. They released it on platforms where PUBG was not available and on top of that they released it for free. It's clever but this particular combination of events do not occur every month.
Some companies will have spectacular failures as well as spectacular successes. Successful companies are able to learn from both and iterate.
Unreal and Unreal Tournament were absolute block busters that paved the way for Fortnite, just as Paragon did. You wouldn't have arrived at Fortnite without first going through the ups and downs that preceded it.
By your logic, a company can only be considered successful if they never make mistakes, which is a severely flawed position.
I don't really consider Unreal and UT because, while they were definitely successful and I personally love UT, they're the product of a different time. The last truly successful UT was in 2004 (UT3 in 2007 didn't have quite the same long-lasting appeal and even that was 12 years ago!). There's also Gears of War that was quite popular on consoles but again, a completely different formula and nothing remotely close to what Fortnite is achieving today.
It's not a binary. If I can consistently roll a 6 on a die at 1/4 probability, I'm still doing _something_ based on skill, in aggregate, while the outcome of any given roll is still largely being governed by chance.
> It's clever but this particular combination of events do not occur every month.
Adaptability isn't about _making_ the opportunity. It's about having enough flexibility to capitalise on it when it presents itself.
First of all, they weren't the first in the battle royale market. Many similarly styled games came before. Why hasn't PUBG, despite its absolute success, attained the relative success of Fortnite, which is likely driving 100x or more revenue? What about the many games or mods before PUBG?
In Epic's case, a big reason is the infrastructure. PUBG is a pretty bad game, from a technical sense. It runs like crap on PC, and the console ports are even worse. Comparatively, though not bug free, Fortnite is one of the most optimized, beautiful, performant AAA games out there.
They have in-house expertise with their engine. This is the difference between DICE making a technically amazing game like BF1 with Frostbite, then handing that exact same engine to the Bioware Montreal team to make Mass Effect Andromeda and getting that hot mess of a game. You can't just see a market trend like "oh battle royale games are popular" then become Fortnite. Their investment into the Unreal Engine helped make it possible.
And that's not including the investment into Save the World, which probably wasn't alone an investment that would have shown returns. But it made Fortnite BR possible. Game companies make poor performing games sometimes. That doesn't mean they're bad developers, or that they are "lucky" when they have a success. Their ability to identify that they could take the foundations laid by StW and capitalize on the battle royale market trend is nothing short of marketing genius, because its not immediately obvious from playing StW, specifically the building mechanics, that it would work well as a battle royale game. None of them had building before fortnite.
Ok, so they made a good game. Do you have any idea the engineering expertise that's necessary to scale a game like Fornite to the 8.3M concurrent players it experiences at peak? Fortnite is the most popular video game of all time, period. And, oh by the way, it's an online game with 100 player lobbies, real-time competitive-grade player interaction, and matchmaking within seconds. That's not easy. That's not "luck". And if they'd stumbled when they started achieving some small levels of success, people would have left. They didn't. 
Luck has almost nothing to do with it. They didn't get lucky that they had an amazing engine and a game like StW to build on top of; those things were the result of a decade of amazing engineering. They didn't get lucky when they scaled from 500k concurrent players to 8M in a period of months. There isn't more than a dozen people in the world reading this who have experienced scale that dramatic, and even if you had, probability states that you would have failed, and even if you hadn't, you're probably not working in an industry with customers as fickle and shitty as video gaming. Epic succeeded, and that's a testament to incredible engineering, planning, forethought, and likely some very late nights, missed sleep, and sacrificed time with loved ones.
They're successful because they're smart and they're hard working, not because they won the lottery.
> Why hasn't PUBG, despite its absolute success, attained the relative success of Fortnite, which is likely driving 100x or more revenue?
PUBG has had a following almost despite itself. The performance is terrible, the game assets are bland and most are store-bought, and the development behind it is incredibly slow. People played PUBG with conviction for, what, 6 months to a year?, before Fortnite showed up and started peeling players away. And when they launched on the Xbox, you couldn't use the same account that you had on the PC--which was a pretty big slap in the face for a game whose only rewards are collectable aesthetics.
While they're both technically the same genre, PUBG is slower and more methodical while Fortnite has quicker matches on the jump (if that's what you want), a more light hearted and original approach to style, and, of course, the building aspect.
On top of that, they were professional.
They released content on a regular schedule, with seasons and the season pass being something you could understand. They fix issues pretty quickly, and the game runs smooth. Plus the fact that it's not as intimidating as the gritty, slow pace of PUBG means there's likely a smaller barrier of entry.
The team behind Fortnite churn out good work, and I think the community sees and appreciates that. The game feels healthy and growing, rather than stuck in a perpetual 'alpha' phase that PUBG is still in.
Luck provided them with the opportunity, but their ingenuity is what let them take advantage of it and capitalise on it.
Besides, Unity clearly stated that Improbable knew about their TOS violation for at least half a year and Unity's reasoning also makes some sense, as Improbable is bundling Unity's SDK in their product. Problem is, that it's too late now because Improbable blew this up from their perspective omitting important information about what was actually going on.
As an analogy, I have the right to live anywhere I want in my country (where I live is a free choice), that doesn’t mean I can afford to actually do so.
Saying that Unity is wrong because they have complex licensing is just as misguided as saying that Epic is wrong because they charge royalties. Should Unity invest $25 million into a fund for "royalty-free game engines"?
? Hasn’t Epic always been quite mod/dev/indie friendly, giving away the Unreal SDK for free, publishing is free for non-commercial projects and as long as you weren’t an AAA dev/publisher you ‘only’ had to pay 5% of your profits once you made over $100.000
> Once you ship your game or application, you pay Epic 5% of gross revenue after the first $3,000 per product per calendar quarter.
epic had a fine licensing scheme before with udk which was modernised along with the market. as well as the additional services they now provide. without these services and the quality of games they produce they would have no fortune.
They realise, in the market, you need to keep growing or go bust, so further developments and improvements are made. its not dishonest or unfair - tried running a business lately?
Please enlighten us as to why selling software is worse than giving it away for "free", then changing the definition of "free".
> More than a year ago, we told Improbable in person that they were in violation of our Terms of Service or EULA. Six months ago, we informed Improbable about the violation in writing. Recent actions did not come as a surprise to Improbable; in fact, they’ve known about this for many months.
> Two weeks ago we took the action of turning off Improbable’s Unity Editor license keys. This is a unique case — and not a situation we take lightly — but Improbable left us no choice. This was the only course of action to protect the integrity and value of our technology and Unity developers.
Yikes. Not exactly what Improbable was claiming...
And then Improbable's statement today: https://improbable.io/company/news/2019/01/10/an-update-on-t...
> But honestly, we don’t believe that today was about Unity or for that matter Improbable.
Yes, let's change the subject. Quickly, now!!
Regardless, the ToS are incredibly vague on what is/is not allowed, even for developers that have nothing to do with Improbable.
Finally, the $25M comes from the already established Unreal dev grant fund - it's not "new" money, they just rebranded a portion of the fund in a PR stunt.
Don't you agree that based on the EULA, that this:
> Projects that are currently in production or live using SpatialOS are not affected by any actions we have taken with Improbable.
> If a game developer runs a Unity-based game server on their own servers or generic cloud instances (like GCP, AWS or Azure), they are covered by our EULA.
This is merely saying that they will selectively apply their EULA, which from the beginning is extremely vague, even more so before the previous update.
What's even a year in game development? Could you abandon your whole game source code in a year based on Unity deciding to apply their EULA to you specifically? I don't think so.
Could you force your whole user base to stop using your whole system because Unity decided to apply their EULA to you specifically? That's what they asked them a year ago and overnight made more clear in their EULA.
What Improbable said is true, the issue Improbable raised, is true. Whether they have been told this a year ago, or today, doesn't change that this practice from Unity is extremely awful and put in danger EVERY SINGLE entity that Unity may not like in the future. Personally I think what Improbable did by waiting a year was extremely generous, they gave Unity a year to change their stance and not start to apply their EULA selectively like that.
Overnight, Improbable showed to the world the true nature of Unity.
Improbable's knowing, selective omission of the pertinent fact that they'd been in negotiation for over a year shows the true nature of Improbable.
I really think Unity went above and beyond, here. And the fact that Improbable ran to their competitor to do a rapid PR stunt shows that they had their knives sharpened and ready to go. Tsk, tsk!
> I really think Unity went above and beyond, here.
Nonsense. Unity likes to portray itself as the "open" alternative to other gaming engines, when in reality they have an iron-fisted grip on everything distantly involving their platform.
Here's  what it says now:
> 2.4 Streaming and Cloud Gaming Restrictions.
> You may not directly or indirectly distribute the Unity Software, including the runtime portion of the Unity Software (the “Unity Runtime”), or your Project Content (if it incorporates the Unity Runtime) by means of streaming or broadcasting so that any portion of the Unity Software is primarily executed on or simulated by the cloud or a remote server and transmitted over the Internet or other network to end user devices without a separate license or authorization from Unity. Without limiting the foregoing, you may not use a managed service running on cloud infrastructure (a “Managed Service”) or a specific integration of a binary add-on (for example, a plugin or SDK) or source code to be integrated in the Unity Software or Your Project Content incorporating the Unity Runtime (an “SDK Integration”) to install or execute the Unity Runtime on the cloud or a remote server, unless such use of the Managed Service or SDK Integration has been specifically authorized by Unity. Additionally, you may not integrate the Unity Runtime with a Managed Service or SDK Integration and offer that integration to third parties for the purpose of installing or using the Unity Runtime on the cloud or a remote server. For a list of Unity authorized streaming platforms, Managed Services and SDK Integrations, click here.This restriction does not prevent end users from remotely accessing your Project Content from an end user device that is running on another end user device. You may not use a third party to directly or indirectly distribute or make available, stream, broadcast (through simulation or otherwise) any portion of the Unity Software unless that third party is authorized by Unity to provide such services.
Here's  what it used to say:
> You may not directly or indirectly distribute the Unity Software, including the runtime portion of the Unity Software, or your Project Content (if it incorporates the runtime portion) by means of streaming or broadcasting so that any portion of the Unity Software is primarily executed on or simulated by a server and transmitted over the Internet or other network to end user devices without a separate license from Unity. This restriction does not prevent end users from remotely accessing your Project Content from an end user device that is running on another end user device. You may not use a third party to directly or indirectly distribute or make available, stream, broadcast (through simulation or otherwise) any portion of the Unity Software unless that third party is authorized by Unity to provide such services.
Whether that's a change or clarification of Unity's intent is rather subjective.
I must have a very different set of eyes than Mr. Sweeney here. But the first 200 or so replies were made before Unity could even post a response. They were mostly speculations and mods asking people to calm down and wait for an official response. This is mostly because Improbable's first blog post did not give any specifics and made it sound like Unity pulled the plug overnight (later according to Unity, Improbable knew about the TOS violation for over a year).
So then Unity made a response blog post. Improbable made a 2nd blog post. And Epic made their 25mil announcement. Then, that Unity thread has pretty much turned into a conspiracy thread fueled by the f#$@ed up timing of everything. "Highly intelligent" and "insightful debate" would not be my choice words to describe that thread.
And lastly, I want to say, even if Mr. Sweeney had all the good intentions, it was really painful to see Epic capitalizing on Unity in such quick manner and intensity. I was actually in agreement with his tweets before he posted the lame thread link and announced the 25mil fund to help people transition from Unity to UE4.
Why would Improbable continue to support Unity long term when it's a dead end for them?
Unity has just done something actively hostile to their users, and they're attempting to downplay it, poorly.
It's Improbable who acted badly here.
Unity is trying to tell me, as a game developer using their product, where and how I can use the built executables generated from their editor.
I have no interest in Improbable and this has been a major shot across the bow for me.
And speaking of openness, didn't Epic push exclusivity approach recently in their store? That's bad.
Which is very much in alpha but quite promising.
This just isn't possible with game engines. They are the single most advanced pieces of desktop software in existence. Sure, there are things like Godot that are perfectly suitable for a simple indie game. But making a AAA game engine requires the expertise of literally hundreds of top level senior engineers with advanced physics and mathematical knowledge. There's probably less than a few thousand people on earth with the level of skill and expertise to build something at the scale of UE4. Furthermore, open source is really the exception to the rule in game dev. Practically everything is done closed source with some kind of licensing fees involved. It's quite a different culture from web dev.
Unity fucked up hard here and I hope that their planetary-level screw up will lead to game developers pushing for open source engines to avoid the control of their games being stolen.
I'm not saying there aren't talented developers working in open source. But the sheer breadth of expertise required is unimaginable. You need top-of-their-field engineers from practically every conceivable discipline within CS to build a AAA game engine. Physics, lighting, rendering, networking, audio, UI, and that's just the tip of what I can think of. Engines like Rockstar's RAGE are easily on par with the Linux kernel for complexity.
But you've mentioned it yourself, so you presumably don't see that as a contradiction.
What do you think makes the complexity of Linux achievable with FOSS while the comparable complexity of a AAA engine not?
It just comes down to incentives. Practically every living human being stood to gain from the existence of a high quality general purpose FOSS operating system, and so Linux naturally came about.
The people who would benefit from a AAA open source game engine are... closed source AAA game development studios. As such there's really no incentive for some physics whiz to spend their extremely valuable time toiling away on something that is only going to be used for someone else's profit. The intersection of people who build game engines, and people who make games with those engines, is extremely small.
There's really no such thing as open-source game development except for hobbyists, because that would be literally giving your product away. Games are a hit based, one-and-done type product much more akin to movies than other software.
Clearly there's something because it hasn't been done. Why do you think there are no high-quality FOSS engines?
In my opinion, the problem rather is that the skills that are helpful/necessary to build "typical" open source software are really different from the skills for a good game engine.
About this time last year, I wanted to make a simple little 2D platform game in Godot and my experience was mixed. Some stuff was really easy and pleasant, some stuff was middling and then other stuff was frustrating enough that I gave up: for example, I had to spend an entire day just so I could get sprites correctly sorted so that tilemap tiles and objects that were in front of the player would be drawn in front and those that were behind were drawn behind. Basic stuff. There’s an option to enable for this (y-sort) but it did not work without a bunch of unintuitive tweaking. The docuentation didn’t help, reddit couldn’t help, their discord couldn’t help and I wasted a lot of time on it.
Having said that, I have high hopes for Godot and I do think it has a bright future, but it has a ways to go. I’ve even made some (very small) contributions to the gdnative c++ library, so its not like I’m just complaining ;)
My point is that Godot doesn’t get much interest for more reasons than just consoles (there’s commercial support for porting available). But, as you say, the culture change is happening, it just needs time.
Did it? Lot's of gamers see consoles as something that holds developers back from using better hardware, since they need to target 5 year old systems. Quality both artistic and technical isn't something consoles can claim to be leading in. And clearly, "consolization" in its various forms isn't something gamers appreciate, when it spills out into PC gaming.
And that in spite of some bad apples still going through the gates, the large majority of flappy bird clones never makes.
The average game on a console is going to be higher quality than the average game on PC because the average game on PC has to include the game I made in Visual Basic 6 when I was in high school. With no gatekeeper ensuring basic quality, my VB6 game is every bit as legitimate of a game as Battlefield 5. They both hold the title of "PC Game", but only one of them could ever be called "Xbox Game" because Microsoft would never allow my game on their console.
For example in demoscene the art is to make these old consoles or computers do wonderful things that seem impossible on such limited resources.
> There's probably less than a few thousand people on earth with the level of skill and expertise to build something at the scale of UE4.
That's really bunk. I mean "only elite can do it" it claim. Sure, it's not something you can create in one day, but it's not something that out of reach either, especially when people are collaborating on it.
The graveyard of hundreds of abandoned open source game engines begs to disagree with you. I agree that it seems absurd, but you really can't underestimate the amount of man hours put into these things. Unreal has been under constant development for over 20 years.
It's the same as flight simulation. Why is there only one viable flight simulator (X-Plane) on the market? It's because that kind of coding is simply beyond 99% of developers, and it takes a huge well funded and focused team to make something state of the art.
I wouldn't cite open source codecs as a success story ...
A GUI toolkit is probably more on point and of the correct scale, and those also demonstrate that without significant backing from somewhere, progress doesn't get made at that level of complexity.
A commercial quality game engine is a huge project, and as such, requires a huge projects worth of time and effort to build. Same as any other huge software project (which all have countless abandoned open source attempts). Remember that most open source projects start of tiny (one developer is common, certainly very few start off with more than a handful) and work on it in their free time, while commercial teams like Unity have hundreds of peolpe working on it full time.
The reason they are abandoned is typicaally that 1) the developers, who are doing it in their spare time, don’t have the time anymore; or 2) they get frustrated at the amount of work/lack of contributors/lack of interest and stop working on it; or 3) they simply lose interest and work on something else.
Its not lack of ability, its lack of time/motivation/interest to keep working on it for many, many years.
- Understanding of modern CPUs / GPUs and the capabilities/shortcomings they have
- Understanding the behaviors and quirks of the OS
- Familiarity with multicore programming
- Skillful memory management (such as making your data structures less prone to cache invalidations)
- Mastery of a low-level language (C++, Rust, whatever)
- Familiarity with build systems (CMake, SCons, etc, ... or sometimes you might have to roll your own)
Already I could see the number of contributors who would know all this stuff being pretty low. (I've dabbled a bit in graphics and made a simple OpenGL scene graph renderer and a fluid simulator, but I still don't feel like I'm competent enough...)
An engine is comprised of multiple components (Graphics, Sound, Physics, etc...). So you wouldn't need to know all of it, but contributors would need to have a clear grasp on at least one. So for each component, you would need...
- Entity System: You need a universal way to handle game entities. Implementing it efficiently requires a good knowledge of computer systems, because you need to think carefully about how you store data in the memory.
- Job System: You need a system to execute various tasks (rendering, physics, game logic, ...) simultaneously on multiple processors, so that a single game frame can finish in less than 16 milliseconds. Implementing this would require some knowledge in concurrency as well as OS concepts.
- Resource Management: You need a way to store and keep track of the game's various data stored in files, such as images, models, sounds, game objects and their parameters, settings, etc. You need to implement efficient serialization and compression for this.
- Graphics: Mastery of a graphics API (OpenGL, DirectX, Vulkan), and understanding its various patterns and shortcomings. You also need knowledge in how rendering works (which also requires some math), and nowadays a PBRT renderer (https://www.pbrt.org/) is basically a minimum requirement for modern 3D game engines.
- Physics: Lots of math and physics (Linear Algebra, Differential equations, Mechanics, etc.), and also optimization skills like assembly and SIMD (speed is critical in this area!). Fortunately many people just use already-built middleware such as Havok or Bullet..
- Sound: This is actually the most neglected part in game engine development, and it is hard to find good resources on this.
I think the people who would have the knowledge to build a game engine would be already busy working on other stuff, such as working for an AAA gamedev company (which sometimes does a lot of crunch, so they might not have enough time for open-source stuff), or a proprietary game engine company like Unity or Unreal. But I still see some hope around the edges. From what I've seen, Handmade Hero (https://handmadehero.org/, which is a livestream of making a game engine from scratch, accompanied with various education materials) is the most impressive. It tries to teach those skills needed to make a game engine to interested programmers, which I think is a crucial first step in encouraging open-source gamedev.
Some examples: for entitiy systems, EnTT is amazing. For a job system you’ve got stuff like cpp-taskflow, for physics there’s bullet, for graphics there’s bgfx or full blown renderers. Sure, these won’t solve all of your needs, but they’re a good starting point that frees you from having to do a lot of stuff yourself.
You need to be damn near Johnathan Blow levels of skill and perseverance to create a decent game engine.
Maybe you wouldn't classify him as an "elite", but I sure would.
Won't be easy for sure, neither on technical nor marketing level. Many of the successful examples took 10+ years before they got really viable. But to say it is impossible to do this for a game engine, just because no-one has done it yet, is defeatist.
Thankfully, there are millions of people who can build something at the scale of linux or firefox. Why else would it be possible for them to be open source?
The best way to break that is to not sell games on Steam. Another way is what Epic is also doing, giving away free games to build up people's library on their store as well.
Not really, I personally go and buy it on GOG. Sure, Steam is the biggest store these days, but there is competition. And it's good when developers release in all stores. That's the proper way.
Exclusivity is a bad method to fix monopoly, since it simply creates another monopoly. I.e. if you had one problem, now you have two.
Maybe you're thinking of the Humble Bundle? Many products there are sold as Steam keys.
But if there was a single interface and all I had to do was add my credentials for store X? That's not so bad.
For every person that buys directly from the developer, I expect there are several order of magnitudes more people that buy through steam. If you're a drop in the ocean, that doesn't count as "not really".
or maybe the whole thing was orchestrated? I honestly can't fathom how people are buying the story that Improbable is putting out. It's ludicrous.
Section 4.4 says you can't launch any game on their tech without speaking to them first, and you have to get explicit permission to not use Steam, or their "content launcher"
I wonder if Epic noticed that. Because that's bad for their own store.
More open game engines = more high-quality games from developers that can be acquired, or lowering the barrier to see what new game types start gaining traction so they can come in with a AAA version of the next MOBA, Fortnite, Minecraft, etc.?
Then again, I remember the days of ZZT. It wasn’t an open source engine, but there were a lot of games made on that engine.
I guess making a AAA version of a good indie concept makes economic sense.
SpatialOS provides managed cloud services that solve common technical and production challenges when you’re creating, iterating on and hosting multiplayer games.
SpatialOS: the cloud platform for real-time multiplayer games, built with any game engine.
I mean if they were serious about open engines they might fund a DirectX 12 upgrade for Irrlicht or something.
There's OGRE as well of course, but I seem to recall there was some weird preprocesser step to compilation that put me off it: https://www.ogre3d.org/
> Due to a change in Unity’s terms of service (clause 2.4)
The text they're talking about is dated December 5th. This capture was taken while that Improbable blog post was fresh, on January 10th:
So section 2.4 is at least a month old at this point. They said nothing to their customers for over a month? Then they created a storm in a teacup, and a bunch of developers freaked out and took their own games down on their own account without ever receiving any sort of notice with Unity. Improbable intentionally manufactured a panic: none of these game developers were contacted by Unity or asked to take their games down.
Section 2.4 is nearly identical in the February 2018 ToS by Unity as well: http://web.archive.org/web/20180616042117/https://unity3d.co...
So Unity's response (here: https://blogs.unity3d.com/2019/01/10/our-response-to-improba...) that they talked to Improbable and told them they were in breach of the ToS over a year ago is supported by the actual history of the ToS.
Consider a few things: Improbable is not actually an innocent little lamb here: they have raised over $600m of VC money. Their Series B was over $500m: https://improbable.io/company/news/2017/05/11/improbable-rai...
And then there's the other thing: SpatialOS is NOT an open system. The fact that they're playing up their openness is the definition of smarm: the form of virtue without the substance. They have an open source client but the server is not open source. You can't run your own SpatialOS instances. If you integrate their GDK into your game, you can ONLY use their managed services to host your multiplayer server. It's purely a vendor lock-in model, they just pretend to be open source by having open source clients.
None of the articles that have written about this have had anything to say about Improbable's ToS, none have reached out to Unity for comment, and none have reached out to any of the game developers whose games "were affected", when none of the games were issued any sort of notices by Unity and none of the games had any reason to be taken offline. Everything about this story has been driven entirely by Improbable, without any scrutiny whatsoever, but if you look more closely at what's going on, there are a lot of stones to turn over.
My suspsicion is the price was too steep for Improbable, but they should have been talking to Unity about costs from the beginning. Even I have a backup plan.
And Epic... I didn't like the way they rolled out the "free" version of UE4, perfectly timed to fuck with Unity and this certainly feels similarly sleazy. Back in 2006 when I was first attempting to do some 3D interactive projects, I couldn't even EVALUATE unreal engine without paying something like $500. Unity was a miracle.
This isn't some shack behind an old farm, it's part of a historic mansion complex: https://en.wikipedia.org/wiki/Hyver_Hall
If Improbable and Unity have a dispute - so be it. But they should have given 6 months notice that negotiations have failed and that services would no longer be available via Unity.
Its just all-round bad news for Unity though. With cloud services and multiplayer going to be a major force of gaming in the next 20 years - how much do you want to invest in a game engine which has locked you out of using an ancilliary service?
Unity need to just move on to charging a % of total revenue like Unreal does.
If Unreal used C#, I would have used that. But the reality is that as a micro-studio, its really difficult to find C++ programmers. In some cities there are 20x as many Unity programmers as Unreal programmers. Generally Unity is a bit more reliable and less crashy as well.
IANAL but for me that looks like also banning the usual method of implementing your games server in Unity if we think it also bans SpatialOS.
For me the old terms look like trying to get more money from services like PlayStation Now. However if they really did forbid SpatialOS then that means every single mobile game with server implemented in Unity are also breaking the TOS and should be shut down asap.
Rergardless this debacle proves that Unity is more than willing to interprete their TOS quite liberally if they smell money. So if you build a big MMO that rakes in billions you should expect Unity to barge in and use that, or some other, part of TOS to demand more money from you.
EDIT: My hunch in how this went down. Year ago unity told them that 2.4 breaks the TOS and wanted more money. Improbable said "Nuhhuh, can't you read?" until Unity changed their TOS and said "Yeah! It does!".
So if Unity ever says that you break their TOS and they want money it's better to pay them regardless of what the TOS says because otherwise they just change the TOS retroactively.
> Rergardless this debacle proves that Unity is more than willing to interprete their TOS quite liberally if they smell money. So if you build a big MMO that rakes in billions you should expect Unity to barge in and use that, or some other, part of TOS to demand more money from you.
Everyone that defends Unity here seems to forget that, which is 100% of the issue here. When Unity warns them a year before or whatever won't change a thing, theses terms are so wide that everyone using it on their servers are in danger and this is the true issue.
There's not a single time frame that would allow any game to move out of Unity, even more so a whole platform like SpatialOS that would imply many games. That would be incredibly expensive too.
Personally you would have told me the same a week ago, I would have said I trust Unity not to do that to their customers, now because of Improbable, I know this is false. Now I know that if they see more money to be made, that I would actually actually lose the rights over my games binaries.
Even from Improbable's standpoint it made at least some sense for them to assume it was just personal bullying until the very minute Unity made it a public issue.
Which I highly doubt. But IANAL.
It just seems silly that it went “your in breach of our conditions!” “No we aren’t” “Yes you are (also we just now changed them”.
"You're in violation of the ToS."
"Our legal team looked it over. We don't think we are."
"Well here's a more clear version of the ToS. You definitely are in violation."
Unity might think they only changed the wording, but they feel they kept the spirit of the original ToS.
Instead Steam/Valve should fund open-source game engines and development tools. For them it is a complement to their business model, so the incentives are aligned. And they can ensure a smooth path to market for the game developers. Everyone wins (well, maybe except for Epic/Unity).
It's AAA games that use their own engines and developers that are too lazy to click the Compile for Linux button in Unity that are holding us back.
I would be extremely surprised if that was true for anything other than relatively simple games. No matter what cross-platform abstraction you use, you can never totally get away from dealing with the actual platforms.
Snark aside, PUBG built a little on the battle royale formula. Fortnite built a little on the battle royale formula. Both Bluehole and Epic Games were madly successful. Maybe PUBG would've done even better had Fortnite BR not done so well as a free to play experience. But it could've also done better if it wasn't a buggy mess for like an entire year after launch, one that costs $20 and never seems to be on sale.
There's a reason gameplay mechanics aren't copyrightable. This is how game design evolves. I'd hate to live in the world where ID software permanently owned the rights for making first person shooting games.
One could certainly argue there is some conflict of interest in that Epic Games has a conflict of interest because they licensed their engine to Bluehole. But Unreal Engine is a fairly popular game engine, and I think it's unreasonable for them to not be able to be inspired by games written on their game engine.
Wasn't there a problematic patent on The Incredible Machine that kind of killed that genre for a while?
Although Jeff Tunnel was really pissed off by it, which as a fan of TIM growing up makes me very happy.
You can't copyright a game mode, and PUBG took lots of aspects from others too.
And also Epic themselves stated Fortnite was their "own version" of "Battle Royale games like PUBG"
I've played Fornite. I've played Fornite BR (at release). They were obviously a clone. What is Fornite now is something drastically different.
Anyone who doesn't call Fornite a clone of PUBG obviously only started playing Fornite BR and Fornite BR alone much later.
Bluehole squandered part of their momentum by failing to continually rebase and track UE4 improvements that were made specifically for them. Allowed hackers to take over the game, and then cried foul when their player base dropped.
Also people seem to forget that H1Z1 had a royale mode before PUBG existed. ARMA 2 also had a mod, made by the same creator, who based the idea off of a movie of the same name.
If a company goes to Unity, they'll have to be careful that at any time they'll may remove your right to distribute your own game binaries. They don't even need to clone anything!