Archives for the month of: August, 2017

Hey, Welcome to this week’s Kana Quest Devblog where I talk about all the work I’ve done during the week.

So this week has been mostly about getting elements of the second world working ASAP. With PAX Aus fast approaching there are three major things I need to get done before then. First is World 2, second is getting it working on IOS and android and third is putting in some sound.

So most of implementing World 2 is done, the only tasks left on the plate is a tutorial for how to move to World 2, a tutorial for the mystery tile mechanic and finally all the levels. I’m trying to finish working on World 2 by the end of August so I have plenty of time to get the other things on my list done.

So I have two GIFs to show off this week. The first is a lock out screen if the player tries to move to World 2 without meeting the requirements.

World2LockedScreen

The other GIF for this week is a quick demo of how Mystery Kana work. So mystery tiles, cannot be moved and you cannot see the actual Kana. But they will match like normal Kana do. Using that information the player has to figure out what Kana is hiding behind that disguise. In this gif you can see the mystery matches with Ki and Na but not Ko.  This means that the Mystery tile must have the vowel “i” because if it was matching with the consonant Ko would match.  Then since we know that the vowel is “i” when we see Na match we know that the consonant is “n”. Add those sounds together and you get Ni. MysteryTileDemo2.gif

So there are a few things to keep in mind about Mystery Kana. Even if all the Kana match up if there are any Mystery Kana the level will not be complete. Secondly once you figure out the sound of a mystery tile, it will become a normal tile that you can move freely. This is great because it allows more interesting levels. For example you can make levels that are impossible to complete without unmasking all the mystery tiles.  This definitely increases the design space of Mystery Kana a lot.

Anyway that’s the devblog for this week. Hope you have a good weekend, and I’ll see you next week.

Advertisements

Before we get into the meat of this week’s update I just have some big news about Kana Quest. Officially Kana Quest is going to be heading to PAX Aus this year! If you are planning on coming come say hi and give the game a go! I would love to hear your feedback! And if you have any friends going tell them to check Kana Quest out! Anyway with that done, onto the week’s work!

So this week I’ve been working on implementing the second world into Kana Quest. I’ve known for a while that I want to transition between worlds by clicking and dragging the screen. And for the background art to join up seamlessly. So what’s the process of doing this involved?

world2MoreCurrent Step one was making the background art for world two. This was the easy part. All I really needed to watch out for here was to make sure that all the layers are repeatable so I can make the world as long or short as needed.

 

The next step was ensuring that the two worlds can transition into each other. This step will be easier in the future thanks to more planning in the world two art but no such planning was done for the first world’s art. As such the seam is a little abrupt. But its not an immediate shift so its better than nothing.

World1to2

MovingToWorld2

Part three was bringing the assets into unity and getting the camera to move when the player clicked and dragged. One small bug occurred with this though. I made my camera a physics object. Turns out any child object of a physics object loses its ability to know if the player is clicking on it. This caused some of my menus to stop working.

 

World2WithParallax.gif

Once we had the camera moving we had to get the background parallaxing with the camera. This means that the foreground art will move more than the background art to create the illusion of depth. This turned out to be troublesome as I kept being able to make my world two art not line up with the first world art. Thus forcing me to find a way to ensure that the art would always come back to the right position. This took half a day. It was not fun.

So here we have the last part of getting this whole thing working. The transition. This gave me the most trouble out of everything and is what I spent most of this week working on. The reason is for the first world I had used a static overlay that would fade in OVER everything in the scene. This overlay would work fine as long as the overlay was the exact same as the background. But once you add a variable camera position you no longer can guarantee this. So things had to change. So now, what is happening is I have a script that finds all the visible parts of the background, and prevents them from being destroyed when a new scene is loaded, then it moves those objects into the same relative position as they were in the previous scene. This is important as the camera’s position changes scene to scene so if this didn’t happen the art would be misaligned, or not in shot at all. Then would take all other objects in the scene and fade them out. Once the new scene is loaded it would get all the new non-background objects in the scene set the transparency to full and fade the new objects in. The result is what you can see below.

FirstWolrd2Level

 

And that was the process involved in adding the second world to the game. All subsequent worlds will be easier as I won’t have to worry about making the last three steps all over again. It will be set up for me already! Anyway I hope you all enjoyed learning about my process.

Till next week.

