Raspberry Pi – Minecraft

I don’t know about you, but for my Year 5s, Minecraft is a way of life – for the past 3 or 4 years I’ve seen it grow and grow in popularity to the extent that it’s no longer something cool to talk about, it is beyond cool, it’s just assumed that everyone knows what it is and plays it. So, when I first bought my Raspberry Pis, I remember enthusiastically telling the children that “you can use Minecraft on it”, which was greeted by some mumbling responses and one child declaring that it was too slow on the Pi.

When I went to Picademy I learnt the significance of Minecraft on the Pi – it’s not to play Minecraft, which can be done on any laptop, desktop, Xbox or even on Android & IOS devices, it’s to use lines of code to hack Minecraft and change the rules of the game.

The Minecraft section of our course was run by Craig Richardson, a former teacher with a passion for both Minecraft and the Raspberry Pi who is employed by the Raspberry Pi Foundation to pass on that enthusiasm to other teachers and children. He has very kindly shared his resources here and he even explains how to install Minecraft Pi Edition on your Raspberry Pi.

So, for those of you who don’t know, Minecraft is a simple, block based game where people can build, using blocks, houses and castles and boats and whatever their imagination requires. You can set up the game to be very simple i.e. resources are readily available, there are no bad guys etc or you can play so that you need to collect resources in order to make your buildings sustainable etc. It has never appealed to me in the slightest, but I really enjoyed using Craig’s hacks to explore the game and would consider looking at it again. One of the first things we were told when loading the Pi version of Minecraft is that the current version doesn’t work very well in full screen so don’t try to make your window full screen.

The first thing Craig asked us to do was to build a house. We discovered how to select different coloured blocks and built houses of varying quality (mine ended up being bright pink with a glass roof – it was hideous!). We also found out that to move our character (called Steve), we used the WASD keys, then the mouse clicks to play and select blocks. Once we’d built our houses, we were then asked to record the co ordinates of a point somewhere inside of it and then walk our character to another random point on the map.

In order to release the mouse from Minecraft, we had to press the tab key and then we could open Idle in order to type in some lines of code. Thankfully, Craig has helpfully created worksheets to go through all of this information including some extra tasks like creating a Minecraft folder in LXTerminal.

Screen Shot 2014-08-21 at 12.32.38 Screen Shot 2014-08-21 at 12.32.15

As with the CamJam sheets I looked at last week, I’m really impressed with the amount of detail in these workbooks – not only are the lines of code explained, there is some information on the back about what you’ve learned in terms of the language of code and an extension task. The first booklet explains everything from switching the Pi on to getting your code running and has a helpful big red box to remind you about using tab to release the mouse. From there you move on to making  flowers follow your character, then building a house in one go, using chat, freezing water and making a ‘block fighter’ mini game.

So let’s see how simple the instructions are to follow.

My first problem was that I couldn’t really remember how to control Steve in Minecraft so I had to sit for a while and press buttons until things happened – left click allowed you to smash things (either with your sword or without), right click allowed you to place blocks. Pressing E came up with a list of different materials that you can use to build. Pressing the space bar allowed you to jump and double pressing it allowed you to fly (double pressing a second time made you drop to the floor). I could also press ‘esc’ to alter the viewpoint from first person to third person (some of our group felt that the first person view made them feel a bit seasick). So I built myself a house…..


In order to teleport into my house I need to make a note of the co ordinates of it – in the top left hand corner, in white, are the xyz co ordinates of my front door (which need to be rounded to the nearest whole number for the code to work). I actually want to teleport to the middle of the room so I’m going to use -30, 8 and -32 in IDLE an then save my code.

I hit upon a problem when I tried to run my code – I kept getting the error “no module named mcpi.minecraft” …a bit of fiddling and I discovered where I’d gone wrong – in my infinite wisdom, I’d saved my teleport file to completely the wrong place (I found a directory called .Minecraft and thought that sounded right), it turns out it’s important to save the file to the Documents folder called minecraft. So, now my code works I can move my character away from my house, tab out of Minecraft and then hit f5 in the Idle window and….tada, I’m back in my house!



