Arcs in Strategy Games

It is common to hear players talk about “tactics” and “strategy” in games. In this case, the colloquial understanding of these terms happens to be pretty useful, in that it maps well to something that actually goes on in playing strategy games. With that said, it’s worth taking a moment to clarify these terms:

Tactics” usually refers to “short-term decision-making”. Questions like “should I move this character two steps forward, or three steps forward” are questions of tactics. Tactics are micro-level decisions in strategy game play.

Strategy” usually refers to “longer-term decision-making”. Questions like “should I be aggressive early, or be defensive now and attack later on” are longer-scale choices about a game that players make. Strategies are macro-level decisions in strategy game play.

In both cases, we are talking about a grouping of gamestate information over time and how it changes. I refer to this grouping as an “arc”. Continue reading “Arcs in Strategy Games”

Game Design Digest, from the Dinofarm Forums

A few months ago, I posted a thread on /r/gamedesign about how we should make 2017 a year with more game design blogging. Since then, a few Dinofarm Forums members have talked about starting up a game design writing career (or re-starting one). The last few days have had a huge uptick in interesting, quality articles on game design. I may be biased, because these are people who hover near my circles, but I find these to be some of the best articles on game design I’ve read in many years. (Here’s the good news: if you’re a reader of my work, you may also have the same biases!)

Here are some of the users over at the Dinofarm Forums (and the Discord!) who have been writing stuff recently. Follow these blogs!

Evizaer – Some of my long-term fans might remember Evizaer from an appearance he made on my old podcast years ago. He recently has started up a new blog and has a new article up about analogy (sort of like theme) that I think is quite good!

Elliot George – A newcomer to the Dinofarm community, Elliot produced this great piece, which is easily one of the most thoughtful pieces on strategy game design I’ve read in years.

Hopenager – Has started a completely brand new blog on game design. I have a few issues with the opening setup, but based on the last paragraph, I’m really excited to see where it goes.

Brett Lowey – This one doesn’t entirely count, because Brett is an established game developer, but I just really appreciated that he wrote this great piece on his “game design commandments”. I think this is something every game designer should do. (Also: his commandments are great!)

Disquisitor Sam – Started his new blog last year (I think) but it has recently gotten a facelift. His article on Auro I particularly recommend!

 

Already, 2017 is looking like it might be better than the last three years of game design writing combined. I should mention that a lot of these have happened in the last 36 hours. There are also rumblings on the forum of other people who are also starting blogs. Like I said in that reddit thread: if you’ve been thinking about writing about game design, do it! Ping me anywhere you can, and I’ll share your work. I want to do whatever I can to help foster a community of thought on game design.

Push the Lane!

[IMG]

I’ve been working on this game now for over a year. It started as an abstract strategy game that was kind of like bejeweled or something, and then I decided to take it in a D&D Boxing direction with the Battle Blast theme.

Now the design is maturing in a lot of ways. One small example: instead of your attacks dealing random amounts of damage, minions have a random amount of health. So it’s basically just one of the ways to convert the output randomness to input randomness.

Another neat thing: you have stats, like attack damage and items that change that, and the enemies have health and armor and all of that, but health is visually represented as pips underneath a minion that simply “how many of your attacks it WILL take to take down this minion”.

Here’s a rundown.

Theme
It’s an American Gladiators or Nickelodeon’s Guts! type of TV game show. A sport – played single player, against basically an advanced strategic obstacle course, fighting robotic minions.

Continue reading “Push the Lane!”

Clockwork Criteria: 6 Guidelines for Ideal Strategy Game Design

What are the criteria that make something a good “Clockwork Game”?

The Clockwork Game Design model is something I have been working on for the last five years or so. It is specifically an effort to figure out how to make the most elegant and effective strategy games possible. There are certainly practical reasons why you might not want a specific game to be a Clockwork game. But to the extent that you want your strategy game to be elegant, you should adopt as many of these principles as possible.

Above: my book

Below is a list of criteria that strategy games should strive for. I am sorting them by how controversial they are. In other words, I am putting the stuff people pretty much agree upon towards the bottom.

These are not ordered by priority. I am making no statements about which of these is more or less important; just that they are all something to strive for. Continue reading “Clockwork Criteria: 6 Guidelines for Ideal Strategy Game Design”

Riot is thinking about input/output randomness in League of Legends

