The gameplay prototype doesn??™t have to look pre y, but it has to be fun. I??™ve built 2D overhead maps
that show a bunch of di?¬? erent colored triangles moving around on the screen to prove how well characters
will react to the environment, move together as a team, respond to stimuli, and stu?¬? like that. When it is all
said and done, the code responsible for this can still drive a 3D world.
On multiple prototypes:
Something else I like to do is build multiple smaller prototypes to prove out a variety of di?¬? erent gameplay
issues instead of trying to always have to lump it all into one large prototype. You might have a basic prototype
to prove out basic control mechanics, like running, jumping, etc., then have another to prove AI, and
another to prove out other things like driving cars, ?¬? ghting, etc. You must still demonstrate how all of these
will work together, but having a variety of small prototypes can o en allow a bunch of di?¬? erent team members
to each focus on a di?¬? erent aspect of the game.
Along with the gameplay prototype, I also like to have some of the art team, along with possibly some
additional design or programming help, build a visual prototype that accurately demonstrates what a portion
of the game will visually look like.
Pages:
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061