I’ve mastered booklet 1, with one minor hiccup, so let’s take a look at number 2, the flower path – my goal is create a path of flowers that follow me around the map.

Screen Shot 2014-08-21 at 15.32.02

Maybe I’m just a bit more confident now, but this took me a few minutes to type in and, apart from accidentally missing the letter e off of Minecraft in one line of code, I had no problems….until I decided I wanted to get the flowers to stop following me, then I had a massive problem – luckily I’d written down that in order to stop the code you had to press ‘ctrl + c’ in the Python Shell window, otherwise I know I would have found myself getting really annoyed.

The extension task for this activity suggests changing the block variable value so that instead of flowers, you get melons, gold, water or even lava following you – I remember on our course we managed to make exploding dynamite follow us, which was highly amusing, albeit very destructive. Using this page I decided to try getting some different things to follow me – it did not like it when I tried to get Emeralds to follow me and I got a recurring ‘fail’ message across my screen and when I tried 319 for a ‘raw pork chop’ I ended up with a trail of wooden signs following me, so I guess it’s a bit of a case of trial and error (I did successfully manage to make running water appear under my feet using the codes).

Anyway, this is another fun Minecraft hack from Craig.

Just a final point – as I went to quit Minecraft, I suddenly got really upset that all my hard work building my house would go to waste, so I did a little research – by pressing escape I could quit the game, but the next time I loaded up Minecraft, instead of clicking on ‘create a new world’, I could click on my existing world and go back there -it seems that Minecraft Pi autosaves. While doing my research I learned that the version of Minecraft for the Raspberry Pi is a much more simple version compared to the full version so does not have the same scope for multiplayer etc, but it’s still good fun!

Personally, while Minecraft is a bit lost on me, I think that these 6 booklets are a fantastic way to get children interested in word based coding over block based because it’s not just typing in lines of code to make a message pop up, it’s typing in lines of code to ‘hack’ a game that they already play – it has huge mass appeal and I can’t wait to show the children I teach these booklets and let them have a go!

One thing I really appreciated about using IDLE over the LXTerminal is that it preempts the code you are typing and a little yellow box started hovering over my current line of code, suggesting what the rest of the line might need to look like. I also found that IDLE automatically put in line indents, which can be one of the reason lines of code fails.

So, if you teach children who are interested in Minecraft, I would thoroughly recommend taking a serious look at Craig’s worksheets and giving Minecraft hacking on your Raspberry Pi a go!!

Espresso Coding

We’ve been using Espresso in my school for a number of years for subjects like history and English. I’m sure most schools have one of their servers installed somewhere in a forgotten corner. As a maths and ICT teacher, I’ve never really found much use for it, but occasionally I’ve given it a cursory glance. Earlier this year we were sent information about a free trial of Espresso Coding, which I decided to take a look at with my Year 3 and 4 children in order to introduce some of the concepts of code and to see if it’s any good. We’ve been using it in the classroom since January 2014. Espresso have said that they will start charging from October 31st 2014 (I can’t seem to find the price so far). It seems to operate completely online and be managed separately from the main bulk of Espresso (which requires you hosting a server within your school that they manage externally), however, this may change once they start charging. I’d be interested to see what they charge since Scratch and  Scratch Jr are comparable products, but are both completely free.

So, what do you get for your money? Espresso have created 2 units of work for year groups 1-6 and in each unit they aim to teach a develop various different coding skills. They’ve also introduced a ‘starter unit’ so that you can recap the information from previous years without going all the way back to the beginning of Espresso Coding.

Screen Shot 2014-07-19 at 19.20.25

Each unit is broken down into 6 lessons and each lesson also has 6 parts to it, which does make the software fairly idiot-proof, however, it does mean that there is an awful lot of repetition. Your more capable children could quite easily jump straight to Step 6 of a lesson and find no difficulty with the task.