For the past five years or so, I’ve been talking about the input/output randomness concepts, and why they’re so important for game design. While I wasn’t the one who coined the terms—that honor goes to the great fellows at the Ludology Podcast—some Googling around shows that no one has talked about the concepts, or developed them, nearly as much as I have.

In short, talking about randomness, especially in these terms, is kind of my thing.

Here’s a quick list of some of the more notable times that I spoke in depth about this subject:

Beyond that, you can (and should) read my books, listen to my podcast and watch the complete 3 Minute Game Design on YouTube.

Between that, and the fact that I recently praised League of Legends and its developer, Riot, for some of the radical things they’ve been doing to their game, you can imagine how pleased I was to see that a Riot designer, Greg Street, made a video talking about input and output randomness in League.

I want to do three things with this article. First, I want to signal to the Riot devs that I would be more than happy to help them out with this project of making the game more input-randomnessy and less output-randomnessy. Let’s chat!

Second, I will talk about the current state of randomness in the game. And finally, I will talk about a few of my recommendations going forward.

The Gist

You should check the links above for more detail, but the very short and rough explanation of input/output randomness is that they are describing the distance between new random information and the user’s ability to react.

Input randomness is stuff like the Tetris “Next” box, or a randomized map—stuff where the user has time to see what the random information is and make decisions based on it. Fog of war is also often used as a mechanism for input randomness: you see stuff usually a turn or two before it can threaten you.

Output randomness is stuff like “roll to hit” in RPGs or games like X-Com. You decide to attack a thing, and then there is random information which comes into the game and determines whether that hit connects or not. In this case, you have zero time to “respond” to the new random information. The course of the game has now been altered by pure randomness, unfiltered by your decision-making.

A quick note is that actually, input and output randomness exist on a spectrum. Randomness which is really close to the user but still technically is input randomness(imagine 1-tile-radius fog of war) may actually be so close as to function similar to output randomness. For more on this, read my article on the Information Horizon.

One more note: as Mr. Street said in the video, output randomness is bad for strategy games. (Actually, he wasn’t that strong with the language, but that is definitely my view.) You also don’t want zero randomness in games. What you want is a carefully placed information horizon.

Randomness in League

There are a number of sources of randomness in League already, but what’s exciting is what they’ve been adding, so let’s talk about that first.

One of the big ones, that they’re talking about in the video, is the new Dragons (or I guess they’re calling them Drakes? I’m going to call them dragons) system. Every game, there is a random elemental dragon. Killing each dragon gives your team a different kind of buff—something like, Air dragons make you move faster, fire dragons make you deal more damage, Earth make you destroy towers faster, and so on. After one of these dragons is killed, a new random one will spawn.

But here’s the cool thing, and when I saw it, I was impressed, because it’s exactly what you should do. The dragon takes awhile to respawn. But on the dragon’s death, the next dragon is selected and a big bright symbol is painted on the dragon’s lair wall for everyone to see. This is a great example of input randomness. Both teams know exactly what random dragon is going to spawn there, and decisions can be made around that.

This system is a really great start. There should be a lot more of this on the League of Legends map (which I guess they call “Summoner’s Rift”? I’m going to call it “the League of Legends map”).

My Suggestions

Category #1: Increasing input randomness. I believe that by making the League of Legends map more dynamic and more different each game, Riot can worry less about perpetually adding content to the system and the sort of “patching just for the sake of keeping things fresh” idea that they arguably do sometimes.

  1. Randomized geometry. Why is the map geometry—the pattern of the walls and everything—the same exact every match? Is this geometry sacred? Remove this brush, put a pillar here, change the shape of this wall. You can definitely design the parameters in such a way that it’s always fair for every character, yet slightly different every game. If you’re really worried about it causing balance problems, maybe have it change randomly at 10 minutes and at 20 minutes, or something.
  2. Randomize all jungle monsters. Having a fixed jungle means having a fixed jungle route. Instead why not have there be a few more jungle monsters, but what they are and where they are is randomized somewhat. That way you can have a more dynamic and less “memorized Starcraft build-order” automatic pathing to the jungling. Make it mirrored, so it’s fair.
  3. Random plants. I love the new “plants” system, and maybe it’s just the beginning. But why not randomize the positions and the types for these plants? Make it mirrored, so it’s fair.
  4. Push the dragons further. Right now the buffs are cool, but maybe instead of just the four elements, it’s four different kinds of monsters as well. So you could have an Earth Wizard who does lots of magic damage, or a Fire Ogre who has shitloads of health. Maybe Ogres, when killed, change the terrain somewhere else or spawn plants somewhere.
  5. Random (mirrored) cannon minions, and more? I like the idea of there being some more variance in the minion-stream itself. What if randomly, every 5-7 waves or so, a super minion spawned on one of each team’s lanes (probably, it can’t be the same lane). There could be a little map alert telling both teams about this. I spent like two minutes thinking of this idea, I don’t know—but the point is, I do think there’s a lot more that could be done with minions than is being done here.

