Category: UX & Prototyping

First of all yes, I know the name “Adventure Island” is taken, but this is just a working title while I define all the game rules, objective and even the world itself, which is not even an island at this point.

But what you have here is the very first early prototype of the game I’m making for Stine in the UX & Prototyping course at ITU.

Almost entirely based on the paper prototype I already wrote about earlier this month, the objective of this early build is first and foremost, to get me acquainted with JavaScript in Unity. I had already worked with the Unity Engine before (see the games Mr. Optimistic, R.E.D. and The Hitchiker in the projects section of this site), but this was the first time I was doing the coding by myself, no other programmers involved. This meant learning quite a few things from scratch. I tried a visual scripting tool, but it didn’t help much without at least understanding a few of the basic things of JavaScript, since I was constantly hitting a roadblock when my 3rd person controller object wasn’t detecting the collisions with the other interactive elements of my scene. It took me quite a while to figure out what was going wrong (hey, I’m not a programmer, remember?) but eventually I got it right, so with a few tweaks here and there I managed to get a working framework which will later on let me expand this game world easily by reusing the current code.

So basically this prototype is still pretty much devoid of gameplay. Sure, you can talk to NPCs, they trigger events, and you can use the boat to cross the lake (even though right now it still looks as if the main character is WALKING on water). But later on I intend to add some minor combat element into the game as things get bigger and better. Not that I have much time left for making combat very interesting and innovative, so I will borrow many things from the good old Zelda playbook.

Yes, this game is being heavily inspired by the Legend of Zelda series. Considering that this is a project for a course in which we are meant to make a game for someone else, not ourselves, you could think that I’m playing foul here and using a game that I like as a model (because yes, I’m a HUGE Zelda fan). But if you’ve been reading my previous entries about what Stine likes in a game, you will definitely agree that a game based on exploration in the way that games like Zelda and Oblivion (should I start making references to Skyrim now that this new behemoth of a game is out?) do it.

But of course this game is neither Zelda or The Elder Scrolls. And neither is it World of Warcraft, as much as Stine would love to see it (mind you though, she is waiting for the game that will finally beat WoW so she can jump into it and lose herself in this new world).

But I’m taking cues from here and there. You have a relatively big, open world (Zelda and Skyrim check), with some areas closed until you have the right item/progress in-game that you find in chests (Zelda check), characters who give you quests that add to a log (Skyrim check) and in the future, I hope, simple combat based on sword and spells (Skyrim and Zelda put together for a check).

But my focus of attention is still on the exploration aspect of the game.

While still unfinished this world already has a forest, a lake, a volcano and a town, with some paths here and there so that the player doesn’t get lost, but it’s still pretty much a green land without much to do or discover.

What I did though was work on the camera: when the player is in a town or in an important area, the camera zooms closer to the character (which, by the way, is still an unfinished one, and needs to be changed into a girl, more on that in future posts). This way the player can pay attention to the tiny details of the areas. Say, for example, an inscription on a wall (something I know Stine will be very keen to look at and decipher what it means) or a window with someone looking through it. Also when the player talks to a character the camera zooms in even closer so as to emphasize the characters who are interacting with each other.

But when the player heads out into the open, the perspective changes. It doesn’t zoom out the camera. Instead I’m changing the field of view of the main camera. This makes the main character appear still big enough so that he is not lost amidst a sea of enemies or other things in the world (of course, once I start populating it with such elements), but allows the player to view what lies around her much better. This distorts the view in the corners a little bit, but I think it also gives a nice effect of the world being kind of round.

During the presentation of this early prototype in class, someone made a good point by asking that, if Stine likes exploration, why would I offer her a world that is not entirely open right from the start, but instead restricted until she gets the right items. My reply to this is that, based on the interview I had with Stine over a month ago, Stine likes the feeling of knowing there is a place she cannot reach yet, and she will keep trying again and again every time she has a new ability or item to see if the area has already opened up to her.

But in any case this is still a very early prototype, as this last picture summarizes.

I hope to really improve this in the following weeks to transform it into something that Stine will really like. And, as usual, I will post my progress here as the days move on.

What you see here is the very first paper prototype of my game for Stine, the girl I am making a video game prototype for in my UX & Prototyping course. It might not seem like much at first, just a simple (badly) hand-drawn map on a hexagonal grid with a small ball of aluminum near the middle of the map (it’s kind of hard to see in the picture, but it is there).

So… what is the point of this map? Does it actually serve a purpose? Is it some kind of D&D game?

Not at all! This, along with some blue paper with a hole in it and a script that I have written get together to make a paper prototype that has actually fulfilled its purpose very well. Either that, or Stine lied to me when she said she liked it.

You see, this is what Stine actually sees when she plays my paper prototype. Just a very small area of a map, with the rest all covered with the blue paper.

I gave her some very simple instructions: her character (at this point still undefined) has to find her way through the map to reach a great wizard who has locked himself up in the top of a tower. What reason she has for finding the wizard I left it up for her own imagination.

The problem is that the door to the tower is locked shut and there is absolutely no way that she can break it or climb the tower. So she’s going to have to find her way through by exploring the map, talking to villagers and perhaps acquiring some equipment. After that, I told her nothing else and I just read to her the parts of the script that I had prepared for whenever she reached specific points of the map, like the villages, the lonely hut on the North side or the spot marked with a red “X”.

Why make a paper prototype like this? Because, as mentioned in previous posts about this project, Stine LOVES adventuring and exploring in games. So my intent here is to have her move around a game world of my own creation and see how she reacts, how she moves and how she thinks (aloud) while playing it. This will help me shape up the first digital prototype of the game and represents an important step forward into creating a game entirely from the feedback of another person.

And how did she do while playing the paper prototype? That’s a very interesting thing: it was totally unexpected for me. She REALLY believed herself in this game world and feared for the life of her character. For example, one of the villagers told her that a thief hides himself in a hut to the North. She needed the treasure that the thief had taken, but when she saw that the hut had smoke coming out from the chimney she decided it was best not to break in because she was afraid the thief might be in. Since she didn’t know if she could really die in the game she was trying to be very careful about it, and refused to enter the place, instead going out to explore the world some more and maybe coming back later.

There were also some funny moments. She found a lone tree for example, one that I had drawn there merely for decoration and to avoid the map being too empty. But she was disappointed that it was only decorative and expected something else out of it. So she… hugged the tree. Yes, that’s right. She felt like she needed to interact with the tree, so she hugged it. And not just once, she did it more times when she came across it, in case that could somehow affect the outcome of the story.

More interesting for me as pure feedback was that she re-visited some areas that she knew she had already completed to see if things had changed in a way. For example, she went back into the forest where she had already opened a treasure chest because there might be something new in it.

Another important fact was that she was expecting small details that could hint her about the game world itself, like footprints of some kind of animal (in fact she was disappointed that there were only human footprints around).

The final, very important piece of feedback I got was about the size of the map. Since the view she had was at all times very limited, this gave her a feeling of the world being much bigger than it actually was. This is something that I intend to apply in a very easy way into the digital prototype, which I will discuss later on, even though I have already started to code it (yes, me, someone who doesn’t know a thing about programming, is coding this game by himself…)

That’s it for now. The next step is to create an early digital prototype based on this paper one and making good use of the feedback I got from this. And I already have some neat ideas.