🍪 Game Engines Became Gaming’s Messiest Drama

Hello there, frame-rate detectives and launcher survivors. Today we’re talking about game engines, the invisible machines behind modern games and, somehow, one of the spiciest drama factories in the industry.

Most players don’t care what engine a game uses until the game stutters, crashes, looks weird, eats their storage, or runs like their GPU personally insulted the build. Then everyone suddenly becomes a technical director in the comments. “It’s Unreal.” “It’s Unity.” “They should have used Godot.” “Bring back custom engines.” Fine. Sure. Also my toaster has opinions about shader compilation now.

The funny part is that engine gossip actually matters. It affects what games look like, how they perform, what studios can afford, how easy it is to hire developers, and how much control creators really have over their own work. A recent VG Insights report covered by 80 Level found that, among over 13,000 Steam games released in 2024 with at least 1,000 sales, Unity powered 51 percent of shipped games, Unreal powered 28 percent, Godot 5 percent, GameMaker 4 percent, and proprietary engines made up less than 10 percent. Unreal’s sales share jumped from 19 percent to 31 percent, boosted by big releases like Palworld and Black Myth: Wukong.

That is the engine drama in one ugly cookie bite. Unity still ships a ton of games. Unreal is eating more of the high-profile conversation. Godot is turning into the indie rebellion. GameMaker remains the cozy 2D workshop. CryEngine is the old legend people mention like a retired boxer who once punched the entire PC market in the jaw.

And behind all of that, developers are making a choice that feels less like “which tool fits my game?” and more like “which cursed landlord do I trust with my next five years?”

Unreal Engine is everywhere, and that is where the gossip starts

Unreal Engine has become the obvious choice for a lot of studios because it offers serious visual power, a known pipeline, a large talent pool, strong documentation, marketplace assets, and a business model that feels friendly until your game becomes successful enough to owe royalties. Epic Games also made the deal sweeter with its “Launch Everywhere with Epic” program, reducing Unreal Engine royalties from 5 percent to 3.5 percent for eligible games that launch on the Epic Games Store at the same time as other stores.

From a business perspective, the attraction makes sense. Why spend years maintaining your own engine when Unreal gives you cinematic lighting, modern rendering, tools designers can use, and a hiring market full of people who already know the workflow? For publishers under pressure, standardizing around Unreal can look like responsible production planning.

Players, of course, are not looking at a production spreadsheet. They are looking at the frame-time graph having a panic attack.

The loudest Unreal gossip right now is performance. Tim Sweeney argued in 2025 that many Unreal Engine 5 performance problems come from studios building first for high-end hardware and leaving optimization for lower-spec devices too late in development. He also said Epic is working on automated optimization features and more developer training to address the issue.

That answer did not calm the room. Some developers and players agreed with him, because yes, optimization at the end of production is basically trying to install brakes after the car has already entered traffic. Others pushed back because when many games using the same engine show similar stutter, shader issues, heavy CPU demands, or blurry upscaling, people start blaming the shared tool.

🦊 Kiki: I get why Unreal became the shiny default. I really do. If you’re a studio lead staring at a budget, a deadline, hiring problems, and shareholders breathing like horror-game monsters behind you, Unreal looks like the adult choice. It has the tools, the brand, the talent pool, the big cinematic promise. But players don’t experience “workflow efficiency.” They experience the game freezing during a cutscene while their console fans sound like a jet trying to leave the planet. And then everyone acts shocked when the comment section goes feral. I’ve seen this cycle too many times. Trailer looks gorgeous. Preview says “next-gen visuals.” Launch day arrives and suddenly the game needs DLSS, frame generation, a prayer candle, and three patches to stop coughing. At some point, the industry needs to admit that photorealism with unstable performance is not a flex. It’s a very expensive way to annoy people.

🍪 Chip hugs a tiny graphics card and slowly backs away from a settings menu.

The “Unreal look” is becoming its own meme

The other complaint is less technical and more aesthetic. More games are starting to feel like they came from the same luxury showroom: glossy rocks, cinematic blur, heavy foliage, dramatic lighting, wet surfaces, realistic faces that somehow still feel a little spiritually unemployed.

That is not entirely Unreal’s fault. A good art team can make Unreal sing in a thousand different styles. The problem is that powerful default tools create gravity. When a team is short on time, using familiar lighting, marketplace assets, default post-processing, and common workflows becomes tempting. Then players start noticing the same visual flavor everywhere.

That is where the gossip gets interesting. Unreal is not “ruining art direction,” but it can make certain choices easier, cheaper, and more defensible. When enough studios make those choices, the engine starts to feel like an aesthetic trend instead of a tool.

