Archives for posts with tag: GUI

Hi Welcome to the Dev Blog for Kana Quest. If you’re new here and have never seen or heard of Kana Quest, read this blog post for the Who, What, When, Where, and Why of Kana Quest. –> https://kipentheodor.wordpress.com/2017/09/09/kana-quest-primer/

Otherwise read on to hear about what’s been done over the last week!

So I have one and a half months till PAX Aus hits. And I am officially freaking out. There is so much to do and so little time for me to do it. I still have to get Kana Quest onto Steam so I can take preorders at PAX. I still have to implement some sound into the game. I still have to organize my booth’s set up. There are still some bugs that need to be ironed out. I need to make an awesome trailer to show off my game. And finally the one thing that has me worried most of all, my tutorial is still awful.

The tutorial has always Kana Quest’s biggest weakness. I tried to sit down this week and think about all the common misconceptions people have when they sit down and play.

  • They think they are writing words.
  • They think Hiragana is Kanji and start freaking out they don’t know the meaning of each letter.
  • They don’t understand they are trying to match sounds.
  • They don’t understand the win state.

So how am I going to prevent the player from thinking these things?

I

Don’t

Know

That’s it. The reality is I’m just not sure. But I cannot afford to give up. So here are some ideas I have that hopefully will help fix the problem.

Idea 1. Completion Gauge: So most people when playing are not sure what their goal is. If I give a visual representation of how close the level is to being completed it will better communicate the goal. I think it will help players know how close they are to completing a level, but not necessarily understand why they are completing the level.  CompletionGauge2.gif

As you can see I have already started work on this idea, mainly because I think this is my best one. To get this working though I have had to change how I handle checking whether or not the level is complete. Now the game will find the largest group of Kana in the level. Before the game would only actually check the group size starting from one location. I had to change this as if that starting location was the last to be connected it would be very easy to have a situation where the gauge goes from zero to full which would only confuse player further.

Idea 2. Show the Player the Hiragana Table: So the idea here is to show the player the whole Hiragana table after they learn their first three Kana. Hopefully this will demonstrate to the player that Kana are phonetic letters and not Kanji (which are pictorial). The other great advantage of doing this is I prepare the player for all the characters that they will learn. That way they don’t freak out that they are going to have HUNDREDS of Kana to memorize. HiraganaTableGif.gif

Idea 3. Show the English Sounds Matching in Tutorial Levels: The idea behind this one is that the player doesn’t get to see where things are matching. While this is a core part of the gameplay later on, for the tutorial the most important thing is that the player understands the core mechanic. If showing the English for a little bit will achieve this I’ll try it!

Idea 4. Change the Structure of Tutorial Levels: So the idea here is that I increase the size of the early levels but not increase the difficulty. What I’m thinking is a really long level with the same Kana repeating but with stone Kana to limit movement. Coupled with the completion gauge hopefully this will communicate the idea that creating matches is the goal.

So those are my ideas on how to improve the tutorial. They aren’t perfect so if you have any ideas, PLEASE TELL MEEEE! I’ll see you all in a week’s time where hopefully I haven’t turned into a stressed out wreck.

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 has been a rough week for Kana Quest. This has mainly been because my grandfather’s health has deteriorated quite significantly so my mind has been elsewhere. But hey somethings did get done so without further ado here’s what I got done.

First thing I got done was I have fully implemented a medal system into Kana Quest. This allows the player to choose their own difficulty. A gold medal will be earned by completing a level in the minimum number of moves. A silver medal will be earned by completing the level within two or three moves beyond the minimum. And bronze medals are earned for completing the level in any amount of moves.

KanaQuestMedalMedu

Seen below is a demonstration of the player losing the medal they earn based on how many moves they use.

MedalDemo

finishedlevelThis is a wip of the gui that will appear once the level is complete. I like the cool rainbow next level button but I’ve gotten a bunch of feedback that it doesn’t fit with the art style. A variant of this gui will appear depending on the medal the player earns.

 

 

 

The last thing that I achieved was debugging the new movement script from last week. I’ve gotten rid of a lot of the main bugs that were plaguing that script but now things are much more stable. There is still some bugs in there but I have had a much harder time replicating those bugs so they remain in until I can consistently trigger those bugs to get rid of them.

Anyway hope you all have a good weekend. I’ll see you next week.