Screen Shot 2014-08-15 at 15.05.30 Each activity is introduced with a simple video explaining what you need to do and how you need to drag your blocks into place to achieve the expected outcome. This means that Espresso Coding is really good for those teachers who are less confident with coding and the language of coding.

After watching the video you are taken to your ‘game’ in the My Design tab – here is the start screen for Unit 4a -> Lesson 5 -> Healthy Eating (lesson 6 is always a ‘design your own game’ option using the new skills you have just learnt).

Screen Shot 2014-07-19 at 19.36.45

This basically shows you the four images you can animate – in Scratch any image that you can manipulate and get to move is referred to as a sprite, which is the term I now tend to use to differentiate between something that moves and something that is in the background so that when children move on to Scratch they understand the term.

While you are creating your code, you can get back to the game screen by clicking on the “My Design Tab” and to play your game, you need to hit “Run”.

So, when you enter the My Code tab you have a selection of control bars and a load of pictures that you can drag into place to write your code:

Screen Shot 2014-07-19 at 19.44.31       Screen Shot 2014-07-19 at 19.44.10

By dragging the blocks into place you should end up with something like this:

Screen Shot 2014-07-19 at 19.39.02Screen Shot 2014-07-19 at 19.38.33

Let’s take the very bottom line of ‘code’; if I were to read that to the children I would read it as “If dog hits burger, burger gets randomly placed somewhere new and score goes up by -10”. As you can see, it’s all very simple and self explanatory.

You can see how strange it would look if I put the blocks the wrong way round – the sprite (or noun, or object or whatever you want to call it) must come before the instruction – it’s a bit like writing a sentence in literacy (cross curricular, cross curricular!!!!)

Screen Shot 2014-07-19 at 19.37.29

The whole code basically makes the dog move in straight lines constantly in whatever direction key you press (I tend to subtly hint that WASD is a great key combination, but that’s because I’m a big geek). When the dog hits one of the items of food the score, or variable, either goes up or down and then the food item randomly relocates.

So, what I’ve found is that the children really enjoy using Espresso Coding – probably because they can’t really go wrong so it’s nice and safe. They really like the big cartoon-like characters and the simple instructions, however, I found that after a while they began to get a bit bored with being constrained to one skill per unit. They started to skip lessons out and jump straight to either lesson 5 or the ‘create your own game’ section and just have a play. In particular the boys were really eager to move on and so I tended to use Espresso as a starting point for coding, but once they children were more comfortable I moved them on to the Scratch cards (more info here) and even onto the Code Club resources because that allowed them more opportunities to be independent learners.

Espresso have worked hard to try to make their resource cross curricular and have even got a few lessons designed to work on a iPad and have a good awareness that many KS1 and 2 teachers really don’t have a clue about coding, however, it is a limited application that can get a bit tedious and works best as a way to introduce skills before moving on to more complicated resources.

I would recommend Espresso Coding as a useful stepping stone, although that does depend entirely on how much they plan on charging for the product. Personally, I haven’t renewed my contract for Espresso Coding because, while you are teaching children coding concepts, there is no independence or opportunity to really use the coding skills. It is a little bit too much of a ‘paint by numbers’ approach to teaching coding and I prefer using Scratch or even Hopscotch on the iPad to Espresso.

Raspberry Pi – CamJam EduKit (part 2)

After the success of my first post, thanks to Raspberry Pi tweeting about it, I thought I should move on to the other three worksheets that come with this pack (there are another two in the process of being made). I’m really pleased with the feedback I’ve received and I’m really looking forward to seeing the new improved sheets that Tim Richardson is hoping to create using some of the things I said in my blog – another reason why these are such a great resources, the developers are willing to listen to feedback and use it to improve their work! Thanks guys.

So, the next three sheets are entitled: User Input, Button and Buzzer. I’m curious to see what exciting things I’m going to create this time round!!

