Storytelling - mapto/sprks GitHub Wiki

A game is nothing without a game world. A game story world is needed, because it makes it easier to come up with details when you know the background.

So far we have the following bits from a story world:

• Global Sparks Introduction with interviews (https://github.com/mapto/sprks/blob/master/views/intro.html)
• The Scenario Incidents from "UCL Behaviour and Attitude Survey Report" in Dropbox->Reading
• Incidents in repository (https://github.com/mapto/sprks/tree/demonstrator-1july/static/incidents), for a detailed example see (https://github.com/mapto/sprks/blob/demonstrator-1july/static/incidents/infrequent_use.json)

Our current main way to convey the storyworld to users is text. We are planning for skin/theme illustrations plus minimal animations. However, the text still needs to be nice for the user to read. Sound would also be nice.

###Timeline Oddly enough the timeline is a factor here as well. it is the one to drive the personalisation of the game to the user. One key task is to introduce new elements in an appropriate time moment. This in fact is the story being told during the game.

Time starts when user registers. When connection is lost, time stops, but resumes on login. Each of the first weeks of the game the following should happen (sort of tutorial):

• 0 - Intro
• 0.5 - stories/users
• 1 - policy button
• 1.5 - score window
• 2 - graph
• 2.5 - time controls
• 3 - score button
• 5 - profile button