Loading

Quest – Rapid Fire Ideas

Learning never exhausts the mind. Leonardo da Vinci

Working online with Allen Heard means there is no respite. Its keep up or give in. Move aside, step down. Conversation is now via Twitter but most weeks over the phone. Some conversation work so much faster in dialogue. This afternoon we decided to try and write a game asyncrously in the new web editor. No planning, just throwing it up there. Chinese whispers for IF. That should prove fun. The benefit of IF in a browswer.

I think we have come to an unofficial agreement on a few key points.

  1. The starting point is playing games.
  2. Next is game design.
  3. Learn how to build, then build.
  4. Then code.

The mini Quest 3-4 room games like Escape from Byron Bay, are the aspiration. There is more than enough in these mini titles keep students challenged. Also, we seem to agree that one of the strengths of IF is to bring literacy to another subject other than English. Talk with, supporting and leaning on the English team is vital. See Jane Ashes, we need you.

qr code

 

 

 

Tick Tock Clock for Quest

Following on from Byron Bay, the students have been competing against one another. They set the challenge by how fast you could escape the game.

In an effort to create an official timer – I used the in built time function of Quest and displayed them as a status attribute. Of course, health and score will be in 5.2 and already in the web editor (as it runs on 5.2).

  1. So create a timer, set the variable – here a point is added every two seconds. I have found the speed of the ticker definitely impacts on player/learner focus. Too slow, its doesn’t really matter or doesn’t seem to impact on game play. Too fast and its distracting. Its hardly a scientific analysis, but it seems an intuitive observation.
  2. Set a variable ‘player.Tick’ and ‘player.Tick+1’ to add 1 to your Tick Tock Clock each time a cycle passes (here every two seconds).
  3. Create a player attribute, set it to integer. Lastly display it as a player status attribute. Do make sure you call your timer name and your status attribute  are called something different.

<timer name=”Ticker”>
<interval>2</interval>
<enabled />
<script>
player.Tick = player.Tick+1
</script>
</timer>

Of course, as I am planning in my first web editor Mini Quest – I am planning to set the timer against the player, counting down. Basically counting backwards until ‘BOOM!’ Game Over. In this instance is will be the same interval but setting the atarting value at 300 and -1 for example.

Then there is always a turn counter, another measure of game play, more about making the right decision and thoughtful decision making rather than encouraging focus/fun/pace.

qr code