“Good news everyone!”

We have reached the point where we can start having some players test and try break things with the current pre-alpha-thingy-candidate version of the game. We are looking for just a couple of testers who can cope with the fact that they will get early spoilers and experience a not entirely finished game narrative and interface. On the other hand you will greatly help us stabilize things, spot a few more bugs and make final improvements!

Take into account that you will have to use an issue tracker to report us problems (ie, using a website with a form to check for existing known problems and report new ones) and that we will ask you some questions after you played.

Use the contact form in this blog to get in touch with us :)

This residency was very different – naturally at this stage focused on the software, we started with an initial list of showstopping things to fix, and then used online methods of organisation via mantis and the wiki.

We also presented the project for the first time, at NIMk’s space invaders event, and we had some super volunteers from Eindhoven Technical University Game Experience Lab to test the game (which Aymeric describes in more detail).

One of the things that I was pleased to get a chance to tackle was how to cope with the basics of online multiplayer games:

• How do we cope with having too many players?
• What do we do with players who haven’t played for a long time?
• How does this shared world repair itself so new players don’t find a world trashed by the earlier players?

The most worrying problem for me was the (perhaps rather hopeful) issue of being swamped by lots of people. This is an interface and resources problem, there has to be a fixed limit somewhere, a point where we have to turn people away. How do we do that?

There are two limits in this game:

A = The number of people playing at one time (interface, game world, and perhaps to a lesser extent CPU limited).
B = The number of people playing in total, with characters and associated data stored in the game (server memory limited).

B is a much higher number than A, so we can hide inactive players in order to accommodate a far higher number of people playing in total than we do simultaneously.

In other cases we are making solutions part of the game itself. For example, “cleaner” bots wander the world removing players who haven’t moved for a week – and at the same time remove items that are left over as a side effect of people playing the game.

Players can move bots around the world along with anything else, so they are given the ability to navigate their way home automatically. In some cases this results in some amusing emergent behaviour.

If left for long enough, the game will clean up all the players and return it to it’s starting point. If lots of people are playing and messing up the game too much, we just create more cleaners! At least, that’s the theory.

Thanks to Maarten Witteveen @ BALTAN for the photography.

Today was a crucial and quite scary step for the project: playtesting.

Indeed, so far we’ve been happily working and testing the game on our own. We did that not because it was a secret process – after all anyone can check out and run the source code since day one – but because it would not have made much sense to get feedback on something that was actively developed, thus changing directions very often.

The downside of not sharing the progress, is that eventually you end up being so much immersed in your creative process and imaginary world – in that case, Pluto – that you have no way to remain objective or even properly test the game yourself.

For example, after making one of the quests hundreds of time, to look for bugs or test some new feature, the user interface and the narrative disappear completely from your experience. It becomes an automated procedure and certainly not a playful moment.

On top of that, each of us started to be obsessed about particular features or details that are not necessarily useful or important for the project. But it is important to be able to “kill your darlings” before they slow down the development of the project or get you entirely side tracked.

All of this make the playtesting a necessary, yet scary, mandatory process to move on and remind you what were the reasons that pushed you to make this game.

Last week we reached the point where most of the essential game mechanics and interface features were in place, in an unstable and clumsy way of course, but at least we knew that we were heading towards a stage where the game was playable and more or less coherent. This is why today at Baltan Laboratories we hosted a play testing session of NOP with game design students and researchers from TU Eindhoven.

For such an occasion, it’s really important to leave your ego behind and be ready to face, most of the time, painfully honest comments. In that regard we had a fair amount of these and it was a really good thing. A bit painful at times though… ahem.

What we did was to let the testers play the game for 15 minutes, and ask them afterward a few questions. More specifically:

1. interface (readability, flow of the game (action-response sequences), user input, commands)

2. narrative (story, non-player characters, multi-player aspect, game world, message communicated)

3. playability (difficulties encountered and suggestions to improve)

4. fun (did you enjoy the game? why?)

5. link to entire project (Is the game clearly linked to the research aspect of the entire project?)

The response we got was very good and helpful. I will not give much details, but overall most of the advices and critic we got were known issues or things we noticed were wrong but for which we were not entirely sure how to deal with them. Regarding the game itself, some players managed to progress very fast, others struggled and it was interesting in each case to know why it worked or why it did not.

Of course it can be frustrating to get feedback on things that you already know are broken because of lack of time or just because it is not high priority at the moment. Never the less it is important to get over this frustration and let the players tell us whatever come to their mind as it is an invaluable source of information, specially if your testers are themselves working in the field of game design. We greatly appreciate the time they took to visit us and give feedback on the project.

At the end of the session we had a long list of things to fix, things to change or improve and things to add or remove. Very long list. The good news is that most of these should not be too difficult to implement and hopefully can be done, for most of them, before the end of the week (says the narrator in a hopeful way).

Once this is done, we will be ready to invite remote beta testers – from the internets – and it will be the second major step to take in order to make sure we’re on track.

Monday October 11, the first day at BALTAN Laboratories in Eindhoven! We walked to the SWA building, through Phillips Complex S, and at the 8th floor gasped at the enormous space of the lab. After a grand tour by director Angela Plohman, we set up and started to write down the master plan for this week. Lots of decisions to make, especially after the playtests we’ve held. The feedback we received made sure we zoomed in on the parts that needed the most attention first.

First task was to make the interface more user friendly. Most playtesters were too busy trying to figure out what to type and how to type it, instead of discovering the game world. We decided to simplify the vocabulary, write more elaborate help texts in case of an error, and write a general “help” that gives an overview of the vocabulary, what each word does, tips to speed up navigation through the world and all this with clear examples.

Second big change is the layout of the page. In the old layout the input form was at the bottom, with the story being written above it and on the right a feed of messages from the game. The new layout is meant to look and function more like Facebook and Twitter, with the input form at the top, the story below, on the left a feed of messages directed at you, and on the right a feed of general messages. To match the social networks more closely, the story is now in first person perspective, and everything you type is a message. This way you can follow what other players are doing, get curious about how they found that pony or managed to enter a fishtank, all the while enjoying the fine feeling of transparency.

We also needed to think of ways to be more “in your face” with our narrative. Hints and tips were missed too easily. We will change the texts and use the Facebook data we have at our disposal in more elaborate ways. And hints a player needs to progress will be more obvious. We need to find a balance here.

Well, that provided us with enough work for two days. Wednesday we’ll do another playtest with game design students and researchers from TU Eindhoven. We hope to be ready for another round of feedback by then, so we can go through a second iteration of improvements on Thursday and Friday.

Oh and tonight at 19.30 we present Naked on Pluto at NIMk, during the Space Invaders event there!