10 Hardest Video Game Genres To Make (From A Game Developer)
Don't start here if you want any hair left by thirty.
It's fairly evident to anyone that some games just take way, way more effort to develop than others.
There's a reason why the match-three puzzle game or a basic endless runner is normally the best place to start if you're learning to develop; they're self-contained, require very few assets, and have limited systems to build in order to see a working product.
But what about the other side of the spectrum? What's the HARDEST game type to build, besides the "Whingy Gamefaqs Posters DON'T Regard This As Garbage" category (which, up until now, has the fewest entries of any game subgenre)?
No doubt the answer will differ depending on which developer you ask, but these tend to be the most prevalent answers.
TOP TIP: Don't start your developing career with these.
10. Balanced Fighting Games
Maybe a bit of a surprise entry here, because fighting games buck the idea that having fewer assets... means an easier or simpler product to create overall. But whilst the amount of work required to create a basic fighting game isn't huge, the amount of effort needed to make one balanced and sustainable definitely is.
It's pretty easy to build a fighting game, but it is INCREDIBLY difficult to build a balanced one.
When making a fighting game, it's tempting to think of a diverse and exciting cast of unique characters to choose from right from the starting line. After all, that's one of the cornerstones of a great fighting game, right?
Well, yes, but a far more successful process for building one requires the team to completely exhaust the design for one character, first, starting with just that singular character battling against itself over and over in an attempt to balance them.
Ryu vs Ryu, for weeks upon weeks. It's like every Street Fighter 4 tournament, circa 2009.
The scary thing after that, is... that process grows exponentially. You have one character? Then you have one interacting pair of characters every match, to balance. You have three characters? That's nine interacting pairs to balance.
If you have a proposed roster of twenty-five characters, suddenly you have to balance six-hundred-and-twenty-five interacting pairs. Oof.
Just thinking about it makes me feel like I've taken a full Ultimate Raging Demon to the brain.
9. Live Service Shooters
Though balancing most online games (especially ones with varied and contrasting ability and equipment pools) is already a tricky challenge, the distinction of "most difficult" in this category goes to the live service shooter.
Unlike a session shooter like Counter Strike, a live service game has to be marketed, monetised, and balanced as if it's an organic creature - always on, always awake, always available.
This requires a deceptively high level of resource and overall effort... because whilst it might be tempting to just maintain the level of success and engagement your game currently has, the interest will wane rapidly without regular and significant content updates. And be assured, that if your designers estimate the content your team creates will last the average player twenty hours, that just means one maniac is going to blast through it in five, then complain there's nothing to do.
So, it's worthwhile to have two development strike teams working in tandem - one to balance and maintain the game as it exists, live, and another to produce the content that players will voraciously guzzle down in the future.
After the latter team deploys that content, it'll be the former team's job to balance that new content, and so the cycle continues.
"Here's the new battle pass we've been working on for months! It's four-thousand levels of difficult and exciting new content, ready fo... aaaaaand, someone's completed it already.
Great."
8. Games With Branching Progression Systems/Narratives
"Fractals" is the term used by some designers as shorthand to describe the often-headache-inducing branching trees that gamers love; branching trees (in terms of narrative, character abilities, and more) often mean your game is going to offer the player more choice and agency, but that also means the work required is going to multiply, often several times over.
Branching narrative paths occur when a character has to make (often pivotal) choices which alter the events yet to come. When considering a branching narrative path, the earlier the branch occurs, the more work is going to be required overall.
If, after one hour, your player has to choose between taking the crown to be king of the realm, or leaving the realm to be a space raisin (and each choice leads to a unique eight-hour story), the unchosen option is eight full hours of gameplay some players will likely never see. And if at the end of those stories another binary choice is offered, then you can see how the vast majority of the game you're developing is going to go completely unseen.
You can see how it becomes significantly more value for developers to instead just... create the same amount of content, but offer it all, instead of offering these branching paths.
Fractal progression systems aren't quite as demanding on content, but require a heavy amount of time spent on balance (with the exact same problem, that most players will never even see some of that content).
Branching systems are maybe the only entry on this list that're so time-consuming to make because of what the player won't see, as opposed to what they will.
7. Simulation Racers
I think it was Stephen Fry that said, "the more passionate [a person] gets about something, the more unreasonable they become when you suggest they don't know everything about it."
Having worked on several AAA driving games with car enthusiasts, I can attest to this being completely correct.
The people that make simulation racing games are car nutters. They know to within the millilitre how much wiper fluid a Subaru Impreza Turbo holds, and they dislike being questioned on their sources. They just know.
So then, that meticulousness is transferred over to the development of their sim racer, with every minuscule detail accounted for, in a manner considered overkill to anyone outside of the big car community bubble. However, you soon realise that fastidious attention to detail isn't surplus to requirements at all, because the only people more defensive about their knowledge than car devs...
...are sim racer players.
There are entire communities dedicated to finding inconsistencies between real vehicles and their in-game counterparts, and they don't care one single Magic Tree if the car stats were correct at the time of development and then changed afterwards - these sticklers for detail require complete accuracy, all the time.
Unless you're willing to keep your level of detail firing on nitrous the whole time, I'd steer clear of sim racers.
6. Asymmetrical Multiplayer Games
Asymmetrical multiplayer games, like Dead By Daylight or the much-overlooked Evolve, differ from standard multiplayer games in that both teams have distinctly different goals. For example, one team might try to get to the extraction point, whilst another team plays as John Goodman and Roseanne Barr, attempting to bite off their heads. It's often the unpredictability and strategy of trying to predict what another human player might do that leads to the most fun moments.
This is probably the most contentious on this list, because depending on which developer you talk to, asymmetrical multiplayer titles are either easy to make, or an absolute nightmare. There doesn't seem to be any happy medium.
This is probably because it's assumed - nay, expected - that there's going to be game imbalance. After all, if your players are playing as vastly different characters with contrasting objectives, it's mad to expect parity between everyone.
So, you can either lean into this aspect, or fight the Sisyphean challenge of trying to make the game fair when one or more of your players is expected to be overpowered. Whilst there are other aspects of design that make asymmetrical multiplayer games tricky to create, it's this unique "do we, or don't we?"-aspect of design that creates the biggest migraines.
After all, why nerf Roseanne? Part of the fun of playing as her is KNOWING you can decimate all the peons!
5. VR Games
Most people that play on a VR headset for the first time are astounded by the technology.
"I've got to get one of these!", they bark. "This blows regular gaming out of the water!"
Yet, when they finally buy an Oculus Quest, it's brought out every couple of weeks to play Lights Music Cube Cutter, then stored away to collect dust and owl faeces (in this example, the person in question lives in the upper floors of a barn).
So then... attachment rate is low (people with VR headsets don't typically spend as much on VR games as core gamers do). Not to mention that VR in itself is still relatively niche as a format. Those factors alone would make VR game development a tough gamble, but we also have to take into account... y'know, the games themselves.
Elements of difficulty building for VR are numerous, but some of the most notable are input (how does the player interact with the world? Is it organic? Is the user interface descriptive enough to be useful, but not so intrusive that it hampers the experience?), limitation of playspace (can you make your player feel free whilst limiting their overall movement to within a certain radius?), and technical limitations (VR games require a much higher refresh rate to be playable, meaning you need to be careful with your poly counts and normal maps!).
Much like the mobile market, the true superstars of VR do extremely well both critically and financially, but getting to that point is... virtual insanity.
LOL JK
4. Technically-Demanding Cross-Platform Games
I've specified "technically-demanding" here for an additional garnish of challenge on an already savoury stew of difficult-difficult stroganoff.
Having players of the SAME platform interact with each other successfully and accurately is plenty work for your programmers already, but having them interact with different platforms simultaneously without any kind of hiccups? Yikes.
If you've ever tried to cook an "oven-only" ready-meal in the microwave, or a cup-a-soup in the air-fryer, you'll know that mixing formats often ends up... sloppy. And explodey.
The reason I included "technically-demanding" is because this added layer of nuisance is frequently the hurdle that knocks an upstart indie jumper out of the race. Your game might look fantastic on Xbox Series X, but you're not going to get the same kind of fidelity on the Nintendo Switch.
That's unsurprising to anybody, but what happens when you need to get identical performance in online matches between the two ever-so-different machines? Do you insist on parity with the lowest-spec system and make the experience lesser for those with beefy machines, or do you take a few performance inconsistencies on the chin and maybe face the wrath of Reddit?
Now if you'll excuse me, my kettle-cooked cheese toastie is ready. Mm. Moist.
3. Physics-Based Online Games
A simplified explanation of how some online games function is: the server will expect you to do a thing, you'll do the thing, and it'll go "ding-ding-ding! Correct!" - it'll move you server-side (often ahead of your action), check your version of the game to make sure they're the same/it predicted correctly, then it'll confirm you're there on the server.
If you've ever been running along and zipped back about ten metres, it's because that "prediction" was incorrect; when you and the server desync, it moves you back to the last known location.
Not all games work this way, but this PredictoMax 3000 approach is excellent because it's so rapid, especially when characters and behaviours are predictable enough for it to work seamlessly. Characters only have a finite amount of movement options, walls are either being touched or not, and so forth. But what happens when you add the chaos... of physics?
Well, a total headache for your team's programmers.
The trouble with mixing physics with online gaming is that physics-based interactions are largely unpredictable until they actually happen. If you've ever been playing an online game with physics objects and shouted "whoa, did you see that?! That rock just missed my head!", and your pal replies "it was nowhere near you on my screen..." - then either the physics estimation by the server was different for both people, or the programmers were clever enough to make the physics objects unique to each player.
In any case, online games with physics are so difficult... because they're so unpredictable.
2. Games Requiring Intricate AI Systems/Enemies
Artificial intelligence has come on leaps and bounds (especially when it comes to AI frogs and handcuffs! Ho ho!) in the last couple of years, but it's worth remembering that AI routines still need to be mapped by a fallible, sweaty meatbag first. And debatably, the trickiest part of good AI is making it dumb enough to be fun to play against.
You see, when a programmer builds an AI enemy, they make it real smart. The problem with that is, it's better than you, in every way. It has a better K/D ratio. It's faster. It can eat more raw ham than you. Probably.
The real illusion is that these incredibly complex characters with circumstantial behaviours for every possibility have to be dumbed down to such a degree that you stand a chance against them.
So what this effectively means is, AI programmers have to create a turbo-genius which has the ability to crush your puny human cerebrum with a digi-blink, but then to handcuff it, blindfold it and take away its raw ham-eating dentures... just so you can pretend you're the best in the world at this game.
Look at what they have to do for you... just so you can mimic a FRACTION of their power.
1. Massively Multiplayer Online Role Playing Game
MMORPGs, without a doubt, are the hardest game genre to build, for one very significant reason - the sheer volume of resources required to build them. As a common sense rule, +1 game content = +10 more development required.
Fledgling devs often think big when imagining their own magnum opus, excitedly telling friends about how their MMORPG is going to have twenty character classes, each with three fighting styles, and there'll be PVP, and there'll be a peer-to-peer marketplace, and...
Ugh.
Just the sheer AMOUNT of content and systems in the average MMORPG are enough to fill two or even three full titles from most other genres, and even when you've finished creating your game, there's the question of upkeep, which is a gargantuan task.
In some ways the MMORPG market is one of immense optimism; MMOs have one of the highest failure/collapse rates of any online game genres. To embark on the colossal quest of building one, you need to have the kind of conviction you'd normally only find in a plucky JRPG protagonist, and you will absolutely require the power of friendship to overcome the challenge of bringing one to release.