Muddy waters - Usability and design issues

Ford (Flat, Shallow Water)Ford/Flat

Grey Shallow Water/ (Shallow Water)Grey Shallow Water

Grey Deep Water/ (Deep Water)Grey Deep Water

Starting with Wesnoth development series (1.9.x) new graphics and animations for terrain and unit types were introduced. These new graphics enrich the gaming experience, since they render the board smoother to the sight.

However, some users highlighted some problems with these new terrain types, in particular for water based terrains. It seems rather hard to distinguish at first sight the type of terrain for certain 'waters'.

Is it a problem? Why?

On playtesting - Quote from the field

 

"Since I joined the developers I don't play much anymore. Testing the stuff I am responsibly for is just enough and I don't even enjoy it anymore. Playtesting is hard work." (Wesnoth developer, Interview 12/05/2011)

Examples of total conversions and 'total add-ons'

As I mentioned in this post, WML is often used by Wesnoth users to create their own content and to enrich the game with possibilities that bend (or blur) its original design. While browsing the forum's "Experimental Corner", I discovered that the idea of doing a total conversion for Wesnoth (and bring it to completely new settings) was not as new as I thought, when first reading the title of that thread. Indeed, total conversion projects for Wesnoth have been attempted in the past. Two notable examples are Spacenoth and The World of Orbivm. [caption align=right]

Wesnoth Markup Language as mediating artefact

A key topic in my interviews was mediation between design, development and use of the video game. That is: how design decisions are negotiated in relation to end-users' needs or, put it differently: how gaming practices and design/development decisions influence each other. Since I conducted most of the interviewees with contributing users, the answers reflect their point of view, rather than non-contributing users' one.

The departing point was this FAQ, which I noticed some weeks ago:

Why doesn't Wesnoth have my favourite feature?

Because we are building this game for ourselves, to suit our own preferences. We're not building the game for you, in large part because this is our hobby, not our job; whether you like it or not is immaterial to us. You may wonder, then, what the point is of soliciting ideas, as we do on the forum. We, the developers, have certainly come up with many good ideas on our own, but our players often do as well, and generally ones we don't think of ourselves. If a player comes up with an idea we like, we might implement it. Not because they asked for it, but because of its own merits as an addition to our game. [...]

Relationships and bonding in collaborative projects

This is just a general consideration coming from my first few interviews with Wesnoth devs and users, and it relates to a (probably wrong) assumption I (and others within academia) made. I always gave for granted that the people gathering around a given FOSS project such as Wesnoth, could be considered as a sort of community. However, after these interviews I start questioning this perspective.

Even if I take the somewhat general Rheingold's definiton of virtual communities:

social aggregations that emerge from the Internet when enough people carry on public discussions long enough and with sufficient human feeling to form webs of personal relationships in cyberspace.

the people answering my questions, gave me the impression that the "web of personal relationship" is probably much more loose than one might expect from this kind of definition.

Syndicate content