{"author_name": "Sam Hogarth", "cat": "LD #23", "comments": [], "epoch": 1335008520, "likes": 0, "metadata": {"p_key": "57902", "p_author": "Sam Hogarth", "p_authorkey": "508938", "p_urlkey": "93651", "p_title": "Post-Lunchtime Update", "p_cat": "LD #23", "p_event": "LD23", "p_time": "1335008520", "p_likes": "0", "p_comments": "0", "p_status": "UPD5", "us_key": "508938", "us_name": "Sam Hogarth", "us_username": "Sam Hogarth", "event_start": "1334880000", "event_key": "10", "event_name": "LD23"}, "text": "

Lunchtime (nom!) is over, time for a brief update.

\n

Well, my idea is starting to take shape now, and although I don’t have anything visual to show, I have quite a lot of the groundwork prepared. My focus has been on creating a way to encapsulate each of these tiny worlds. The game engine will load a set of these when the game is started, and sequentially let the player play through each world. The “meta” world oversees the flow of the game, and will look like a scientist’s laboratory.

\n

As the player completes the worlds, a SCIENCE! meter will fill up. Once it reaches the top, you win!

\n

I have devised a system whereas each world is represented by a class. This class is responsible for loading all of the content, handling game logic and rendering that particular world. Therefore, each class is itself a self-contained game, with the meta world feeding in the appropriate objects from the game engine.

\n

Let’s take a look at the Kanban board:

\n

\"\"

\n

Next up: rendering the meta world. To PAINT.NET!!!

\n

 

", "time": "April 21st, 2012 6:42 am", "title": "Post-Lunchtime Update"}