And the more studios abandon proprietary engines, the more this concern grows. The same 80 Level report noted that proprietary engines still accounted for around 42 percent of total units sold in 2024, even though they represented less than 10 percent of Steam games released that year. That suggests custom engines are still powerful where they survive, but fewer studios are willing or able to keep building their own tech.

Unity burned trust so badly that people still smell smoke

Unity’s drama is different. Unreal is being accused of becoming too dominant and too heavy. Unity’s scandal was more personal. Developers felt betrayed.

In September 2023, Unity announced a Runtime Fee that would charge developers when games using Unity were downloaded after hitting revenue and install thresholds. The Guardian reported that the fee would begin after $200,000 in revenue over 12 months and 200,000 installs, with charges up to $0.20 per install depending on license. Developers immediately raised concerns about reinstall abuse, subscription services, bundles, free-to-play models, and the basic horror of having your engine vendor change the economics after years of development.

Unity eventually scrapped the runtime fee in 2024 and returned to a seat-based subscription model, but Reuters reported that Unity Pro prices rose 8 percent and Unity Enterprise rose 25 percent starting January 2025. Reuters also noted that the original pricing structure triggered customer backlash, hit Unity’s share price, and was followed by a company reset that included workforce cuts and office closures.

The gossip version is simple: Unity tried to put a meter on success, everyone screamed, and then Unity walked it back after the trust damage had already entered the bloodstream.

🦊 Kiki: Unity used to have this weird emotional role in indie development. It was the “yeah, you can actually make something” engine. Students used it, small teams used it, mobile teams used it, weird experimental devs used it. It felt accessible, sometimes messy, sometimes bloated, but familiar. Then the Runtime Fee happened and the whole vibe changed. People were not just mad about money. They were mad because it reminded them that a tool can become infrastructure, and infrastructure can suddenly wake up one morning and ask for rent in a new language. That is why the reversal didn’t magically fix everything. You can cancel a fee. You cannot instantly reinstall trust like a missing package dependency. Developers remember when the floor moved under them.

🍪 Chip tapes a tiny “terms changed” warning label onto a cookie jar and looks deeply stressed.

Godot became the indie rebound relationship

Godot benefited from Unity’s mess because it represents the opposite emotional promise: open source, no royalties, no subscription anxiety, no corporate overlord changing the pricing model in a quarterly panic. For many developers, Godot is attractive because it feels like a tool they can trust, inspect, modify, and keep using without wondering if a surprise invoice monster is hiding in the EULA.

Its momentum is becoming easier to see. GamesRadar reported that Godot’s Steam presence has grown sharply, with the number of Godot games on Steam rising from 375 in 2023 to 1,229 in 2025. The same report noted that Slay the Spire 2, originally built in Unity before moving to Godot after Unity’s fee controversy, launched in March 2026 and reached a peak of 574,638 concurrent players on Steam.

That is huge for Godot’s reputation. A successful, visible game does more for an engine’s credibility than a thousand “is Godot ready?” arguments. Players might not care what an engine is, but developers absolutely notice when a major release proves the tool can survive outside hobbyist discourse.

Godot’s gossip problem, though, is growth pain. In February 2026, GamingOnLinux reported that Godot maintainers were dealing with a flood of low-quality AI-generated pull requests. Maintainer Rémi Verschelde described the situation as draining and demoralizing because reviewers now have to second-guess whether new contributors understand their own code, whether it was tested, and whether verbose descriptions are just LLM fog.

So Godot has the funniest possible problem for an open-source darling: people love it enough to help, but some of that “help” arrives as AI-generated garbage homework.

🦊 Kiki: Godot is in that dangerous phase where everyone wants it to be the hero. I like Godot. I like what it represents. I like that it gives developers a way to say, “Actually, I would rather not build my entire game inside a corporate mood swing.” But the fan energy around it can get a little culty, and the AI slop issue is such a perfect 2026 problem that I almost hate how predictable it is. A bunch of people using AI to generate contributions they don’t understand, then dumping review labor onto unpaid or underpaid maintainers. Amazing. We automated being annoying. Godot’s strength is the community. Godot’s problem is also the community when the community forgets that open source is not a content farm for your GitHub profile.

🍪 Chip opens a pull request, sees 4,000 lines of nonsense, and quietly closes the laptop.

GameMaker is the little 2D gremlin that refuses to die

GameMaker’s gossip is quieter because it knows what it is. It is not trying to be the engine for every cinematic open-world dream project. It is a 2D-focused tool that lets people make games quickly, especially beginners and indie developers.

That simplicity is why it has real cultural wins. GameMaker has been used for games like Undertale, Spelunky, Hyper Light Drifter, Hotline Miami, and Katana ZERO, according to PubNub’s engine comparison.

