Constraints are a constant in design, and while they can sound like a bad thing, I'd suggest that I think they're not just inevitable, but beneficial to a strong, focused game design.
We don't talk about this a lot, so let's dive in a bit.
We don't talk about this a lot, so let's dive in a bit.
To clarify, constraints are factors that put pressure, requirements or challenges on the design that aren't just the design itself.
Each game has its own, unique constraints. While we can't prepare for everything until we hit it, let's categorize a few places they come from:
Each game has its own, unique constraints. While we can't prepare for everything until we hit it, let's categorize a few places they come from:
* Technical.
A few examples would be the memory budget, how many characters can be "active" at once, database space for inventory items, rig bone counts, or AI behaviors.
(AI is generally really expensive on performance).
A few examples would be the memory budget, how many characters can be "active" at once, database space for inventory items, rig bone counts, or AI behaviors.
(AI is generally really expensive on performance).
* Art and style
This is less about what you can't do, and more about not overly-constraining artists. Where are the opportunities to show off cool stuff? Let the style of the world be present for the player?
(I recognize the irony having worked on Valorant 😅)
This is less about what you can't do, and more about not overly-constraining artists. Where are the opportunities to show off cool stuff? Let the style of the world be present for the player?
(I recognize the irony having worked on Valorant 😅)
* Tone and world
Regardless of the tone, consistency is key - and a lot of things you might want to do might warp the tone and feel of the game, even if the gameplay and mood would be good in a vacuum.
Regardless of the tone, consistency is key - and a lot of things you might want to do might warp the tone and feel of the game, even if the gameplay and mood would be good in a vacuum.
Your job, as the designer, is not just to understand and work with constraints, it's to ensure your design has them *integrated* in it!
AI is expensive? Your design might want to find non-AI content to challenge players more.
AI is expensive? Your design might want to find non-AI content to challenge players more.
Tone is cheery but we'd like a climactic moment? A boss battle that elicits horror might be too far, but irony or poetic justice might be something that's close enough.
This is also important that these constraints aren't all visible at the start;
This is also important that these constraints aren't all visible at the start;
We learn about what not to do, often, by attempting to do it. The failure itself or conversation will reveal and expose the constraints.
You might have already designed without that in mind! But, it's your job to do your best to honor it - work with it - integrate it.
You might have already designed without that in mind! But, it's your job to do your best to honor it - work with it - integrate it.
Sometimes, you can work "around" these challenges with the team - that's part of the process! - but a lot of times, these constraints will force a helpful focus and discipline.
One that I think benefits design a great deal.
One that I think benefits design a great deal.
These constraints often help make some choices about focus for you; leveraging that as a blessing is smart.
But I think constraints are just a forced version of something that it's important to take the time to do even without them: *focused, disciplined design*
But I think constraints are just a forced version of something that it's important to take the time to do even without them: *focused, disciplined design*
We're in a world of unprecedented capability with games -- huge worlds, massive teams, incredible rendering capability, powerful player machines.
But this capability unshackles the designer from a required focus. Focus makes better games...every time.
But this capability unshackles the designer from a required focus. Focus makes better games...every time.
Games that do a few things well, and offer a clear experience, are going to succeed - both at drawing in the right players, turning the wrong ones (IE people who don't want this thing!) away, and delivering on it well.
What if we don't?
What if we don't?
We're likely to end up with an unmanaged mess; something that fails to do anything well because the design scope is out of whack.
Kitchen Sink design is almost always a mistake. More is not better - in fact, I think we have some high profile examples of just that.
Kitchen Sink design is almost always a mistake. More is not better - in fact, I think we have some high profile examples of just that.
Cyberpunk, Anthem and Battleborn (just to name a few) are games, like every game, made by a talented team of developers, with love and care, and a high capability of craftsmanship (even despite the burnout)
These teams know how to produce phenomenal games.
These teams know how to produce phenomenal games.
But that's why so many high profile flops as of late are the result of unmanaged largess and a *lack of constraints*.
These games had the talent, but not the focus.
This is something to pin on the leadership - always. Their job is constraints and focus.
These games had the talent, but not the focus.
This is something to pin on the leadership - always. Their job is constraints and focus.
While these are big examples, let's not see it only as a large problem;
Content and smaller components of the game need to be focused and consistent, too.
It's 1/1000000 to get something like HL2's Ravenholme out of disparate content, usually you get a mess
Content and smaller components of the game need to be focused and consistent, too.
It's 1/1000000 to get something like HL2's Ravenholme out of disparate content, usually you get a mess
How can you watch for this in your own design?
Well, I invoke the Goldblum Theorum;
Well, I invoke the Goldblum Theorum;
Start here always. "Can we?" is secondary to "why do we want to?"
Once you determine why, then ask how
This will generally make you a giant pain in the ass. Part of your job is being that pain in the ass, sadly. It's one of the myriad of reasons being good to folks is important
Once you determine why, then ask how
This will generally make you a giant pain in the ass. Part of your job is being that pain in the ass, sadly. It's one of the myriad of reasons being good to folks is important
Most games, though, will have constraints. Start there! Remember your job is to make the whole game better, not just have good design in a patchwork game.
Negotiate them, discuss them, but once you've done that, embrace them. Don't buck them.
Start compromising now.
Negotiate them, discuss them, but once you've done that, embrace them. Don't buck them.
Start compromising now.
And like most design skills, being a better person (compromise, negotiation, looking for win-wins) will make you a better designer. Start thinking about the constraints and how to integrate them in daily life - it'll be easier to transfer when you do.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
