In A Bad Mewd
Third Person Sandbox Destruction Game
The first Game Project as a part of my Education. I made player movement, behaviour and Attacking.
Team Size: 15
Engine: Unity
Time: ≈2 weeks
The first Game Project as a part of my Education. I made player movement, behaviour and Attacking.
Team Size: 15
Engine: Unity
Time: ≈2 weeks
|
|
|
In A Bad Mewd is a third-person sandbox destruction game where players take control of a pampered house cat who is unfairly abandoned (for like 15 minutes, max) and takes revenge by destroying the apartment their owner just moved into.
You scramble around your owners apartment, gaining points for destroying things as you try to find the most optimal route of carnage through your new living space before your owner returns.
How movement functions in this game is slightly overengineered. It follows the standard W&S for forward and back, with A&D for strafing left and right with spacebar as jump. We apply forces to make us move (or just flat velocity in the case of jumping), however I manually calculated the way to keep movement consistent across player rotation instead of making directions local to the player themselves. This comes from the fact that this was the first 3d game I ever worked on in Unity and I was still unfamiliar with easier ways to achieve the same results.
How the attack functions in this game is that I had a collider connected to the cat that logged when an object entered or exited it and when you pressed left click it would then apply a force away from the cat to every object within that collider, launching them away from you and allowing the physics and object breaking system (made by co-programmer Kenan Ege) to do their job from there.
The main takeaway I have from this project is that: Communication is the single most important aspect to a multi-person-projects success.
For the final half-week of the project our communication had clearly failed. Most of us were super stressed, not knowing what was needed, done or was to be cut for time. In the meantime our producer thought the situation was so calm as to not need any standups. In the end I decided enough was enough and held our own group meeting where we went through our Jira board with everyone in our team, talking with each other about what was feasible to do in the time remaining, what was already done but not updated and what could/needed to be cut.
After that meeting we successfully finished every task we had in our To-do and In-progress and managed to get done before the deadline.
Phone number: +46-73 073 85 80
Work Email: SimonMikaelAgren@gmail.com