Skyrim
A mockup of the best seller RPG The Elder Scrolls: Skyrim
TEAM SIZE
DURATION
PLATFORM
TECHNOLOGIES
2 DEVELOPERS
6 WEEKS
WINDOWS
Unity3D, C#
WHAT WAS THE POINT ?
After the Mario Kart mockup, which served as a first project to get our hands on Unity, we started this project to conclude our training on this engine and further expand our knowledge of this popular engine. We had a few obligations regarding the features as we obviously could not replicate all of the original game's features. We had to emphasize the combat system as well as the inventory, The GUI was a big part of it as well. We had the pleasure of working with Music and Sound Designers who made some background musics and sound effects for the game. Integrating their assets was also part of the plan.
WHAT I ENDED UP DOING...
We ended up splitting the tasks in 2 rather than both doing a bit of everything. I focused on the GUI as well as the inventory system and the serialization for the auto save feature. Obviously we both did a lot of small tasks and general debugging, but these were the 3 big things that I did. Being a group of 2 also implies that we didn't have to worry too much about team management. We were in the same room at all time and discussed things most of the time. We simply kept track of our work progress via tools like Trello, but there was no need for extended team management and plannification.
WHAT I LEARNED FROM IT !
This project was a a way to push a little further than the Mario Kart mockup for a few aspects of Unity. We did a lot more GUI for the inventory and spell/attack system as well as the save/load system. Serialization in Unity was also a new thing for me as we had done it ourselves in our custom mini engines before but never in Unity. At some point, we wished we were maybe 3 or 4 to be able to go a bit further and have more complexe results rather than what looks more like a prototype, but we still tried to work on a bit of everything to avoid focusing too much on one aspect, which was, I think, a good thing.
