Ryan Crim, Week 8 Journal PPJ, Blog post 8, GMAP 378

Content with Hours (Examples included):

Getting closer to the end of this project, my main focus this week was to clean up different aspects of the game structure and my individual games, as well as implement a new one if I got the chance.

To begin the week, I tried to make the game more uniform by adding the pink bar of pre-game instructions I had in my mini/micro-games into each of the others as shown in Figure 1. This required modifying the timer and stateholder scripts to consider when a game actually “starts” (instruction bar disappears) as well as updating the scripts for each game to consider this new logic. Furthermore, there was the issue of the low amount of points the game awarded from playtesting, so I centralized and increased the point values and updated all the game scripts to use these variables so that the point values can be easily modified. Lastly, in terms of structure, I noticed that when I updated the transition screen to compare the scores from the last game to decide what music should play (as part of my score changes from the last build), I accidentally had the updating of previous scores in an if-block so it did not update every time as it should and does now. (2.50 hrs)

Figure 1. Screenshot of pre-game instruction bar in existing Runnerz game

Moving on, I made a few additions and updates to my each of my existing games listed below...

• Abducktion (0.25 hr) 
• Added sound effects for X-ray and cup swap (whoosh) 
• Draw at Noon (2.00 hrs) 
• Created an animation controller and added/modified scripts to handle animating the alien as shown in Figure 2 
• Modified motion of human knockback to coincide with the alien’s as well as to keep the camera on the animating alien 
• Fixed issue where alien would shoot itself after Ricardo shortened the transitions 
• G-Switch (0.25 hr) 
• Slowed spinner speed to make it easier for aliens to affect the game 
• Added sound effect for jump to make it easier for Human 2 to know when to switch gravity 
• Dance Off (0.50 hr) 
• Modified motions of player object and added slight motions to camera to try to get more consistent motion and feedback

Figure 2. Animating alien model in Draw at Noon