The first thing I need to do is rebuild my LED circuit from sheets two and three (my bad for dismantling it after the last blog – stupid need to tidy things neatly away) – now that I feel a bit more comfortable with the bread board etc this should be a bit easier!

Circuit built from memory, I was about to plug it in then remembered my own warning from the end of the previous blog and carefully checked that I hadn’t made a silly mistake (once again I’m so grateful for my PiBow Coupe case with the pin numbers all marked up for me). I turned on the pi and thought it was well worth checking my circuit was set up correctly by running the blink programme I’d made in sheet 3 – it took me three attempts to remember how to access the directory where the programme was stored (cd EduKit was the code I needed), but eventually I got my LEDs flashing and was ready to move on to my new task. It was only after I opened up the worksheet to get to work that I realised that the first line of code on the worksheet helpfully guides you to the right directory – well done me!!

So, once again we’re jumping up in the difficulty scale with significantly harder lines of code here. On the one hand the user could quite conceivably copy the code and get the results without any understanding, but the joy of these worksheets is that they do explain what many of the lines of code mean so that people like myself with little or no knowledge can begin to understand what we’re actually doing.

Most of the code that we’ve seen before is explained with hashtags as in the previous sheet, but some of the more complex code is not fully explained and instead is simply summarised – I think I would have preferred having the option to understand more layers of the code, for example that if you put

print "words are here" 

whatever is enclosed in the speech marks is printed to the screen on running the programme, however, I appreciate that the CamJam guys are trying not to overcomplicate things – perhaps a sort of glossary of new code terms could feature at the end of the page for the geeks like me who want to go deeper? The same is true of lines that involve == and of course > which I understand as a maths teacher, but sadly there are plenty of teachers out there who may not understand is meant by the less than, greater than signs!

Overall though, this is another great worksheet and I had fun trying out the different combinations. I had two debugging problems this time around, the first being that for the green LED I’d managed to type ++ instead of == which meant it kept only selecting the green LED and the second was a sneaky space bar which slipped into one line of code before a bracket meaning that the LED just flashed once and ignored the count command. I also nearly forgot the final line of the code to clean up the GPIO pins, but I remembered in the earlier sheet that this was stressed as important so I quickly tweaked my code to include that line.

This time the sheet finished with “do not disassemble this circuit” so I was ready for worksheet 4 and my button.

As with worksheet 2, we are once again introduced to the new components (the button and the ‘other’ resistor in the pack). I’m afraid I couldn’t quite get my head around the concept of a ‘pull-up resistor” from reading about it on the sheet, but I’m hoping this will make more sense once I’ve built the circuit, or else it won’t be something that I need to understand in detail.

As soon as I began to construct the circuit it became more clear – in the previous circuit, the resistor sat between the ground and the LED making part of the completed circuit, this time my circuit goes ‘live’, resistor, GPIO input, button, ground with the resistor sitting neatly between the live input and the button itself. I think I know how it works now.

At this point I’ve realised I have yet to discuss the different types of pins on the Raspberry Pi, so a quick run through – there are 3 main types of pins: live, ground and GPIO. if you connect a circuit from live to ground with an LED in the middle, you will have a lit LED – the live does not work based on any input from the Pi, it is ‘always on’. Live pins can be either 3.3v or 5v. Every circuit needs to be connect to a ground pin, which is what makes bread boards so useful, you can utilise one row to take all of the ground connections, however, there are several grounds on the Pi to make things easier. Finally you have the controllable GPIO (general purpose input/output) pins which can be numbered in one of several ways, but the most common is BCM numbering and this is what is marked on my case. The key thing to remember is that every circuit must end at a ground.

Anyway, back to my circuit, which now has a nice, shiny button installed


It’s almost as though the creators of the sheet read my mind as this time all of the new commands ARE explained in a box at the end – fantastic!!

