Developer Diary 4

A lot has happened since the Diary of last week. The production, graphically and technically went along very smoothly. The audio had a small fallback during the recordings of the voice-over for our young Nathan, but I will get on that later.

Firstly thumbs up for our Lead Programmer Daryll and his sidekick, programmer Robert. Daryll has made great progress this week. He has amazed me, as the planner of Quark, with his commitment (working almost every night till at least 10pm) to get the things he promised to work on this week done in time. But I will certainly not forget to give my compliments to Robert. Last week he was still very busy typing storylines and monologues, now he made a switch to writing a whole different “cake” (and no, it’s not a lie). Instead writing wholy correct English sentences, he now only writes “if else” statements to tell the mouse, what to do, in-game, if the player clicks on it for longer than a second.

Hanny made a lot of progress as well on her eading post of the Graphical part of the game. She made charactersheets of young and old Nathan. Also, for young Nathan, she made a first conceptual ready-to-animate version so I can, as animator, bring young Nathan to life. Nils has made a great progress with the environments for the first puzzle. Lars had a bit non-Quark scheduled agenda this week, so we haven’t seen him much at school or at our Quark-table. Even though he has put work into graphical production this week, we do miss the joy and laughters he always brings.

As said earlier audio had a slight fallback. Our audio artists, Nils en Daryll, couldn’t record the voice-over for young Nathan. So poor Hanny had prepared herself for her big role as Nathan for nothing (this also happened to a certain boy from Pallet Town).

At the beginning of the week we had a consult with the boss of a certain famous game company (and former teacher) and he had heard news of the puppetshow act we gave a while back. He adviced us to take advantage of our ability to come up with weird, unusual things which ultimately result in original, one of a kind results.

Even though our group is small, and consists only of 6 members, the structure of who is responsible for what is complex. So a so called “Bitch flowchart” has been brought into existance. Thanks to that it’s easier to see and know who is responsible for which part of making our game and (most importantly) who has to listen to who (yes, multiple times people have to listen to themselves, as they are their own lead and bitch)

All in all every Quark-member gave it their all, so far possible, to make this week as productive as possible.

Well so far the Developer Diary for this week. I hope you could follow all above, and if not, please reread it all again :P


EDIT:  René would also like to thank Robert very much for taking the time to check his Diary for any spelling errors and correct them.

René