Ewe Few Crew
Tags
Co-op
Unity​
Action
Adventure
The Game
In this cooperative split-screen adventure, you and a partner embark on a daring voyage to return your livestock safely home. But the journey is far from easy.​
Man The Helm
Arm The Cannons
To protect them!
From your foes!
Adjust the Sails
The Project
Timeline:
7 Months
Team Size:
6
Ewe Few Crew is the culmination of 8 months of hard work by me and my capstone team, Team Electric Eel.
As a team, we set out to create a game that can showcase our individual talents, and make a portfolio piece we're happy showcasing.
In this process we went through many cycles of iteration, designed countless concepts, and had our fair share of both successes and pain points.
About
My Roles:
As we were a small team, we each had many roles. My main ones being:
Game Designer: Iterating systems and holding the games vision.
​
Programmer: Creating front end systems that follow designs.
Game Design
Programming
Designed a changing weather system that interacts with the world.
Developed a ship movement system utilizing the weather system.
Programmed an enemy entity system that attacks your sheep.
Contributions
My Process
"How might we create an interactive sailing system that encourages cooperative play?"
Step One: Record
What have similar games done before?
What Didn't?
What worked?
Stations
Sails
Weather
Oars​
Water Current
i. Research
List your options.
Determine which match your pillars and vision.
ii. Refer
Write out your conclusions for you and your team.
iii. Report
1/3
Takeaways
Technical
Systems Development: Developing large systems, requires constant testing to ensure past features are still working as intended. We had to use a methodical checklist to ensure things were working well with each update.
​
​ Local Co-op: Multiple factors made this more difficult than anticipated. Split-screen, cameras, control integration, UI placement, and world interactions were some of the challenges that we had to overcome to make this game work.
Challenges
Management
Planning: In a development process issues will pop-up. Miscommunication, unexpected bugs, and sickness are just some of the factors that delay a sprints progression. As a team we overcame these problems by having a flexible schedule, and altering our design to accommodate for the issue at hand.
High Spirits: With unexpected issues comes stressful moments. In times like these it's important to constantly keep the team motivated and in good spirits. Doing things to make sure everyone feels like they're part of the team and are contributing to the project is a necessity.
Plan for the Unexpected: Since there will always be issues of some kind, it's important to think ahead and plan extra time to account for it. There will always be a challenge, how you react to it is what's important.
Conflict: Disagreements are a great thing for the development process, they allow for the team to communicate issues and can introduce new innovative solutions that bring your game to the next level.