This was a fairly easy sheet to work through and this time I only made two minor mistakes (I accidentally put a capital P for print and I forgot my semicolon after the else command). What I’m really appreciating is that in the terminal box the common commands helpfully colour in if you’ve spelt them correctly so if I type print it becomes a lovely turquoise colour and if I remember to put speech marks either side of my printed messages then they go a lovely green colour, it’s great for debugging and makes the lines of endless code look a little bit more interesting.

On this page I also really like the simple end paragraph along the lines of “this will keep going until you press ctrl + c” because I think I probably would have panicked without that instruction. So sheet 5 is getting a massive thumbs up and I’m pleased that my button does something (even if that is just to print “Button Pressed and 0” to the screen).

No instruction to keep the circuit, but I’m not taking any risks as we move onto the final sheet, the buzzer.


I almost feel a bit sad that I have used everything from my tin to create the final piece of my circuit – this time the worksheet begins by explaining what a function is and how you go about defining and calling one, which is fantastic. This is something I’ve sort of got my head around from Codecademy, but seeing it explained another way has helped to consolidate my understanding! My final task then, is to programme the buzzer to beep out “SOS” in morse code and repeat it a user defined number of turns.

So, once again another successful and easy sheet to follow – I’m really beginning to enjoy myself and sad that I’ve run out of sheets. My mistakes this time were really silly – in my haste to finish I missed out an entire function so when I tried to run my programme it told me that ‘wordSpace’ was not defined. There is a great little extension task on the end of this sheet so that after you’ve made the buzzer beep out SOS you can think about the code for making it do more letters. My gut reaction is that I now want to be able to use the button to make the buzzer go off and I’m already trying to think about how I would programme that so these sheets have really got me thinking, but more importantly, they’ve really helped me to understand python through practical application and I’m feeling a real sense of achievement.

Once again, a great resources from CamJam and well worth the investment in the EduKit tin – I’m really looking forward to letting my Year 5 and 6 Code Club have a go at working through them all and seeing what their reactions are.

Raspberry Pi – CamJam EduKit (part 1)

As I have mentioned somewhere in a previous post, the Raspberry Pi community is very friendly and eager to help people. One of the most proactive groups I have come across is a meetup group in Cambridge called CamJam*. One of the organisers of CamJam, Michael Horne, mentioned something on twitter the other day which caught my eye. He was talking about the CamJam EduKit, which he had helped develop with the PiHut in order to provide teachers with everything they need to get started with the Pi.

*Raspberry Pi meet ups are held all over the country and referred to as Raspberry Jams, but I have yet to find one near me in London (I’ve only seen information about the Cambridge and Manchester Jams so far, but maybe I’m looking in the wrong place). The Cambridge one seems to be a really friendly event and I would love to live close enough to pop by.

There are two things which appeal to me about the CamJam EduKit, firstly they’ve really thought things through and have also created a bunch of basic worksheets, which can be found here and secondly, it only costs £5 plus p&p (which was £2 when I bought my kit).

So, what’s inside the kit:

IMG_5080It’s a useful little kit – you get 3 LEDs (light emitting diodes if you want to get fancy), a simple switch (mine came in two parts, but I’m not sure if this is normal – you simply push the red bit onto the base to make a working switch), some resistors (according to the data sheet, 3 are 330 ohm and a is 4.7k ohm, sadly, at this point in time, this doesn’t mean a great deal t0 me), a small bread board, a buzzer and some wires.

Since owning a Raspberry Pi, I’ve learnt a lot about jumper cables, but the simple fact is, if it’s a sticky out end, it’s male, if it’s a hole to slot something in, it’s female. You can have male to male, male to female and female to female cables; the female end plugs onto the GPIO pins of a pi, the male ends slot nicely into bread boards, but realistically you’ll need a selection of wires for most experiments so it’s great that this kit gives you several male to female along with a couple of male to males AND they’re conveniently colour coded. I would, however, recommend taking a look on ebay or amazon as I picked up a pack of 20 or so of each type for a couple of pounds – I’d also like to mention that when I first got a Raspberry Pi, I naively went to Maplin and asked the young man at the desk if he could help me find some female to female jumper cables…he looked at me blankly and wondered around pointing out a variety of different cables before giving up, so when you’re talking about jumper cables, don’t expect other people to know what you mean!!