Another week another Devblog.

This was an ok week for productivity. Some stuff got done but not as much as I know I can get done (I spent most of Wednesday practically falling asleep). But three big things were done this week!

The first thing is that I have officially started working on Kana Quest’s audio. Well more like the background music for the game. Now when I knew I was going to have pixel art for the visuals of Kana Quest I knew that chip tunes were going to be used for the music. So this week I did my research of what were the best programs for making chip tunes and landed on FamiTracker (the visual fustercluck you see below). Then I spent a little bit figuring out how to use the thing. Thankfully there were some really well made tutorials on youtube that sped up the process. Now that I’m used to the software its not so bad to work with. Although if you look below you can see that I kinda ended up with a piece of music which has 5 frames to a crotchet for some reason. This is great if I want to you know have quavers (sarcasm). Regardless, progress on the theme song for Kana Quest is progressing nicely.FamitrackerScreenshot.png

The second major achievement for this week was the implementation of an options screen. Last week I talked about how the player can now switch between Hiragana and Katakana. The options screen is how the player is going to do that, so it is pretty important that I get the options screen working. I haven’t got all the controls on it working yet but we will get there soon enough. At the very least its really nice not to have one grayed out button on my main menu screen.Options Screen Demo

Finally, saving the best till last, we finally have world 2 implemented into the game! So the way you get to the world 2 is by click and drag the screen to move over. I’ve put a ridgidbody2D onto the camera so that when the player lets go of the camera will continue moving for a moment. It just feels a nicer to do doing it this way. Another thing to notice is that the menu button changes color when we move to world 2. One of the things that is a big part of making the art for a new world is making sure the colors of the UI matches the new setting. So, although you can’t see the extent of this in the gif below, a large part of putting this into the game was recoloring all the UI. One last small detail in this gif is the title screen. I’ve changed the image used for the stars in the background. I’m much happier with where they are now and the new stars look great!MovingToWorld2.gif

Anyway. That’s all the major and interesting stuff I got done this week. I’ll see you next week where hopefully we will be able to show off some levels for the second world! Until then, take care.

So this week had one task. One job that had to be done. It was long, it was boring, it was tedious. It was implementing Katakana into Kana Quest.

Why is implementing Katakana such a chore I hear some of you wonder. Well simply because implementing each Katakana has a bunch of steps that are not at all interesting and when you times those steps by 46 (the number of kana) things get very boring very quickly.

So the pipeline is as follows.

  1. Create the sprites. (We talked about this last week as I was most of the way through making the Katakana Sprites at that point.)
  2. Set the image setting for each sprite.
    1. This isn’t too bad what I have to do is tell unity how it should process each sprite. How big the image is (pixels per unit), its filter type (point filter as bi-linear and tri-linear make pixel art look awful) and if its a single or multiple sprite image. Now all of the above I can do all in one go by selecting all the files at once, but below I have to do one by one, because Unity wont allow me to do this in batch. Finally I have to set the sprite size for multiple sprite Kana. So for each Katakana I had to go into the sprite editor and tell it to divide my sprite sheet how I wanted it divided.
  3. For each kana make an animation using the unity animation system.
    1. For the stone tiles this is easy. They are just one frame so its just a matter of dragging and dropping the image into a new animation. For the normal tiles this takes a while longer because I have to copy the animations seen on the Hiragana Tiles. But the big annoying part of this step is that I have a LOT of animations on the one object now. So much so that they don’t all fit on screen so adding a new animation took about three seconds of scrolling down the animation list before I could get to the “make new animation” button.
  4. Add those animations to the animator of the tile object, and then set up the logic of when to play those animations.
    1. So putting the animations into the animator is easy. Select all the files you want and drag them onto the animation screen. Setting up the logic has to be done one by one and is really tedious. Right click from where you want the tile to transition from and to (from all to each individual animation in this case). Then click the arrow that comes up and create the parameters controlling the animation. In this case, what is the tile’s hiragana number? Is Katakana enabled? And is this a stone tile or a normal tile. Rinse and repeat 92 times.
  5. The last step is to add a control for turning Katakana off and on. This was the last and easiest step. Now if the player presses ctrl+shift+k in game katakana will be toggled on and off.

And that’s the process. Since you got through all the technical stuff your reward is some gifs! Enjoy!KatakanaDemo

SoneKatakana