New year yippie! Our team at Domino Theory has started this new semester in a positive start, with a quick review from the work we have laid ourselves from last semester. We used the first week to familiarize ourselves with the workload that we will have, both working for the game that we are creating and also the workload that we have for the semester. We also used our first time meeting each other since last year (haha) in person, re-aligning everyone's visions with the game, and took our time reaffirming what we wanted for our final product, we also answered some things that we asked ourselves with playtests, and what we want to focus on for the upcoming playtest that we will have.
As the main programmer for the team, during our time in meetings, I kept on asking about our mechanics, and what the team's vision is for it, to make sure that the vision can be done in the final build. One question that I realized we haven't answered and had asked in our recent meeting is "How is the player going to play? Controller or Mouse and keyboard?", we have been designing our game with a mouse and keyboard in mind, which we will end up having as the main controller the player will play our game with, but I used this time to reason to my team why this was important to know because of the known issues that we have.
Did you like this post? Tell us
Leave a comment
Log in with your itch.io account to leave a comment.
Like that you're checking the vision against the mechanics that you're programming to ensure that they align. This will ensure a more coherent final product.
Its awesome to hear that during your meeting to keep a clear vision on the core mechanics as well as the player controller as this can be a problem later on if this vision gets confused with the level designer where the player controller may end up not working so keeping it clear within meetings with what will be happening with that is very important