Malcolm Bornmann, PPJ 01

Malcolm Bornmann, PPJ 01
List of Completed Tasks - Met with new team for the first time to get on the same page and discuss deliverables and roles, I volunteered to work on the Art Team and Design Team (1 hour) - Reviewed Oil and Cordite documentation from Workshop 1 to familiarize myself with the game (30 min) - Brainstormed ideas in Discord throughout week about lighting, models, character design, level design, mood boards, and story (3 hours) - Created mood board for level design, finding and compiling reference images (1 hours)

Total number of hours: 5hr 30min
Sample(s) of work: The mood board I created which helped spark ideas about level creation

What Went Right: We have lots of great ideas about how we can move forward with the game! The Journey's End Team offers skill sets in art and story, something that pairs well with the direction the original Oil and Cordite Team wanted to go in.
What Went Wrong: This week was messy. It took a while to adjust to the new team size, dynamic, and management systems, we had members miss meetings, new members join throughout the week, communication failures, and an overall imbalance of who did what for the deliverables. As we feel more comfortable with each other and the direction of the game, hopefully all of this will be ironed out, but for the time being, I don't believe we are as unified and efficient as we should be.
Working on Next: - Refine level design ideas with Design Team - Provide ideas and feedback to Art Team as needed - Help update playtest survey - Contribute to status report presentation

Comments

Post a Comment

Popular posts from this blog

Image
Jacob Dixey, PPJ#3 Playtest Survey Draft  - 2 hours 2nd Scrum Presentation - 1 hour Camera Improvements - 1 hour Spinning Action - 1.5 hours COM-Buster Takeoff - 1 hour Pause Gameplay - 1 hour Bouncing - 1 hour Tweaking - 2 hours Samples Spinning and Bouncing Scrum Presentation Pause Menu Positive: The level's visual style came together really well, in addition to many of the core mechanics surrounding flying being solidified with a lot of time put into tweaking it for playtesting. Our meetings have also given us a lot of good ideas for how we can communicate the different states of the player visually, such as heating up changing a shader on the COM-Buster and its trail, and when Overheating causing a fiery effect on the screen that slightly gets in the way of your peripheral vision. Negative:  It was another week of getting things together last minute. I want us to start meeting up earlier (say, Saturday) and then using Monday (or u...
Read more

Getting Started: In the Cloud(s) Sean McFadden Summary (PPJ #01)

Image
This week was spent doing two main things, both seemingly involving clouds. The first was getting our project website setup. I don't think we need anything fancy yet, so it consists of a basic standard website hosted on an S3 instance. I added some nice features like logging and view counting just so we can monitor exposure in the future. The website is really bare bones at the moment, pretty much consisting of only a few lines of text and some empty web pages. I plan on adding some more styling and media over the coming weeks, as we don't have much in terms of presentable media at the moment. However it is important to have a good framework for a modifiable website at the moment, as it can ease the process as the game grows. If you want, you can visit the website below!  oilandcorditegame.com Additionally, I spent a big chunk of time researching and planning the implementation of our clouds system. Since the game world has a massive layer of clouds below the player, ...
Read more

Peter Eldredge PPJ #1

Image
Set up the Unity Project and GitHub, adding some of my useful Scripts - 1 Hour Group meeting about the project and tasks - 2 Hours Conceptualized and implemented a modular enemy framework - 3 Hours Helped Jake with programming the player controller (primarily the physics) - 3 Hours Final setup for the demo/build - 1 Hour Enemy Example Enemy Framework Example The behavior above was made just by tweaking some values on prefabs and scriptable objects. The idea is that this will be expanded throughout the course and we can have an easy way to create new enemies. The behavior system can also be expanded to movement patters and a health system/weak points. Here are some inspector tabs to demonstrate how the behavior was achieved. The scriptable object is the attack behavior. It controls the conditions for the attack to fire as well as the prefab which handles the attack itself. In this case, it simply instantiates the FastLaser prefab. The condition that must be met are that...
Read more