So, the first of the CamJam sheets is a very simple ‘setup and go’ activity – the traditional first thing to do with code is get the computer to print back “Hello World!” and so, of course, this is the first thing that the CamJam sheet has us do.

Screen Shot 2014-08-08 at 20.03.43 Screen Shot 2014-08-08 at 20.03.57 Screen Shot 2014-08-08 at 20.04.04

I like the layout of these sheets – it’s very clear what you are expected to do, but how easy is it to actually apply the instructions?

The first thing to point out is that page one is all about the set up for a B model pi, so if you have a B+ your setup will be different – I have been told the revised version for B+ is coming soon. The second page takes you through logging into the pi and loading up LXTerminal, which is great information for beginners and then the actual code itself is explained very well.

So, I followed the instructions through from start to finish and everything has worked as planned, my only problem – I’m now stuck in terminal inside the EduKit directory and I have no idea how to get out of it, however, a quick bit of experimentation has allowed me to discover that I can get back to the home directory by typing in cd ~ again – hooray!

Time to take a look at sheet two and see how we get along – we’re moving straight onto the tricky stuff here with both LEDs, resistors and a bread board (which I still know nothing about).

The first few pages of this sheet are a helpful guide to the components – I’m beginning to think that this kit is aimed at KS3 children, but it’s helping me and I think the more able KS2 children would really enjoy learning some practical applications of the python they’ve been learning in Codecademy.

So, the first thing I needed to do was turn off the pi and build my circuit – the worksheet doesn’t guide you through shutting down, but luckily I knew to type ‘sudo halt’ into my LXTerminal window. I’m not going to lie, this was the first time I’ve used a bread board properly and I felt a massive sense of achievement once I’d slotted in all the bits. I originally had problems getting things to stay in place until my other half pointed out that I needed to really push the resistors into place and not just slot them in loosely.

IMG_8981Achievement unlocked, it was now time to start typing some code and I fell into my first foolish mistake while trying to access my EduKit directory. It’s so important to remember in Python that case matters so my first attempt to access the directory lead to a “No such file error” because I’d forgotten the capital K for EduKit. An easy, but common mistake.

What I particularly like about this worksheet is that after you’ve typed in the lines of code, they are explained below so that you have an idea of what you are doing.

My only problem was that I had made two mistakes in my code – firstly I’d written a full stop instead of a comma in one line of code and secondly I’d written ‘LOW’ as lowercase by mistake and I had to figure out how to access my code to edit it and the sheet doesn’t explain what to do – luckily I figured out that you just need to retype the nano command again to access it.

Anyway, so far the first two sheets have been really easy to follow so let’s finish off this post by taking a look at sheet three since it immediately follows this one.

The third sheet in this series simply walks you through typing the code to make the LEDs blink – this time there are a lot of hashtags in the code, which means notes from the writer rather than relevant lines of code so I obviously didn’t type them into my terminal, but these stood as simple, useful reminders of what different commands meant. The explanation for this code is therefore embedded in the code rather than as a box at the end – I like this because it feels like progression from the first two sheets where everything is explained separately.

It was during the debugging stage (I’d randomly put a full stop in the middle of the first line of code), that I remembered that by pressing the up arrow you can get the terminal to repeat a previous sentence so instead of constantly typing in “sudo python 3-blink.py” I could just press the up arrow a couple of times and it appeared for me – useful thing to know!

Anyway, while I feel the electronics setup may be tough for some of the less able KS2 children, these are a fantastic set of sheets for use with upper KS2 and certainly with KS3 and I’ve been really impressed with the ease of use and the attention to detail. For the beginner, this is a really useful tool and I would definitely recommend taking a look and purchasing a kit yourself.

