Hey guys, this week was awesome. Everything was just great. Me and Max worked really really hard for the game and all the work paid off. Everyone liked it. Nathan gave some amazing art to make the game look beautiful and our producer, Andrew, helped us on every step. I was lucky to have a great team in my first prototype in the EAE program.
On Monday, we had a dry run pitch. We had a white box working on Monday. From that white box, making a complete prototype was a tough task. We worked hard on Tuesday and yes it was done. On Wednesday, we had our final demonstration of the game, which went really well. This was followed by postmortem. Bob explained us how a postmortem should take place and how it helps. And I think it really helps to improve yourself and make yourself ready for the next challenge.
(All my friends in EAE, you all should know this.) I was talking to Roger during the break in the Game Design class and he said that he was surprised (in a good way :P) and really happy that all the prototypes were so amazing.
WHAT I LEARNED FROM THIS PROTOTYPE?
1) First of all, what exactly is a prototype?
2) In a prototype, learn what is needed. You don't have time to learn everything and then start programming.
3) When things aren't available with you, try to do it yourself.
4) Your co-engineer could go faster than you. You should catch up with him. (what say Max? : P)
Complete experience of making the game was fabulous. It started with a quick prototype followed by a running game. Then the pace slowed down a bit because of few reasons but then all ended well. Looking forward for the next prototype. See you soon C# and XNA :D.
 |
| Screenshot 1 |
 |
| Screenshot 2 |
 |
| Screenshot 3 |
Click here for Monty's Quest Trailer
On Monday, we had a dry run pitch. We had a white box working on Monday. From that white box, making a complete prototype was a tough task. We worked hard on Tuesday and yes it was done. On Wednesday, we had our final demonstration of the game, which went really well. This was followed by postmortem. Bob explained us how a postmortem should take place and how it helps. And I think it really helps to improve yourself and make yourself ready for the next challenge.
 |
| Postmortem of the Game |
(All my friends in EAE, you all should know this.) I was talking to Roger during the break in the Game Design class and he said that he was surprised (in a good way :P) and really happy that all the prototypes were so amazing.
WHAT I LEARNED FROM THIS PROTOTYPE?
1) First of all, what exactly is a prototype?
2) In a prototype, learn what is needed. You don't have time to learn everything and then start programming.
3) When things aren't available with you, try to do it yourself.
4) Your co-engineer could go faster than you. You should catch up with him. (what say Max? : P)
Complete experience of making the game was fabulous. It started with a quick prototype followed by a running game. Then the pace slowed down a bit because of few reasons but then all ended well. Looking forward for the next prototype. See you soon C# and XNA :D.
No comments:
Post a Comment