The official pricing also makes its lane clear. GameMaker’s FAQ says the free version lets users create games and export to desktop, mobile, and web, while selling games requires a $99.99 commercial license. Console developers need an Enterprise subscription.

The downside is obvious. GameMaker is not built for serious 3D. Its scripting language, GML, is easy to learn but proprietary, which makes skills less transferable. It can run into performance problems on complex games, and advanced multiplayer requires more work because there is no native advanced multiplayer networking support.

Still, GameMaker survives because finishing a game matters more than winning engine discourse. A beginner who finishes a weird 2D project in GameMaker has done more than someone who spent six months arguing whether Unreal is “real development.”

CryEngine is the tragic ex everyone still talks about

CryEngine used to be the engine that made PCs cry. The original Crysis became a meme because it looked so far ahead of its time that “Can it run Crysis?” became a hardware personality test. GameFromScratch described CryEngine as one of the most exciting engines of its era, known for pushing graphical boundaries and powering high-profile games that helped define Crytek’s reputation.

Then the path got messy. Ubisoft’s licensed CryEngine technology helped lead to Dunia. Amazon licensed CryEngine and turned it into Lumberyard, which later evolved into Open 3D Engine. Crytek continued using CryEngine internally, including for Hunt: Showdown, but the public future became murky. GameFromScratch reported that CryEngine 5.7 LTS from April 2022 was the last public update and that Crytek said the 5.7 LTS version would be the final public release of the 5.x branch.

CryEngine’s story is a warning. An engine can have legendary technology and still lose mindshare if the ecosystem, support, documentation, public roadmap, and developer confidence fall behind.

That is the cruel part of engine wars. The best tech does not always win. The trusted pipeline wins. The hiring pool wins. The community wins. The engine that still looks alive when a producer asks, “Can we staff this?” usually wins.

Engine drama affects players more than they think

Players usually meet engine decisions at the worst possible moment. They do not sit in meetings where a studio chooses Unreal to reduce tech risk. They do not see the spreadsheet explaining why maintaining a proprietary engine became too expensive. They do not hear the debate about whether moving to Godot reduces licensing anxiety. They just buy the game.

Then they feel the consequences.

If too many studios standardize around the same engine, players may see more visual sameness. If a studio moves from a mature internal engine to a new tool too late, players may get stutters and weird performance tradeoffs. If an engine company changes pricing, studios may delay projects, migrate tools, cut scope, or absorb costs that eventually shape what players get. If open-source projects drown in low-quality AI contributions, maintainers lose time that could have gone into actual improvements.

The engine is backstage, but backstage keeps catching fire.

🦊 Kiki: I think players should care about engine drama, but not in the lazy “blame the logo on the splash screen” way. A bad PC port is rarely just one villain sitting in a chair labeled ENGINE. It is usually scope, deadlines, publisher pressure, optimization timing, asset choices, QA time, platform targets, and some poor technical artist trying to make a 4K rock behave like a reasonable citizen. But engines shape the mess. They decide what is easy, what is expensive, what gets automated, what gets ignored, and what teams can hire for. That is why this gossip matters. It is not nerd gossip for people who enjoy compiler errors as a hobby. It is the quiet business drama behind why your $70 game sometimes launches like it was assembled during an earthquake. And yeah, sometimes the answer is just “they should have optimized earlier.” Revolutionary. Someone put that on a conference badge and charge $799.

🍪 Chip holds a tiny conference badge that says “Optimize Before Launch” and nods with tragic seriousness.

The engine wars are really about control

Unreal offers power and industry familiarity, but its dominance creates anxiety about sameness and dependency. Unity still has huge adoption, but the Runtime Fee scandal turned it into the cautionary tale every engine company should have taped to the office fridge. Godot is growing because it gives developers freedom, but freedom comes with resource strain and community chaos. GameMaker remains a practical 2D machine with clear limits. CryEngine shows what happens when brilliant tech loses ecosystem momentum.

That is the real engine story. Developers are not just choosing rendering features. They are choosing a business relationship, a hiring path, a risk profile, and a future maintenance nightmare.

And players are living with the results.

So the next time a game launches with stutter, blurry upscaling, or the visual personality of a damp tech demo, blaming “the engine” might be too easy. But ignoring the engine would be naïve. The tool does not make every decision. It quietly shapes a lot of them.

⚙️ Stay skeptical, like every developer who now reads pricing updates with one eye twitching.
⚙️ Keep questioning, like every player wondering why “next-gen visuals” keep arriving with day-one performance patches.
⚙️ And remember, the engine war is funny until your favorite game becomes the benchmark nobody wanted.

🦊 Kiki · 🍪 Chip · ⭐ Byte · 🦁 Leo