Fast Food Tycoon - Sprint 4

In this sprint, I continued my work on creating UI assets. At this point, most of the game assets we needed were made, so we could spend time adding visual feedback and fluff on places that didn’t have them. Most importantly, I started work on making a “recipe book” that would serve as a tutorial book for making the food items.

One of the UI assets I made was the player UI that would show up on the top of the screen. Technically there was one from Sprint 1, but it was very lacking. It only had space for displaying money and what day it was. I refrained from adding anything to it until now because it’s not exactly part of the core gameplay. So this time, I added the day timer a teammate previously made and added a fill on it so we can program the day progressing later. Also, I added a recipe book button so the player could actually go ahead and read it.

I also attempted to make the buy screen look a bit nicer by making sprites for the buttons and the selected info background menu so that they could be used as their backgrounds. If you make the sprites grayscale, you can use the color setting on the image component to change the color instead of coloring the button in Photoshop. I wanted to make the fridge menu look nicer but I got really worried about breaking its functionality, so for now I left it alone. Since another person on the team made it and made it work while doing so, it looks radically different from the buy screen. I’m still not sure how it works fully.

For the recipe book, I made instructions for creating the burger and fries. I tried to use as few words as possible and explain with pictures. I feel like with that, kids would be able to understand it. I added a teeny lil drawing in the corner of the pages to add some style to it. I wanted the recipe book to have the vibe of it being written in. I guess a fast food restaurant doesn’t really need this kind of vibe from the recipe book but we need some more visual fluff, right? You play a budding restaurant owner. Making a burger and fries are relatively simple, so I didn’t have too much trouble with that. I made it in a way that should make it easy to use as a template so hopefully the other teammates can understand it.

Most of the tasks our team has now are programming related, so I will attempt to focus on that next. I decided to leave writing a tutorial to another teammate so I’d be able to work on getting the recipe book to flip through its pages. I will also make some of the UI in the workstations look a little better. The order building station is very barebones, so I should go and make it better. I still don’t feel very confident in my coding skills, so tasks that would probably be one pointers feel like three pointers. It would definitely take a lot more than 3 hours to do something coding related. I really hate when I break stuff in coding because then I’ll need to waste time fixing it. In a previous sprint I tried to make the tabs on the buy screen clickable so you could access the other sections but I ran into a bug and didn’t know how to fix it. I had to make someone else figure it out, and I hate doing that.

Comments

Post a Comment

Popular posts from this blog

Aftershock Simulator - Sprint 16

Image
  On sprint 16 in Aftershock Simulator, I assigned the team 87 points and 51 points were finished. We’re beginning to pick up now that we have a plan on what to do. In this sprint, our team started on the tutorial levels and the objectives system. And of course, there was some extra work to do for the UI in the game as well.   As a producer, I still find it difficult to gauge the difficulty of a task, especially when it comes to programming. I still end up needing to change the point values of some cards because they end up more difficult than expected. For example, I had figured that creating the basis for the objectives system wouldn’t have been too difficult, but not necessarily. A few of the objectives require you to click certain UI elements on the screen, and the things that would “listen” to those UI elements are all each in their own separate scripts, so now there’s the added work of finding them and knowing where to put the code. I always end up asking people if t...
Read more

2D MegaMan Level 2 Feedback (10/27/21)

     Making a late-game type level is incredibly difficult. I had my idea of making the player climb up, but I wasn’t really able to implement that. I couldn’t really think of a layout for a room that wasn’t having the player zigzag up the room. Although, according to my playtesters, what was in the level was pretty good. At least I was able to avoid the “no clear way to the exit” problem I had with my tutorial level. It was a simple “gather the keys to unlock the exit” type level, and unlike my tutorial level, there was actually a point to it.      Players generally praised the way I set up my keys, as you need two keys to unlock the exit, but there are 3 in total. You can get the first key through an easy or hard route, and then you have to get the second key by passing through some enemies. When getting the second key, I put in a weapon deleter that takes out the Nado so you have to jump through a bunch of enemies to get to the top of the room. There’s a...
Read more

Chicken Scramble - Sprint 1

Image
  To start off, this first sprint was kind of disorderly. Since we’re using a completely new project management tool with no prior experience, it took some time to get used to (and still getting used to it). I suppose for my other teammates it wasn’t a big deal but it was an added pound of stress to my shoulders as the producer. To add to that, there was some confusion between me and the designer as to what the whole game idea and aesthetic was. My original idea for the game was a multiplayer maze in which the goal was for two players to compete to get to the other side of the maze. We could have ways for the players to mess around with each other, like using door switches to open and close doors. To clear up the confusion on what we were building, we set up a meeting to talk about it. To prepare, I made a design map of what I thought it should look like. (In the picture, the blue dots are door switches, yellow dots are checkpoints, and the red dot is where the enemy spawns. Bl...
Read more