Category #2: Removals of existing output randomness. These aren’t quite as important in my view, and they’re also less likely to be taken up by Riot for a number of reasons. But ideally, I’d love these to be changed.

  1. Remove Random Critical Hits. This is totally unnecessary for this game. It’s totally a vestigial D&D thing and all it does is unnecessarily loosen up a system which already is very loose. I’m actually surprised that high level players don’t complain about this, because a lucky crit at the wrong time can completely change the course of a match.
  2. Reduce execution across the board. This one is hard, and I don’t expect Riot to act on it for that reason. But, in an ideal world, we should be making the game be less about crazy reaction speed in team fights, and more about strategy. Removing skillshots and having them be target-based is one suggestion here. Getting rid of “burst” (massive amounts of damage in a tiny window of time) as a concept would be a much wider scope change that would really benefit the game. That would mean questioning the roles of burst-mages and assassins, which is a huge job, but personally I think it would be worth it. Because, as I’ve written about before, execution is a form of randomness, and this becomes more and more the case the faster players are asked to execute.

(On a slightly related topic, here are some more League patch notes that I’d love to see.)

Anyway, those ideas are mostly off-the-cuff (but not getting rid of random crits. That seriously needs to go), but the point is just to demonstrate some ways that Riot’s designers—and designers in general—can use the input/output randomness theory in practice to create a better experience. Using input randomness in this way, you can get the “variety” that is so sought after using extremely costly (both in terms of production costs and accessibility costs) asymmetry content, while also providing players with a fair, balanced competitive experience.

I’m really glad to see someone as high profile using these terms. If you know of anyone else talking about randomness in this way, please let me know in the comments!

 

If you enjoyed this article, please consider becoming my patron on Patreon.com.

Improving Go (Not Really)

My official position is that you can’t really “improve” Go. There might be something in there worth salvaging, but you can’t just tweak some rules and make Go better. That’s not because Go is so great, but because tweaking rules on an existing system like that tends to create vastly horrible results.
With that said, it might be an interesting intellectual exercise to sort of try to graft on the Clockwork Game Design concepts onto Go and see what you get.
Every day I throw down failed game design ideas. Today I thought I’d share one with you guys just to get a little game design conversation going. (With the election and everything, things have been a little slow on that front recently.)
Here’s as far as I got, just to get you guys started.
go2
Some basic ideas for it:
  • 13×13 board, as a starting place. Would scale up or down as necessary. Maybe the board shouldn’t even be square, not sure.
  • Fog of war. Basically my idea was that you get a vision range of 2, but this doesn’t actually make any sense in practice for a few reasons. One is that you shouldn’t be able to place pieces on the perimeter (random), let alone across the board in some random fogged spot. And the second is that at some point (possibly 10-12 moves in) you’re going to just see the whole board – bye bye, hidden information. There may be solutions to these problems, but I don’t know. (I’ll come back to this at the end.)
  • At least 1 piece down already, probably more like 3-4 in a random, non-mirrored configuration (this is to avoid guessing what the opponent is doing in the fog).
  • Grey pieces are down in a mirrored configuration. Grey pieces turn your color when you put a piece next to them. Or maybe they do something different?

A few thoughts I had as I was giving up on this:

– Maybe this could be single player somehow? Like having to do with the grey pieces? Probably not.

Back to the fog of war and the problems with it: funny thing about this is, it doesn’t really work, and one of the reasons it doesn’t work is the “I can just lay down pieces willy-nilly whereever I want with no restrictions” element of Go to begin with.

Anyway, like I said, I make these kinds of failed little concepts all the time and since things have been slow around these parts recently, I thought I’d share this one totally non-working, bad idea with you.

How would you apply the Clockwork Game Design design methodology to Go? Just to review, here are some of the demands:
– No memorized openings/closings
– Some source of hidden information
– Ideally, something that looks like a core mechanism
– The game should be no longer than it needs to be (Go’s pretty long)
I’d love to hear your thoughts.