Date/Time: 10/18/18
Members Present: Nathan Murphy, Eddy Basharat, Chris Lenart, Michael Zhang
Topics/Agenda: First meeting day. Figure out what game to do! Why we should do it! Assign roles to team members! Do a user interview with someone in class.
Action Items with names assigned: Each member must pitch in ideas for which game should be done, and why.
- There was a unanimous decision to do a fresh take on Adventure!
- All members love the idea of an old classic dungeon game.
- Discussed what makes the game so appealing and fun to play to each and every one of us.
- Assigned Micheal the task to oversee the website, while Chris will be Head of coding, Nathan will be lead game designer, and Eddy will be the Creative officer.
- Decided to have a website template up by tonight, and have an algorithm ready for SDP Day 2
Date/Time: 10/25/18
Members Present: Nathan, Eddy, Chris, Michael
Topics/Agenda: Discuss algorithm, and further discuss roles of everyone in the group. Decide the title for the game amongst the group.
Action Items with names assigned: Michael is to oversee the website, Chris is to be head of coding, Nathan is to be lead game designer, and Eddy is to be creative officer.
- It was decided to not start coding until an algorithm/pseudocode has been established first
- Nathan and Chris work on Algorithm during the meeting time for about 10 minutes.
- Nathan talks about how many levels are wanted, and how many monster types could be added. Discussed looking at maybe about ten levels with ten different bosses if there is enough time to do so.
- All decide to race each other after class sometime, and whoever wins gets to name the game.
- Eddy discusses a possible story to be added to the game manual to give it an old vintage feel like the old classic “Adventure!” game. The story would follow a normal kid who would have power thrust upon him somehow and be forced to travel and battle monsters to ultimately break the curse that has spread across the land.
- Eddy also pitches some ideas for the SDP video. Have the video be centered around Chris being stalked by a guy with a sword, who tells him to break the curse. Rough pitch. decide to keep adding onto that for the storyboard slides. All the members loved the idea. They praise Eddy for his smarts and creativity.
- All members are tasked to do some part of the code to make it fair, but mostly agreed to focus on our respective parts for the time being.
- Decide to continue on SDP day 3.
Date/Time: 11/15/18
Members Present: Nathan, Eddy, Chris, Michael
Topics/Agenda: Finish up Beta code, talk about final video ideas, interview someone else for the 2nd interview, and add it to the site.
Action Items with names assigned: Michael and Chris interview someone, Eddy works on storyboard and user manual story. Nathan proof reads the code to check for errors/suggestions. Eddy will also direct/edit video. Michael and Eddy are to work on user manual together and add it to the website.
- Michael and Chris interview someone for the 2nd interview and put it up on the site.
- Eddy works on the storyboard for the video, and explains the final idea for the video. Talks about times to record the video, and props to bring to campus. Need a sword, possibly a cape, or mask. But DEFINITELY need the sword the most.
- Nathan discussed how there can’t be any additional levels as previously planned, because time is running out. The code is practically done though, only needs a little bit of touch ups.
- Eddy decides to shoot the video on the 26th and 28th, because it’s the only time all of the members are free to meet up and record.
- The whole team decides to work on the project a little more during Thanksgiving break if any of us has time to spare, but if not it’s fine.
Date/Time: 11/26/18
Members Present: Chris, Nathan, Michael, Eddy
Topics/Agendas: Prepare for Final testing with instructor, and shoot video after class. Look for locations to shoot in. Discuss presentations briefly. Prepare for presentations
Action Items with names assigned: Chris and Nathan are to make sure the game runs fine, and to refine any last minute coding. Eddy is to prepare for the video, and look for locations to shoot the video. Michael will supply a camera and help refine sound for final video. Everyone is to prepare for presentations on their own, and practice their slides extensively. Everyone is to also create the presentation slides in which they will speak.
- The first 40 or so minutes were spent testing the game and making sure everything worked perfectly.
- Everything was working like a charm, and we were ready to test with our instructor
- Instructor came by to test the game, he was very impressed, and only asked that Chris add many more comments to the code. Overall he was happy with the way it turned out, and seemed to enjoy the concept of the game.
- After class was over, Nathan and Chris sat down and ate their lunch while Eddy explained to them the video scenes and how they should go.
- Michael gets the camera from his apartment at the Annex, because he forgot it.
- When he comes back, the team realizes that the camera is almost dead even though Michael promised he’d charge it the night before. So his phone was used instead, which surprisingly enough had better picture quality.
- Once all the scenes for that day were shot, we all went our separate ways and agreed to meet on the 28th to film the final parts.
- We all also briefly discuss the presentation slides and that everyone should practice on their own, since there is no time to practice together with everyone’s busy schedules.
Date/Time: 11/28/18
Members Present: Eddy, Nathan, Chris, Michael
Topics/Agendas: Presentations, and finish shooting the video
Action items with names assigned: Everyone is to practice the slide they made in the powerpoint, and practice speaking it before class. Eddy is to edit/film the final parts of the video and submit it by Thursday.
- The group finished the presentation, and was off to start shooting the video again
- Eddy shoots multiple shots of Nathan, Chris, and Michael talking about/playing the game and making sure they all show up on camera, including himself.
- Once filming is done, everyone left, and eddy goes home and finishes editing the video to submit it on Thursday, the 29th.
Date/Time: 12/03/18
Members Present: Nathan, Eddy, Chris, Michael
Topics/Agenda: Last meeting day. Finish up the website before Wednesday
Action items with names assigned: Eddy is to do the conclusion/recommendations, add the game’s story to the user manual, and finish up the meeting notes. Michael is to do the schedule, advertisement, and the rest of the user manual. Nathan is to do the Introduction, Discussion, and put up the Algorithm to the site. Chris is to do the Program Description, and add the game’s entire code to the site.
- This was the last meeting day for the team, and the only thing left to do was completing the website before the 6th.
- All team members chose which sections of the website to do, and switched around sections they were uncomfortable with, or felt other members could do better.
- Once that was over everyone knew their tasks and could begin working/finish working on them.
- For good measure, Chris created a to-do list for all team members and sent it via group chat, so as to help everyone stay on top of things and not forget their tasks amongst their other obligations to other classes.
- Once everyone that was finalized, the team stayed behind and began working on their assignments for about 5-8 minutes before heading off to their next class, or just going to eat their lunch in peace.
- All members decided to keep in touch and update one another on each other’s progress.
