REVIEW!!

Well unfortunately I haven't been able to blog for the last few weeks due to school exams and other disruptions... So, information dump.

INDEV CHANGE LOGS:

## Match'n'Grab V In_0.01:

## Created by Alex Engelbrecht, AEG

## Version dev begin date:  04/09/2012

##                          DD/MM/YYYY

##

## Version dev end date:    04/09/2012

##                          DD/MM/YYYY

##

##

## Current Features:

##          -Imports all useful modules

##

## Additions and Changes:

##          +Importation of modules

##

##

## Match'n'Grab V In_0.02:

## Created by Alex Engelbrecht, AEG

## Version dev begin date:  04/09/2012

##                          DD/MM/YYYY

##

## Version dev end date:    04/09/2012

##                          DD/MM/YYYY

##

##

## Current Features:

##          -Imports all useful modules

##          -'Constants' class for storing

##              system variables

##

## Additions and Changes:

##          +Addition of class '_constants'

##

##

ALPHA Change Logs will be posted once Alpha version is completed.

Review:

Progress is a bit behind schedule but going well, game will be finished on time.

B.14159265359

Okay, this day for me is a milestone. Today I officially complete the planning phase of this assessment and moving into the actual production phase. Order of operations for the creation and completion of the Indev--Alpha version will continue (roughly) as follows:

1) Create game folder/file structure

2) Create code objects:

-Word/Picture objects

-Falling Obstacle objects

4) "Grabber" code object

3) Create main game program (Word/Picture object matching, falling obstacles, etc).

(1--4) Debugging program: All the while I will be upgrading and creating a "Debug" console so that I may interact with the game or diagnose faults behind the scenes.

The Indev/Alpha Test Plan has been created pre-development.

Then with the move to the Beta version comes the inclusion of:

-Level Selection Screen

-Functioning Log In Screen

-Extra Levels/Themes

-Inclusion of modding API

-"Real" Sprites (instead of "Dummy" sprites)

A Beta test plan will be created as features are added.

Another Weekend Ahead...

So ends another week, and begins a new weekend. For me weekends are time of work. And this weekend I shall work. At the present time I have completed my brief and have begun making essential files for running the game, as well as folder structure. By next week I will begin coding.

The future...

At the moment I'm so lazy I wont format that title.
Anyways...

Expect posts to get more frequent as I begin coding, there will be an update at the end of each or almost each day, as well as a major post at every new version update. These major posts will include a change log, showing Additions, Modifications, and Removals from the game, along with an up to date bug report on new, persistent, and recently removed bugs.

Back to B.e(ish)

I have now almost recovered from my setback a couple of days ago. I am planning that a lot of hard work over the weekend should put me perfectly back on planned schedule. So far I have re-done my mind map to approximately what it was before hand. Story-board is coming along, as well as my final specifications brief.

.......

........................

Well... Lost my USB stick yesterday... And back ups are out of date. What do I call this? C to B?  Yes I am now slightly behind unless I recover my USB stick. In order to stay productive however, I started writing some pseudo code. Yeah. That's it.

Meh.

Unfortunately I didn't complete my specs brief today as I hoped, however, I am still a week ahead of schedule. I will complete the brief over the weekend in order to keep this week ahead of me.

Another A
"My Journey From B to C"

In the very first post on this blog I discussed the philosophy of the Adventurer setting out on his journey. Like all other journeys, the Adventurer does not travel from A to B, but instead from B to C within the entire journey A to Z, as the real question is not "How does the Adventurer get from A to B?", but instead "How did He get to A in the first place?".

Today I have started another sub-journey within my journey from B to C. This day marks A in B to C. Call it B.a; but is it? No. Because how did i get to that .a in the first place? In fact, this may be about B.d or even B.e.

This B."e" milestone is the beginning of the write-up of a Final Specifications Statement Brief. This will include a list of initial brief points along with self identified step-ups. It will also include story board, code flow-chart and pseudo-code.