Rogue poker
(Team, University Project)
Rogue poker
(Team, University Project)
Embedded Files
(Team, University Project)
What is it?
What is it?
Rogue Poker was my second university team project. It was an exploration into mashing the concept of a deck building rogue like with the rules of poker…also with the logic of rock paper scissors thrown in too. It was built for both Windows and Android.
Where is it?
Where is it?
Press kit and Windows and Android build available on game website
What was used?
What was used?
Unity 3D
C#.NET
Blender
Photoshop
Premiere Pro
Rogue poker was my first foray into mobile development of any kind. The concept was another team members, but we all clubbed together to make this concept a reality. It was created for the COMP 3013 module for my undergraduate degree, which along with the creation of this project with a team, it also required the creation of a team site and developer presence.
My role in the team was the project manager responsible for prototyping, sprint and backlog management. Along with this I was also the creator of the website, all the game logos, half of the 3D game assets and all video content.
reflection: prototyping is important
reflection: prototyping is important
One of my core roles on this project was a project manager, focusing on managing and creating tools for the initial prototyping phase.
Due to the complex nature of this project, I decided before even touching a game engine we would instead start with short prototypes that can be iterated upon as development went on. As our concept was so new and strange, I knew that if we dived straight into systems design and programming we would be lost without a sense of the flow and balance of the game.
I first designed and manufactured a paper based prototype based on the initial concept of the game. This used DND dice to indicate the value of the bet placed on each option and lined paper to take down scores, along with some assets I created to indicate what the Dealer entity was deciding.
We played for hours, testing and noting the bounds and problems we found with the flow and balance of the game and designing a rough flow of the game as we went along. This led to further prototypes that heavily informed the logic behind the final product.
Page updated
Google Sites
Report abuse