Too much info

Gosh Friday was an absolute disaster.

Time to do a quick index for the productivity of the day.

When the day started, I tried using the 27 inch iMac that was on our work desk and surprisingly, it worked. (+1)

Since the mac worked it meant that Puvan can finally get started with coding and stuff like that, [his macbook was kinda in repair] so I left Puvan to that.

Before anyone started on their work, we decided to conduct our scrum meeting and I wrote all the things needed to be done by the day on the whiteboard. I felt kind of relieved when the list looked really do-able and so we got to work.

We quickly removed two tasks within the first 20minutes (Logo redesign and Game names) and gosh I was quite happy with our productivity. (+1)

Then hell came.

We got down to nailing our game mechanics for the game we sort of chosen. Legasea(name was just randomly suggested by Puvan :D) was our main problem of the day. I told Puvan to begin on his programming and 2D tutorials so he can start coding once we decided on all the game mechanics. Being gamers ourselves, Nic and I quickly settled many of the game's mechanics. Things were going smoothly when suddenly we talked about the random survivors that we will meet. I suggested 4 personalities (Aggressive, Sly, Patient, Charismatic) that resemble stats and also 4 different classes (Sailor, Fisherman, Pathfinder, Merchant) that have different specializations. Believe me, we did not settle on those names on the fly. We took 2. yes 2 freaking hours just on the names and more importantly their uses and their jobs. By then it was 11am and we had to register our palm for the attendance taking in the future. After the palm registration we decided that we needed a break after the heated discussion between me and Nic. (we were the only ones talking in the whole room P.S sorry about the noise guys)
(it's a major -50 for me at this point)

After lunch, Nic finally sat down and told me he could finally, FINALLY get to his art and visual stuff. I was also kinda relieved too because I can get started on writing everything down and making sure we did not miss anything out. Nic picked up his stylus and I went, "So..." and back to hell we went. This time we talked about mini games that we were going to include in our Legasea game which were fishing,gathering,battling and negotiating.

Fishing took up the least amount of time during our (yes yet another) heated discussion so I'll get to it first.

Fishing was the activity the player can do to gain food units for his crew. The player chooses a fisherman to take part in this activity where the player has to correctly press the order of the arrows in order to land fishes which in turn becomes food for his crew. After we settled on that gameplay, I realized there wasn't really any consequences or even any limit to how much the player can fish during 1 activity so I suggested a number limit which would effectively solve that. However we also thought that we should give the player some form of risk/reward system so Nic suggested that we inform the player when the player chooses to fish over the limit that it MIGHT destroy the fishing rod. After a short while, we were both quite satisfied with that mini game done.

We moved on to the next which was gathering. Before we got into gathering, I decided that we needed to finalize the gameplay screen and what information should we present to the player while he/she was playing. I listed the obvious ones which were the crew size and the food unit. We discussed further about showing food upkeep and stuff like that but it was nothing we can't handle. After that we moved on to the next resource. (Yes Nic wants the resource to be seashells. -.-) I initially suggested wood/lumber which seemed appropriate as they needed it to build or upgrade their current mode of transport. We thought about it for awhile but dismissed the discussion when we realized that the detail right now was not important but the mechanic was. So we left it at lumber and went to gathering(foraging supplies). Nic thought about a game he used to play which we could incorporate as our mini game for this activity. The idea was that the player had to link up multiple objects that are identical and also next to each other. When the link is complete the player will receive a set amount of lumber. (yes after all this I think my scoreboard should be -8923432948923)

I realized that after explaining so much, I have already done a word doc that would explain all the game mechanics. Things are still going as well as I thought. After a much needed saturday rest, our team is ready to spearhead into the basic development stages and get something out tomorrow. (yes we are gonna work our brains out on a sunday. Sounds like a crime to me.) But still, I'm pretty excited about what we have done and what we are going to do in the near future and I can't wait for it. We may not be the best team (yes there are some perfect teams. *cough* T.S *cough*) but I know that we are doing our best.

This post is aptly titled.