After modifying my existing games, I had a bit of time to create a game based off of the Whac-A-Mole arcade machine (cleverly called Whack-An-Alien) as shown in Figure 3. Just like the real machine, moles (or aliens in this case) randomly pop up out of the nine holes. The humans need to position the hammer over the corresponding hole (by holding in the correct direction(s)) and slam it down on the alien in order to get points (see the screenshot for controls). After a short time of not being hit by the hammer, though, the alien will retract into its hole and the aliens will be awarded points. Aliens continue to pop up randomly until time runs out. The work for this game consisted of building the scene up with all of the assets (including modelling a simple Whac-A-Mole-esque machine in Maya), writing the two scripts to handle the moles and the hammer, and retrieving the background music for it (http://www.playonloop.com/2016-music-loops/dolphin-ride/). (3.50 hrs)

Figure 3. Screenshot from Whack-An-Alien micro-game

Lastly, since we are nearing the end of the project, we were required to watch a post-mortem presentation from the GDCVault in order to familiarize ourselves with the mindset we should have in thinking about how the project went well and how it could have gone better. After watching parts of a few different presentations, I finally settled on watching Chris Harvey’s “Learning From Our Mistakes: A Post-Mortem of Guacamelee!” all the while taking notes. Below you can find my summary of these notes. (1.75 hrs)

As a co-founder of DrinkBox Studios, Chris had a prime viewpoint to see how the process of creating their first game, About a Blob, compared to their process for creating their much more successful third game, Guacamelee, and thereby outlined what changed to bring this success. Within this presentation, Chris split the process into three main stages: Concepting, Development and Marketing.

In the Concepting stage, there were a few different aspects that needed to be considered, including choosing a concept, defining the game and finding the fun. In terms of choosing a concept, they changed up their process by having members of the studio in all different departments meet and create single page pitch sheets outlining a game idea complete with genre, platform, target audience, story and mechanics. Therefore, they could select the game idea that the consensus enjoyed and refine the selected idea with pieces from other pitches to make it even better. Moving on to defining the game, DrinkBox refused to enter production until they understood and nailed down the basics of the game and had as few loose ends as possible. That way the team could stay focused and synchronized meaning that time would not be wasted later on second guessing decisions. Lastly, in terms of Concepting, Chris mentioned that in order to find the fun while keeping consistency, the fundamentals of the game should be conservative and individual elements should instead be riffed on. There is no need to reinvent the wheel for every aspect of your game, and it is better to have existing similar games to see what works and what does not, since that could end up wasting a lot of valuable time in the process.

In the Development stage, there were also multiple aspects that needed to be considered, including pre-production, deadlines, personality and charm, toolset and target platform. Starting with pre-production, Chris mentioned the importance of having a small, dedicated team (from different disciplines) with clear goals and roles to get the process rolling and keep it focused. He also stressed that the leads of the project should not be working externally or this focus could easily be thrown off resulting in rebooting and second guessing. Lastly, he mentioned the importance of keeping constant discussion and to work on small pieces at a time instead of trying to create the whole game at once. This led directly into the idea of setting incremental deadlines with small and obtainable goals. On this front, Chris also noted the effectiveness at making the deadlines external to publishers/the public, since it would put pressure on the team to actually get it done, allow the team to see what each person is capable of and to identify what in the project is not as important as originally thought. Despite having deadlines, though, the DrinkBox team found the importance of switching to the mindset of saying “yes” to more of the team’s ideas so their personality could define it. Therefore, they would have team meetings to see in-progress work from all departments and accept feedback/suggestions as well as encouraged experimenting, which created a more positive atmosphere and revealed unexpected talents from individuals on the team. In addition to being more open and creative, the team realized the importance of making the development faster, easier and more efficient in any way they could. Therefore, when they found a deficiency or an iteration process to be slow, they made modifications to the process to improve the situation, such as creating a programmer-driven, artist tunable system to create visual effects instead of relying as heavily on the artists. Lastly, in terms of determining the target platform and the release process, Chris said they had basically no change in the result (still self-published), but they did change their attitude to question presumptions and to put proper thought into it before making a decision.

Moving onto the last part of the process, Marketing, Chris laid out the importance of making the game as visible as possible through the game reveal, public relations and the launch. Starting with the game reveal, DrinkBox was initially scared to show About a Blob early due to changes possibly confusing people and the belief that showing a game not polished enough would ruin the reputation of their game, however, this resulted in a lack of anticipation for the game. For Guacamelee, though, they took the opposite approach and announced the game just out of pre-production with an announcement trailer that was not perfect, but it still built excitement. Furthermore, they showed the game off as early and often as possible anywhere they could. This lead to them to continuously work with a PR firm to help with the marketing side. Chris mentioned that there was not much media coverage for About a Blob since they were trying to do it themselves and put it off until the end. Considering marketing is a huge part of selling a game, it makes much more sense to hire people who know what they are doing, instead of trying to figure out it out yourself and wasting time that could be spent on the game. Lastly, Chris discussed the importance of planning and taking the launch extremely seriously, including a press tour, reviews and store placement/timing.

Overall, Chris started out the presentation sounding a little nervous, but I think he definitely warmed up throughout it. The information provided and the idea to compare the process of creating a successful game to one that was not so successful really helped drive home the points he wanted to make. This presentation definitely brought a different set of ideas that I never really considered and I plan on putting more thought into the process next time I work on a game.

Content Positive:

- Implemented a bit more uniformity with pre-game instructions and centralizing point values

- Added to and fixed up various parts of my four existing games (including alien animations in Draw at Noon)

- Created Whack-An-Alien micro-game

- Watched a very interesting and helpful post-mortem presentation

Content Negative:

- N/A

Total Hours for the week: 10.75 hrs

Ryan Crim, Week 7 Journal PPJ, Blog post 7, GMAP 378

Content with Hours (Examples included):

My main task for this week was to update the scoring in the game to make it more visual to players without requiring a lot of time to look at it. To do this, as a team we decided to split up the score in two different scores (one score for the humans and another score for the aliens), so that we could implement a tug-of-war style score bar. The way that it works is that depending on the difference in scores between the two teams, the bar fills with more of the winning team’s color as shown in Figure 1. In addition to implementing the score bar prefab to add to each game, I also updated the Score and ScoreChange scripts to properly work with the new scoring system as well as went through the scripts for each individual game and reworked them to handle the new system and to add points for humans/aliens accordingly. After this extensive reworking of the games, I went through and tested each one to make sure that all of the updates work as expected. Furthermore, I updated the High Score scene to properly display each team’s final score and to show the top three high scores for both the aliens and the humans as shown in Figure 2. I also noticed that the scores were not being saved anywhere as well, so I updated the high score script to load from and save to XML files for each team’s high scores. (5.50 hrs)

Figure 1. In-game score bar showing change after a win for the humans

 

Figure 2. High score screen showing scores for both teams

After working on the scoring, I had a bit of time to flesh out a quick idea that came up to implement a DDR-style micro-game. The main gist of the game is that the screen is split into two with the aliens on the left and the humans on the right as shown in Figure 3. “Notes” are spawned in the center of the screen and move toward each team’s input area. If the player inputs the correct direction (see screenshot for controls) when the note is over top of the corresponding input area, the team is awarded +2 points and the note sparks a bit (seen by the green note on the alien’s side). If the wrong input is entered, the input is entered too early/late or the note reaches the edge of the screen, the note fades away and no points are awarded (seen by the rightmost red note on the human’s side). The notes continue to spawn until there is no time left. In terms of the work required for this, it involved writing each of the scripts, building up the scene with all of the necessary art assets and retrieving the current background music (http://www.playonloop.com/2010-music-loops/95/). In order to make the work a bit easier, I salvaged bits and pieces of the code from each of my other games, those being Abducktion, Draw at Noon and G-Switch. Some of the repurposed code included the analog input logic from Abducktion and the object rotation from Draw at Noon/G-Switch. (5.00 hrs)

 

Figure 3. Screenshot from Dance Off micro-game

Lastly, I made a couple of modifications to Draw at Noon. The first of which was adding in the textured alien model that was being worked on the past few weeks. The issue at this point, though, is that the current model does not have any rigging or animation as I believe it is still be worked on. Therefore, as you can see in Figure 4, the t-posed alien looks out of place, however, it does look better than the existing 2D placeholder. In addition, I made a couple of slight changes to how the bullet works, including updating its speed, starting it exactly in the barrel and changing the color of depending on who shot it (pink for humans, green for aliens). (0.50 hr)

 

Figure 4. Screenshot of Draw at Noon with textured alien model

Content Positive:
- Reworked the scoring to be split between the two teams to create more competition
- Added visual score bar prefab to each game to make it easier to tell who is winning
- Updated High Scores to show saved scores for both teams
- Added Dance Off micro-game
- Added textured alien model to Draw at Noon
- Modified bullet behavior to improve it slightly

Content Negative:
- Still waiting to see if the rigged/animated alien model happens

Total Hours for the week: 11.00 hrs

David Monteleone, Week 7 Journal PPJ, Blog post 4

Content with Hours (Examples included):

This week involved a large update to Alien Arcade with plenty of work from myself.

First I had to implement a transition scene for each mini game to move to when it ended. Now when each mini game ends it loads the transition and the next mini game. The game now acts as a seamless fluid piece.

(3 hrs)

I added in music to fit each mini game along with art for the menus and transition scenes. I then added scoring that persists throughout the duration of the game. Now when players score in each game it adds into a cumulative total. I added a high score screen at the end of the game that tells the players how well they did altogether. The new main menu can be seen below with the art from Angela:

(3 hrs)

From the input given from the group, I decided that Slapz should be converted into a new mini game called Runnerz. This new game takes the platforming concept from Slapz and makes the game entirely about jumping and moving about a platform world. The base grey box mini game was added to the build and can be accessed from using the blank panel on the main menu on the far left.

(3 hrs)

Last, I attempted to fix the Drexel Ride scene transition bug. The ride will break when the object talking to the motion base is destroyed. Thus, we implemented scene transitions that do not destroy the object. Our first implementation only worked for Stello Says and jumping back and forth to the main menu and Stello. Besides that the transition scene broke it. This will be my main priority next week. Our attempt to fix the Drexel Ride bug is the snippet of code below, sadly it didn’t completely work:

(3 hrs)
       
        GameObject myObj = GameObject.Find("TransformWrapper");

        myObj.transform.parent = null;

        DontDestroyOnLoad oldDont = myObj.GetComponent<DontDestroyOnLoad>();

        Destroy(oldDont);

        myObj.AddComponent<DontDestroyOnLoad>();

Content Positive (Duplicate hours from above):

-          Mini games now transition from game to game. (3 hrs)
-          Music, Scoring, and High Scores are in the game. (3 hrs)
-          A new mini game called Runnerz has been added and is a grey box. (3 hrs)

Content Negative

-          The Drexel Ride scene switch bug continues to be an issue. (3 hrs)

Total Hours for the week: 12 hrs

Tags: Music, Scoring, High Scores, Transitions, Runnerz, Drexel Ride bug, PPJ