Jespel Juul and Marleigh Norton presented a paper at the recent Foundations of Digital Games conference in which they questioned the popular wisdom that games should have “easy to use interfaces, but … provide difficult gameplay challenges”. To quote from the abstract:
this paper argues that it is rare to find a clear-cut border between interface and gameplay and that the fluidity of this border characterizes games in general. While this border is unclear, we also analyze a number of games where the challenge is unambiguously located in the interface, thereby demonstrating that “easy interface and challenging gameplay” is neither universal nor a requirement for game quality. Finally, the paper argues, the lack of a clear distinction between easy interface and challenging gameplay is due to the fact that games are fundamentally designed not to accomplish something through an activity, but to provide an activity that is pleasurable in itself.
I argue that they are wrong and the reason for their error is that they are regarding games from the point of view of the player, not of the designer. I will be so bold as to claim that it is of critical importance that the designer makes a very clear distinction between the gameplay and the interface and tries to always abide be the “easy to use, challenging to play” maxim.
An important thing when designing a game is to decide what is the experience you want to provide. Often this is some kind of challenge, physical, mental or social. A good design is coherent, fixing on a particular kind of challenge — say physical dexterity — and applying it consistently throughout the game. This way the player knows what kind of play to expect and can quickly establish whether or not to commit time to the game.
A poorly designed game is careless about the kinds of challenges it provides and so is disloyal to its players. It begins as a fast-paced game of physical dexterity and then later throws up a riddle-solving section that blocks all further progress. Players who committed their time to a reflex-based game are now confronted with a challenge they never expected and may not enjoy. This kind of unreflective mismatching is a great way to lose your players.
Having decided on a particular challenge, then the gameplay/interface divide is clear. The gameplay is that which provides your desired experience, the interface is the realisation of that experience on a particular set of input and output hardware. The interface is designed, along standard UI principles, to get as little in the way of the desired experience as possible.
To claim that in some games, such as Toribash, the “challenge is in the interface” is to be unneccessarily fuzzy-minded. If it is part of the intended challenge, it is not the interface it is the game. As a player it may not be clear which parts of the game were intended or accidental, but the designer should know better.
The gameplay of Toribash, as I read it, is in the strategic planning of joint movements in the anticipation of how the physics will play out and the opponent will react. The interface to this experience is the process of clicking on joints to select how they are going to move. Ans this interface is actually relatively poor. The targets are often hard to access on the 3D model (especially using the clunky zoom/pan/rotate controls) and selecting an action by multi-clicking to cycle through a list of options is tedious and error-prone. While I did not design the game, I doubt that this frustration is the experience the designer was trying to convey.
A better UI to the same game might be to have sidebar showing 2D front and back images of a standing fighter. Muscles could be clear, easy-to-select targets, colour-coded to indicate what they are doing with a drop-down menu or a set of key-codes to select a particular mode for each. Macro keys for selecting certain muscle/action combinations would take the drudgery out of constructing common manoevres through dozens of clicks and camera rotations.
Now maybe I have missed the point and the rapid, precise clicking is where the fun of Toribash lies, but my argument remains the same. Just because the gameplay involves what are traditionally considered UI elements does not mean that the two are the same.
Confusing interface and gameplay only leads to carelessness about whether your interface is providing or hampering the experience you desire. This carelessness can only result in sloppy interfaces that interfere with and frustrate play. Only a poor designer writes this off as “part of the challenge”. A good designer fixes it.