If you are planning on handing these worksheets and kits to children to work from, I would emphasize the importance of knowing which GPIO pins are ground, and live and probably encourage them to check with an adult before booting up in order to avoid damaging/destroying the Pi (which can be done with an incorrect setup!). The lovely PiBow Coupe case that I bought from Pimoroni helpfully has all of the pins labelled to avoid confusion and for the B model Pis you can print out something called a Raspberry Leaf which is a simple guide to the pins (I’m sure there will be one for the B+ available soon). Someone on my course actually had a little keyring Raspberry Leaf made from an old circuit board which slotted over the pins, which I thought was pretty cool. Anyway, it’s definitely worth checking that you have your circuit set up correctly as GPIO to ground and not live to GPIO or something equally destructive!

So the conclusion is that these are a great free set of sheets, especially for beginners and the really cheap kit has everything I’ve needed so far to complete the tasks and feel a smug sense of self achievement. Thanks CamJam and PiHut – keep up the good work!


Quest – Text-based adventure game (creating a game)

For an introduction to Quest/ActiveLit, click here. For information about creating your first room, click here.

So, after creating my single room and getting my head around how to use this software, I’ve made a start in creating my full game from the map I created earlier:


As a starting point, I created every single room, which meant I had to give them all names. I would suggest that the rooms are named during the planning phase.

Once I’d created all of my rooms, I could then add in all of the entrances – I know in my final game that I want some of the doors to be locked and/or hidden, but for now I just want to get them all in place – fortunately there is a tick box as part of the ‘exit’ creation tab, which allows you to make your exits two-way, meaning you don’t have to create them twice (once for each room).

Screen Shot 2014-07-31 at 16.51.26

So, my next step is to hide/lock some of my doors.

Screen Shot 2014-07-31 at 16.57.39

And now I can start populating the rooms with objects.

I’m not going to go into too much detail, but my game creation took approximately 3 hours and then I had to ask a friend to beta test it, at which point several problems were identified. I’m happy for people who aren’t sure to drop me an email, but I also found the creator of text adventures, Alex Warren, on twitter and he seems very happy to help and get involved.

So here’s how my populated game looked after creation:

Screen Shot 2014-08-08 at 19.29.40

And here’s a copy of a few bits of the log from my friend playing through, which helped me to make some changes.

Screen Shot 2014-08-08 at 19.30.41

One thing this highlighted to me was the importance of creating an object and a description for every single noun in the room. My room description mentioned a computer, but I hadn’t created an object called computer and this led to my friend getting very, very frustrated.

I also found that it was important to add extra verbs to word – in one room I wanted to have a picture which you could push to one side to reveal a switch, I discovered two things: Firstly, you need to drop a REALLY big hint in the description that the object can be moved and secondly, that you need to think about the different verbs that people might think of to describe pushing or moving or shoving a picture out of the way. I decided to make the object a container AND edit the verb field like so:

Screen Shot 2014-08-08 at 19.33.52

Hopefully, like me, you’re currently bouncing up and down about the cross curricular links between this particular programme and English/literacy. Not only do the children need to plan their story carefully thinking about how events link into one another, they also need to think carefully about nouns and verbs. They need to know what a noun is in order to understand that every single object in your room is a noun and therefore needs to be created as an object and given a description!

When a pupil finishes their game it can be ‘published’, but this only make it available to other users in the group, making it a safe environment to make mistakes and a great way to help each other think about errors. It would also be an ideal opportunity to discuss debugging as each user tests one another’s games.

My final word on this is that I think it will be tough to teach, I think it will be hard work to explain all the nuances to the children and probably require a lot of running around, but I also think it has so many positives that it would be an invaluable classroom tool as long as you take the time to understand how it works.

If you want to play my game, click here and for now, I’m off to plan my next game!!