Game Design & Architecture:

Phagocitosis

Data flow Structure:

1. Game start

1a. Initial animation
Actionscript Progress Bar tutorial
1b. Load Menu

...
Play
Getting a button to work
And the move to scene code
...

2. Game Update

2a. Start

Load new map
Perfect tutorial
General Check if something has been loaded tutorial
General Using XML tutorial, for the map data
General tables tutorial at: Game Development with ActionScript/T5/Multidimensional Arrays
Create entities
General object tutorial at: Game Development with ActionScript/T5/Objects

2b. Update

2b.1- Input and CallAI (pathfinding).
Game development with ActionScript: T8 -> Keyboard input.
2b.2- Checks for walls blocking.
2b.3- Moves
2b.4- Checks for winning Conditions. (what with killing conditions?)
2b.5- Checks for collision with other Entitys.

2c. End

Unload map

3. Game Exit

Flag values and such:

isMoving:

0: not direction assigned
1: direction assigned

direction: numpad alike

0: let your imagination flow!

4: left
2: down
6: right
8: up

matrix cell values:

-1: default/error

0: nothing
1: wall
2: start point
3: finish point
4: killing point
>4: future addons, important to leave the checking open for this

2b- Update method if all the Entities are treated the same way (every big-black-dot step is called for every single Entity):

2b.1- Input/CallAI.

2b.2- Checks for walls blocking.
2b.3- Moves
2b.4- Checks for winning Conditions. (what with killing conditions?)
2b.5- Checks for collision with other Entitys.

2b.1- Look for the "isMoving" flag value on every Entity:

0:

if PC, check for move input, and write in the flag direction. Then isMoving=1;
if NPC, check for pathfinding methods or whatever, write in flag direction. Then isMoving=1;

1:

nothing?

2b.2- Checks if there's a wall blocking in the dir "direction":

Switch with the flag direction' values:

checks, in that direction, the next cell's value:

0: nothing
1: isMoving=0, direction=0;

NOTE: the killing and winning conditions will be treated in other method