Hoi! This is Leina, aka Reina (@rein_bel), because in the wonderful world of Hiragana we have a kana (れ) that does both. I am one of the two composers for Kana Quest.

Though I don’t come from a strictly musical background like Julian, I am a native Japanese speaker who grew up in Japan, listening to the kind of traditional and modern music  that inspires Kana Quest’s soundtrack. 

w5wip.png

What makes a song ‘Japanese’? (And how do we stop being stereotypical?)

Let’s talk about Enka. 

Enka is a type of Japanese ballad music. Modern enka developed in postwar Japan, and enjoyed a revival in the 70s that still continues to this day. Enka is characterised by its sentimental lyrics, use of traditional musical scales, and slow rhythm – often a single syllable can stretch for several notes!

https://www.youtube.com/watch?v=wwKIvbOqqcc

(This is the singer Sachiko Kobayashi performing Enka. Remember her now.) 

Most people’s image of Japanese music may default to traditional Japanese folk music. Koto glissandos, taiko drums, that sort of thing. Have you heard of ‘Sakura Sakura’? It’s a well-known folk song that’s been popular since the Meiji period, and most kids are taught it at some point in their lives. 

712px-Sakura.song

The song is in In scale, a musical scale used in Koto and Shamisen music. Coupled with the song literally being about cherry blossoms, it’s about as Japanese-y as you can get.

Then there’s also everyone’s favourite J-pop and J-rock, which evolved from the global 1960s pop and rock music phenomenon. The Beatles were explosively popular in Japan as they were everywhere else, and J-rock evolved from these influences well into the 70s, 80s, 90s and today. Nowadays Jpop is well-known for its peppy, upbeat energy and their prevalence in anime productions and pop culture. 

So what does this have to do with Enka

During the earlier stages of this project, Theo and I joked that most pop-culture depictions of Japan fell into two camps: ‘Samurai Drama’ and ‘Anime Girls’. Both of us had spent long periods of time living in Japan, and wanted to showcase the other facets of the culture that folks might not be as familiar with. Enka, with its roots in traditional Japanese music and western ballad music, is a perfect example of how modern music evolved into something distinctly recognisable to locals… but might not be as widely known elsewhere. 

W3Done

Japanese Instruments

Two instruments I used frequently in Kana Quest’s soundtrack are the Shamisen and Shakuhachi

The Shamisen is a three-stringed instrument that originated in China via Okinawa. In particular, the Tsugaru Shamisen style is known for its percussive quality. Depending on how the strings are plucked with the Bachi (plectrum), different tones can be produced. A hard downwards pluck creates a distinctive snap or twanging sound, which often becomes the rhythmic backbone of Shamisen solos. A gentle up stroke produces a clean, almost Koto-like tone. 

https://drive.google.com/file/d/1EnwMv7fNOoZlkcEd_wOzQ5E4Dr6Pu0uz/view?usp=sharing

The Shakuhachi is a bamboo flute known for its variable tone and breathy sound quality. In Japan, it’s known as an instrument played by Zen Buddhists as part of their meditation. 

https://drive.google.com/open?id=133Cyrif5SxGdHEptwCJM4hcNCY4DIWf0

 

Production Process

As mentioned by Julian in the previous dev blog update, both of us have a hand in every track. For some of the earlier levels, Julian writes the backing track and sends it over to me. I then write the melody, and send it back for the final mix. On other tracks, the reverse is true– I write the majority of the track, but leave the keyboard and mixing to Julian’s mastery. 

With so much back and forth between our two vastly different workflows and composing styles, it seemed like a bit of a risk jumping into the project– but it’s been anything but, and the final tracks are a beautiful fusion of traditional and modern that we’ve been looking for. 

world11WIP.png

Conclusion

Now we’re seeing popularity in Japanese folk rock songs that reintroduce traditional Japanese instruments to modern music. Wagakki Band incorporate Shamisen, Shakuhachi and Wadaiko to their songs, and they came into the spotlight in the 2010’s through the power of the internet. Various independent Vocaloid producers have also begun using traditional Japanese instruments in their songs.

…Which brings us back to Sachiko Kobayashi, the Enka singer. 

Here’s her performing a cover of the popular Vocaloid song ‘Senbonzakura’, in a virtual live performance in the popular MMO Phantasy Star Online 2. 

https://www.youtube.com/watch?v=zyf7LvXOT4Y

Because “Folk-ballad singer wearing a mech suit in a virtual sci-fi MMO covers a folk J-rock song originally sung by a fictional anime android as cherry blossom petals swirl on stage” is something you really, really can only get in Japan. 

 

Hi all, Theo here. Please give a big hand to Julian and Leina for writing the last two devblogs! I’ll be writing the the next devblog as usual, but I hope you all enjoyed reading Julian and Leina’s work as a change of pace.

However on the topic of the next Devblog, it will come out a week later that usual as the weekend the next devblog would come out the weekend of PAX Aus. Which, Kana Quest will be showing at this year!! So expect the next devblog on the 19th of October, not the 12th. But until then, have a great month. And if you want to read the devblog as soon as it comes out feel free to sign up to our mailing list at kanaquestgame.com

Advertisements

Good morning everyone! This month’s blog is a little sideways turn from our usual venture… written by Julian AKA ‘Zorsy’, one of the composers for Kana Quest. This is so Theo gets a good rest, and so he can tell us more exciting developments behind the scenes hehe. 

It’s been an amazing venture so far being contributing to some of the music for the game alongside the talented Leina https://twitter.com/rein_bel

One very fun challenge composing for the game has definitely been realising the worlds that Theo has created through various forms of traditional music. We’ve swayed through Enka, Ghibli, to more recent JPop. All of which have provided their own unique challenges in relation to soundscapes, samples and the cohesion between traditional Japanese genres, a chip-tune canvas and the individual flares of both myself and Leina! 

I think embarking on the project, neither of us were quite sure where we would end up, but with the majority of the music completed by the time of writing, i’m definitely quite happy with where we’ve ended up! I’ve written a list of some of the more fulfilling challenges to overcome.

 

Background Research

Coming in fairly recently to the project, It’s been awesome to be part of Theo’s vision, as the idea of utilising the tutelage of hiragana/katakana within a Bejewelled Puzzler type of game really appealed to me as i loved problem solving games and am currently studying Japanese myself (Which reminds me after this blog…). However that did involve a lot of research into the game and world that was to be created, and I often found myself delving into some older Japanese styles that I hadn’t been quite familiar with: 

https://www.youtube.com/watch?v=nvvXOfLs-ng

Here was one of the examples of styles Theo was looking at. Whilst the musical brain within me was quite familiar with harmonies and melodies and the ability to recreate them on the piano, I was not initially familiar with traditional Japanese instruments such as the Shamisen/Koto/Shakuhachi at least from the angle of a composer to utilise them! Early on me and Leina had decided that more of these traditional sounds might best be best approached by her, especially for intricate articulations. Here’s an example of some of Leina’s beautiful music: 

Within this challenge, I think there have been many instances where I’ve been faced with a problem such as “this chip-tune element sounds too out of place amongst the traditional instruments” or “how do i make that percussion sound not too aggressive?” as well as “how do I make that percussion sound more aggressive” and the next thing you know, some of the most simple of tasks takes a very long time or the complete opposite! 

Some of my favourite contributions to the soundtrack so far have definitely involved a very large track listing, so one of the best skills I’ve picked up so far has been efficiency in how you layout your workflow!

https://www.instagram.com/p/Bz_vC9JBiM0/?utm_source=ig_web_copy_link

 

Cohesion

We’ve taken a progressive approach to the soundtrack in which the worlds take a (for the most part) chronological approach to it’s production. So we start from Traditional and Enka music, to eventual heavier more AMV OP Japanese Pop music. Whilst throughout every piece will always feature touches from both composers, you can see the early part of the soundtrack composed by Leina, which morphs into a more modern production style composed by me! It’s been really great to see how our styles have all matched with future stages adopting little callbacks to traditional Japanese instrumentation but retaining it’s energy receptive to the world it accompanies. 

WORLD 9 Music

https://www.instagram.com/p/B0SEOodgPqg/

I think where we are now, one of the amazing parts of how it’s been composed is that you can hear both of our styles fusing together, and in fact I’ve definitely learnt a lot from having Leina next to me composing on the game! 

Mobile Composing

This applies to all of us to some degree, but I know one of the biggest challenges especially on my behalf has been composing whilst travelling! Upon starting this soundtrack, I was in Japan myself, but travelling for the majority of May – July definitely was a challenge! As a methodology, most of the time I compose with a piano, and write on the piano, but there were many instances where I’ve written by singing/by hand/by computer or if luggage permits me, travelling with this miniature buddy of mine:

https://www.instagram.com/p/Bz9cCk_ABsh/?utm_source=ig_web_copy_link

Based on methodologies prior to taking on the project, this has been a very enlightening endeavour limiting myself to barely working from my nicer studio back home! Whilst majority of the mixing is still done on my speakers back home, it’s been really inspiring writing whilst i’m on the go, and I do believe some of what I’ve been able to conjure wasn’t possible whilst being in Australia. Creating limitations has always allowed me to grow in another area, and so far I’ve composed from the comfort (or discomfort) of:

  • A couple of friends houses
  • On the plane
  • On the train
  • In my hostel
  • In my bed
  • In my Capsule hotel even. (yes don’t tell Theo) 

*Theo here, Julian. You know I read this right :P* 

There’s still some music left to go, and whilst on my end the composing side of the music making is very close to done, it’s awesome hearing the whole soundtrack come together as well as hearing it get pieced together is a really satisfying experience! 

Time to study Japanese… with Kana Quest… 

 

*Theo here again, please give a warm thanks to Julian for this month’s Kana Quest devblog, by following him on twitter – https://twitter.com/ZorsySan and instagram – https://www.instagram.com/zorsysan/ .

Next month we are going to have Leina in and talk us through some of the finer points of working with traditional Japanese elements.

If you are interested in following Kana Quest feel free to sign up to the mailing list at kanaquestgame.com 

Until next time, take care and have a wonderful month*

Good morning all, welcome to another edition of the Kana Quest devblog. Now last time I said we would have a blog written by the composers to talk about their process. As they are still working hard on making all the music right now we are going to postpone that one for an upcoming month. But is still happening.

And one more bit of news… Kana Quest will be coming to PAX Aus this year!!! So if you’ve been wanting to give the game a go, come on down, say hi, play the game, and find a handful of bugs as I freak out that there are still bugs in this thing. It shall be a swell time.

Now, onto this month’s topic…

Top 5 Dumbest Things That Theo Coded/Implemented Into Kana Quest.

So I was talking to my programmer Reuben this week and we got chatting about some of the frankly stupid things I’ve programmed since I started Kana Quest. And to be honest, most of these things are funny. So for the sake of entertainment, I am going to curate the finest pieces of coding idiocy my brain has produced. And hopefully this will explain to my relatives what I mean when I say that Game Designer is not a Programmer.

5. Stupid As Hell Names

So this one is relatively harmless on the “Theo, oh god what were you thinking” scale. It just meant that every now and again I would get a bewildered Reuben going “Theooooo, what does _______ do”. So lets look at some of the stupidest names for variables or function names that exist in Kana Quest shall we?

DumbCodingPart1

Because nothing says “Always give your variables descriptive names” like asdf.

I mean who hasn’t had been in a situation where they are too lazy to come up with a proper name for something. And this function is a pretty minor one so who cares riiight?

DumbCodingPart2

I mean at least this time the silly name explains what the script does… it moves shit… and it checks if shit has been moved. Simple. I can’t see any problems with the documentation here what so ever. Except for… you know… what is the actual shit is this script is moving.

DumbCodingPart3

This script is a completely different script from the last one

In a similar vein… “heyLookAtThisShitImHolding4U” is just flawlessly named. It perfectly sums up what the script does. It sits there holding level button data and doesn’t do anything else whatsoever. 10/10 flawless coding.

DumbCodingPart4

Unlike the previous scripts, if you got rid of this one you would get horrible visual glitches. Lot of pressure to place on monkeys, but they do the job.

Fun fact, if you have infinite monkeys sitting at infinite computers running Unity, they will eventually end up with an exact copy of Kana Quest. Really puts my coding ability into perspective.

DumbCodingPart5

And now we reach the pinnacle of both comedy and stupid names… Star Wars puns. 

The name here isn’t the funniest thing. Its the conversation with myself that happened afterwards in the comments. I forgot multiple times that I had written this stuff and each time I’d add another comment. I can’t really add any more on because I remember that I wrote all of this now, but its a fun little bit of stupidity. And it makes a good closing point on the category of dumb names.

4. The Hierarchy of the Parallax Objects.

So for those of you who have never used Unity or Unreal Engine. Every level (the technical name is a scene in Unity) has a hierarchy of all the objects within it. A normal person’s hierarchy might look something like this.DumbCodingPart6

See that window to the left? That’s this level’s hierarchy. Each object on that list is an object in the level. And if there is an arrow next to the object it means there are objects attached to it (the technical term is the object has children). This is what you are supposed to do. This way you don’t have to scroll down a massive list every time you want to change something. So you would think, that because I did it correctly here, in one of the levels, I would have done it consistently correctly across the whole game…

Ha no.

See in the level select screen, the background parallaxes. What that means is that the 2D images in the foreground move faster than the background images. This creates the illusion of depth. And it allows me to make pretty gifs like this.

World8-9Transition

So what does this have to do with the hierarchy? Well because of the silly way that I coded the parallax system. It can’t handle having objects having children like shown above. So now the level select scene’s hierarchy looks like this.DumbCodingPart7.gif

The eagle eyed amongst you can notice that there are some objects that do have children in this hierarchy. That’s because some objects are ok for me to give children, while there are others that is isn’t ok. The line is if I don’t want to be able to move the child objects with the parallaxer. Doesn’t excuse the stupidity of doing it this way but at least I get to turn it into that sweet #content.

3. The Way Movement of Kana Coded.

Hey Kids! Do you like repeating the same bit of very long complex code 4 times with with very small and minor variations that are very easy to miss? Then you would have LOVED the way I had originally coded Kana Movement. Unfortunately (fortunately) I can’t show you what this one looks like as Reuben mercifully has fixed it to function in a much better way.

See the problem was when I first coded the movement I didn’t know about all your highfalutin coding terms like *structs* and *enums*. So the way I tracked the direction the player was moving was with an integer value. And it would run four different versions of *THE SAME CODE* four different times just gated off with if statements to get the effect that I wanted. It worked, and according to Reuben my logic within that chunk of code wasn’t even that bad. But it did mean that it would take me 4 times as long to add in a new mechanic or edit the movement code as I had to repeat all the changes I made to one part of it an additional three times. One of the first things Reuben did when he got the job of programming was changing this.

DumbCodingPart8

What I should have done in the beginning

When Reuben finished cleaning this up, he was able to delete a whole 2000 lines of code. And adding in new mechanics became infinitely easier as a result. Good times.

*somewhere Reuben’s eye starts twitching*

2. All The undo Function Information.

On a running theme of not knowing how structs work when I made it the undo function. See there is only one thing more complicated that moving Kana in this game: Undoing Kana. See the problem is that when I first made the undo function I decided that rather than swapping the game objects back to their original positions I decided that I would just swap all the data held on the objects that got moved.

This was fine when there were no strange and unusual mechanics. But the moment I started adding new mechanics I had to start adding new variables to track if one of the objects was one of these new mechanics. This would have been ok… if I tied all those variables together under one struct, it would have been fine. Also for those who don’t know what a struct is. Basically you get to determine the boundaries of a new variable type. And because of this you can make an array or list of that new variable type. This is important is it would allow me when making the undo function to ensure that the many different undo variables don’t get out of position. But that’s not what I did. So instead we have a tangled mess of a metric fucktonne of different list variables that we just have to hope and prey don’t get out of position and work as they are supposed to. Reuben took one look at this script and just said “nope” and decided he wouldn’t refactor the system.

DumbCodingPart10

You can see Reuben’s opinion of this system in the comments up the top

DumbCodingPart9

And these are all the other variables being used to manage the undo function. 

And you might have noticed if you were paying attention, that there is a variable in there called “movementType”, with the comment “//0 is up, 1 is down, 2 is left, 3 is right”. That does mean exactly what you think it means. The issue that I told you about as the number 3 dumbest thing that I coded into Kana Quest… it is present in the undo function. And because the undo function is such a mess, it never got cleaned up.

DumbCodingPart11.gif

Everything is fine. Say it with me now, EVERYTHING IS FINE

 

1. The Animation System

And here we have, the biggest, baddest most horrible monstrosity my sick, twisted mind thought was a good idea at one point. The animation system. “Why is the animation system such a problem? Surely your game doesn’t use that many animations” I hear you ask. Well think again because if I have an opportunity to make something bloody hard for myself I am going to take that opportunity.

And it alllll comes back to the fact that I decided I wanted the Kana in Kana Quest to look like this.

 

See how cute the Kana are? What could possibly go wrong? Well it all comes down to the numbers of it all. See this game teaches you how to read Hiragana and Katakana right? Well there are 45 base Hiragana, and 45 base Katakana. So that means that I will need 90 animations to cover each Kana. And as long as I just load up the correct animator object that has the correct animation attached this will be fine. Riiiight?

Wrong, because I decided in all my infinite wisdom to attach EVERY SINGLE ANIMATION to the one animator object. But then I hear you ask, but it’s only 90 animations, surely that’s not too bad right?

WRONG

Before I said there are 45 base Hiragana and 45 base Katakana. There are ways to alter the sounds of Kana. For example き(ki)+や(ya)=きゃ(kya). There are an additional 21 animations for both Hiragana and Katakana for all the ways you can modify a Kana’s sound. So there are 132 animations.

But like a bad infomercial…

BUT

WAIT

THERE’S

MORE!!!

Because this is just for the normal Kana. There are Stone Kana, Ice Kana, and Ghost Kana that all have their own unique animations. There are an additional 132 animations for both Stone and Ice Kana. Which brings us up to 396 animations. There are 20 animations for all the Ghost Kana, so that brings us up to 416 animations, all attached to the one animator. There are a couple of other unique one off animations that I am excluding here for the sake of brevity, but suffice to say there are a lot of the fucking things. The end result is an animator window that looks like this.

DumbCodingPart12.gif

But, the best thing about all of this is that the version of Unity I am using is 3.1.6f. Which is long before they added a zoom function to the animator window. Which means I’m stuck panning manually like this if I need to edit, ANYTHING. And of course it also means that I can’t mass edit the transition logic. So Reuben and I have had to edit, EACH, AND, EVERY, ONE, by hand. Which leaves a lot of room for human error. Together we have probably spend a full working week of time, just editing and navigating around this thing.

Ah, fun times.

Wrapping Up

I hope this has been a fun look at my own stupidity and inexperience. We will be back next month for another Kana Quest devblog. Hopefully it will be with our composers but I’m sure I will be able to find something to talk about if they can’t do it next month either. Here are the relevant social medias for Kana Quest

And until next time, have a great month!

Well its been a month. A whole lot has happened. But most importantly as I’m writing this… I am in Japan. The place where Kana Quest began. So this month we are going to look at my journey through Japan and look at some of the places that Kana Quest drew inspiration.

 

First up is the flight over. Not too much to talk about here, but the first stop in my travels was Cairns. Can’t get to Osaka without going through it. But I had enough time in my lay over to get some work done on Kana Quest, and charge all my devices up again for the next leg.

Speaking of the next leg, I got off at Osaka. Now I don’t mean any disrespect to Osaka. But I am honestly not a huge fan of Osaka. I personally have never really enjoyed myself any time I’ve been there, so I got off my plane. Headed straight to my hotel. Passed out. And got on a train to Kyoto the very next day. Which is good because in Kyoto was one of the main reasons I was in Japan: BitSummit.

IMG-1094So I tried to exhibit at Bitsummit this year, and unfortunately I was not successful. But I did decide that it would be worth heading over there and meeting some new people, playing some sweet new games, and learning some new things. I do want to give a shout out to Andrew (@DigDugpa), Shawn (@auberginenasu) and Lena (@Crowbeak) who took took me under their wing and introduced me to folks. The show was really cool and there were some really sweet games, and there was a surprisingly large amount of Aussie devs there. There was Necrobarista, Unpacking, and Frog Detective. The dev for Rising Dusk; Lukas Stobie was also there.IMG-1095 (1)

But once the show closed on Saturday, it was time for a Bitsummit tradition… The River Party. Devs, volunteers and attendees converge down on the Kyoto riverbank and just chill. Now the photo below is what the river bank usually looks like…IMG-1097

And this is what the riverbank looked like with all of us down on it.

IMG-1099 (1)

It kind of amazes me that we had a group of people this large (most of whom were drinking), and the cops were not called. I mean no one was doing anything awful, but a group of folk that large is going to be loud. And I can only assume that it eventually got annoying for the locals who were just trying to walk along the river bank.

But all good things come to an end, and so did Bitsummit. But I still had a bunch of time in Kyoto. So what did I do? I went to tourist destinations and drew.

Pictured above is Arashiyama. The place where that iconic bamboo grotto is. But I have always loved this view of it, from the outside. There are way less people, and its still just as beautiful.

I also went to Kiyomizudera. Which is the most iconic Buddhist temple in Japan. Unfortunately for me the temple its self was under restoration so it was covered in scaffolding.IMG-1128

But fortunately for me, I actually went there primarily for the sake of seeing all the small little alley ways that lead up to the temple. See Kyoto is one of the few places in Japan where you can still see traditional Japanese buildings still in good condition (you can see them in rural Japan, but they are often a bit run down). And let me tell you, the alley ways leading up to Kiyomizudera are just stunning in their own right.IMG-1123IMG-1125

I mean just look at them, they are gorgeous. I wanted to do a world in Kana Quest that referenced these alleyways, but due to the parralaxing backgrounds it would have been near impossible to execute them in a way that would have looked good.

Once I finished mucking around in Kyoto, it was time to go home. And let me tell you, home had not changed one bit. It was exactly as I remembered it. The clouds were even doing my favourite thing where they covered the tips of the mountains. Of course when I say home I mean where I lived. A small town called Wadayama in the dead centre of Hyogo prefecture. Below are some pics of my neighbourhood.  

If you were wondering where the first four worlds of Kana Quest came from, this is where they came from. While they don’t look exactly like the real world inspiration, what was more important to me was that the worlds made me feel like I was back here.

But then we have the cherry on top of my nostalgia sundae. The shitty box I lived in for a year. Now the pics just below don’t look that bad… that’s because the moment I moved out. They gutted the insides, repainted the outside and landscaped the surrounding area. Because let me tell you, when I first got there, there was mould everywhere, there were spider webs in my stove top grill, there was a large plastic bucket where a shower should have been (actually that one never got fixed while I was there), and the fridge that I had been left was not working…. And yet… god it was good to be back home.

Also, see that car parked in the third picture? That’s where I used to park my car. But something you cant see so easily is that there is a full two feet drop on the left hand side of that car. So driving into that thing was terrifying because if you messed up… your car was gonna end up on its roof.

IMG-1257

I also decided to do a drawing of the little park next to my home. When I moved in one of my coworkers asked me if being next to the shrine bothered me. She didn’t understand me when I said that I quite liked it because she thought it was scary. Still to this day I think I was very lucky to have something so beautiful next to where I lived.

Now this is starting to get a bit long so I might start wrapping it up. But before I do we are gonna do a few last rapid fire pics and what they are and why they are important.

IMG-1333

My fav Pokemon gets its very first official plushie from the Pokemon Centre, and I am so stoked.

IMG-1328

The Hiroshima Genbaku Dome. I was planning on drawing this one, but when I got there I found it a bit too upsetting to draw. Especially when you look at the pictures of the immediate aftermath and you can see the landscape around you as being nothing but complete devastation, I just found it a bit too much.

IMG-1303

The neighbouring prefecture to my Hyogo to the north west is Tottori prefecture. Which has the honor of being the least populous prefecture in all of Japan. What does it have? Honestly not a lot apart from a lot of natural beauty and sand. Seriously look at these sand sculptures at the Tottori sand museum!

Finally, I have actually been getting some work done while I’ve been over here (I know it doesn’t look like it). Unfortunately most of it isn’t ideal for showing off. But the art for the final mechanic in Kana Quest is now finally implemented. KanaVeyorBeltFinished

In terms of other Kana Quest news, our composers Julian and Leina are working damn hard on the music and I cannot wait to share it with you. And I might get them to write a devblog in the future about what they were trying to achieve with their music.

And with that, that’s all I got for this month. We are going to keep working hard on Kana Quest as we get ready for release later this year. I’ve had a few folk ask me if there is anything they can do to help the game leading up to release. And the answer is pretty simple, tell your friends about Kana Quest. You telling your mates to get excited for this game will do more than anything I do here on this devblog.

Until next time. Take care all!

 

 

Hi all, another month and another Devblog is here.

Sorry it is a day late, but I was volunteering during the Australian Federal Election yesterday and did not have time to write a post. And on that topic, all I will say is I am deeply disappointed with the results for a myriad of reasons. You might be happy with the results and that’s fine, but know and respect that this was a big loss for the Australian game development scene. If the election had have swung the other way, Labor would have reintroduced the Interactive Games Fund. This would have provided the industry with an additional 25 million per year. Now, of course, we will survive. But I really hoped this could have been an opportunity to do more than just survive.

Now onto the main thrust of this month’s devblog. This has been a bit of a weird month for the development of Kana Quest because all the major things have more or less been done. So we are in the fix up phase of things. Lots of small little boring things. For example…

W6L15.png

Before

newLevel2

After

This was a pretty small change, and I don’t blame you if you missed it. In the darker worlds the text displaying the number of medals becomes unreadable. So I added a backing to the medal counter to stop this.

I also finally got round to making some sprites for the final mechanic in Kana Quest. KanaveyorBelts.gif

These are Kana-veyor belts, they move all Kana in a row or column along one spot. Up till now we have just been using place holder assets. Still haven’t fully implemented them yet. That’s Monday’s job.

Also found a whole bunch of very strange and niche bugs.SlimeAnimationBug

For example here if you go to slime a Kana, then pull back to the first frame of the animation, and then let go of the mouse. It will cause the slime Kana to break and be unusable.

IceNNandBinDontRegisterMove.gif

Or how about, if you have an Ice “n” Kana and you move it into a removal tile from an adjacent position you don’t use a move.

Ice+YaYuYoBug.gif

Reuben (Kana Quest’s lead programmer) has had fun the last few weeks squashing this bug. So the problem was that when you used a ya, yu, yo Slime Kana on an Ice Kana and then undid any subsequent moves, the Ice Kana would become whatever was the last Kana it moved with. The cause of this problem was being caused by the fact that we had not set up the Ice + Ya/Yu/Yo animations yet. See, all the Kana faces are handled by Unity’s animator system. And the animator will change the animation according to each tile object’s hiraganaNumber variable. This a variable that is stored on the back end so the player never sees it, but it is vital to the function of the game. But when you add the Slime Kana to an Ice Kana, this changes the hiraganaNumber . However because there was no animation that corresponding to the new hiraganaNumber the animator just says “I’ll just keep playing whatever animation I was playing last”. However because of another weird quirk of how Kana Quest has been built, when you undo a move, you aren’t actually moving the Kana to their original positions. You are swapping all the data being stored between the two Kana involved in the move. So for a brief moment, the Ice Kana would have the hiraganaNumber of whatever you moved it with. This is normally impossible to see, but because of this bug this causes the Kana to display the wrong image.

But I hear you ask, why did it take Reuben a few weeks to fix this up? Well the first thing is that Reuben only works on Kana Quest two days a week, and secondly is that whole animator system I glossed over earlier. See, because all the Kana are just different instances of the same object, each of them have over 300 different animations that could be playing at any given time. And each of those animations need to have the logic behind them properly added. This results in a job that is both time consuming and impossibly dull. Oh and because we are using an old version of Unity for this, we can’t zoom out of the animation tree. So poor Reuben was stuck looking at this monstrosity for hours.

fuckedAnimationTree.png

Also note that this image is from about a year ago. There are now more animation states. So lets all tip our cap to the incredible job Reuben did with enduring this system this month. Also I feel its important to clarify that the janky-ness of these systems are my fault not Reuben’s. As I made them well before he was involved in the project.

Ok, one last weird bug before I sign off for the week.TileSlideMidMoveBug.gif

So if you moved a Kana on or off of a Kana-veyor belt while it is moving itself, it caused the whole system to have a bit of a melt down. This gif here its pretty tame as it just causes the わ to appear where the blank Kana was at the start of the level when the undo button is pressed. But in other times when I was trying to replicate this bug I had multiple Kana going “nope” and just translating off the screen and then glitching in and out of view if you tried to move anything around them.

There have been a bunch of other small little changes that have been going, but most of them aren’t easy to show visually or are just exceedingly boring to write about. So I’m sorry if this month was a bit light on the ground. Next month however I will be in Japan for Bitsummit. Unfortunately I wont be exhibiting there, but I will be around. But the long and short of it, is that next month I think we will do a tour of the places that inspired a lot of the art in Kana Quest.

Until then, take care.

Hi all,

It’s the second Saturday of the month which means its time for a now Kana Quest Devblog! Last time I said we were going to unpack several choice levels from the game, and what makes them good levels. And that’s exactly what we are gonna do. So

Now if you’re new here, Kana Quest is a cross between dominoes and a match-3 game that teaches you to read Japanese. You match sounds between letters, and when all letters are connected the level is complete.

GoodLevel1.png

This is the fourth level in Kana Quest and is the first level that consistently stumps players. Up to this point levels have been made to get the player used to moving Kana around, and understanding that stone Kana can’t move. This is the first level that actually tests the player’s understanding of how Kana match. So, how is this achieved? It is achieved by asking the player two simple questions; “In what order do the three movable letters need to be in so they all match?” and “Now that I have the order of the three movable Kana, how do I position them so that the one stone Kana also matches?”. These might seem like very simple questions, but there are a few factors that make them a lot harder than you might suspect. The first thing is that, this is the first time the player has had to order 3 Kana. Second is that all of the Kana have been deliberately placed so that the player has no matches, this means they are effectively starting from scratch. Thirdly the number of potential configurations is way higher than all levels up to this point. Finally, because the stone Kana is placed in the centre of the board, it means there are a total of 4 different correct solutions. But it doesn’t guide the player to any of those solutions in of its self. This forces the player to pay attention to the sounds of each Kana, and use that information to solve the level. Not use the shape of the level to tell them the solution. This is not to say that using the shape of the level to guide the player is a bad thing. It usually is a great thing to do, especially for more complex levels. But the purpose of this level is to test the player’s understanding of how Kana match.

 

GoodLevel2

The next level I want to look at is the final level of world 3. So where the previous level was testing the players understanding of how kana match, this level is testing the players understanding of one directional kana. One directional kana, are a lot of fun to play with because of how the restrict the number of potential arrangements of the kana. This is useful because it can be used to signal to the player the shape of the solution.

This level is set up so that there are only 5 possible positions for each row that could be the correct position. This helps the player start with a very strong sense of how to solve the level. But there are two curve balls in this level. The first is the one normal Kana (の) at the top of the level. Because this kana could potentially go anywhere in the level, the player has figure out how to best utilise it. The second is the one directional す on the right of the level. This says to the player that one of the three rows to the left of it need to be all the way over to the right, but you need to figure out which it is. When these two elements are mixed with each other they create an ideal puzzle. A puzzle where the player has a strong idea of their goal, but they still have to work for it. One last small detail from this level that I like is the blank one directional kana. These serve to prevent the player from trying red herring solutions. Red herring solutions are fine to have, but each red herring still needs to lead the player towards the solution. If a red herring just leads the player down the wrong path and leaves them at a dead end, you need to get rid of it, as it will only aggravate your player.

 

GoodLevel3.png

So for the last level that I want to talk about today is from the ninth world. If the first is an example of a good introductory level, and the second was a good intermediate level. This is a good hard level. So what makes this a good hard level? Well, honestly the same thing that’s made the previous two good; You know what your goal is, but you don’t know how to get there. This level achieves this with the り in the centre of the level. Because it is central, and it cannot move because it is a stone kana, the first thing the player will do is look for the other kana that match with it. In this level there is the transform kana (the rainbow coloured one), the ice ろ, and the paralysis ひ. The paralysis ひ has to end up to the right of the り because it can only be moved once before turning to stone. This leaves three spots left for the ice ろ. This puts the player on a strong starting direction for the level. But the thing that makes this level so challenging is that because of how ice, paralysis and one direction kana work, if the player makes moves carelessly they will trap themselves and be unable to complete the level. Once again, the needed end state is easy to determine, but how to get there is the challenge. The only real difference between these three levels is that they make the “how to get there” part more complicated.

Anyway, that’s the Devblog for this month. Hope you enjoyed. I’ll be back next month on the second Saturday of the month. I haven’t figured out what the topic is gonna be, but ill figure something out. Until then, take care!

Hi all, its another month and that means its time for another Kana Quest DevBlog!!

Like last month I have just been working on levels. But the big difference between this month and last month is that I am now SO CLOSE to finishing all the levels in the game! There are 13 worlds in a Kana Quest, I have finished making levels for 11/13, and the 12th world is more than two thirds complete. So we are in the home stretch here folks.

At this point I have had a chance to work with all the mechanics in the game and I thought it would be fun to talk about each in depth about the positive and negative elements of each.

mystery

And oh how the mighty have fallen. This is a Mystery Kana, and they were the first mechanic I made for Kana Quest, and I was so proud of it at the time. And I still think its a valuable thing to have in the game, but the more I used it the more utterly irritated I got when I play-tested any level with them in it. So why did I make them? Why are they important? And why are they so irritating? So I made Mystery Kana because I was having a very specific problem, players weren’t flipping over the Kana to learn the pronunciation to complete the levels in the first world. This is problematic because it would render the entire function of Kana Quest meaningless. So I needed a way to effectively force the player to look at them. Mystery Kana do that very well. They just also irritate the player at the same time. The way these things work is they cannot move, but can match. The player needs to keep track of what each Mystery Kana, does and does not match with. Then using that information, figuring out what the Kana’s true identity is. The biggest problem with Mystery Kana is they just simply break the flow of the game and force you make non optimal moves to figure them out, and then you can complete the level. The end result is they start to become a nuisance after a while, and its for this reason they get phased out after world 4.

OneD

The One Directional Kana have been a solid work horse throughout development. There are so many things about this mechanic that are excellent from a designer’s perspective. 1st is they are easy to understand from a player’s perspective. The arrow shows you what they do; they only move in one direction. 2nd is they have a huge amount of design space. Design Space is a design term for talking about how many different interesting configurations a mechanic can be used in. And these Kana allow for so many interesting levels to be made. I am still finding new and interesting ways to use these things even in the 12th world. They are also very flexible in how they can be used. If you want to build an entire level around them, you can and it will probably be a really fun level. But you can also just throw one of these into a level to help guide the player towards the solution. I suspect once I have finished making levels, and I’m in the polishing stage I will end up adding a lot of One Directional Kana for this exact reason. What’s more is they also have interesting interactions with basically every other mechanic. The only complaint I have against them is they can be very punishing of mistakes. The reason for this is if you move one spot too far and then make a bunch of other moves, you end up spamming the undo button more than is ideal.

IceDemo

The fourth world’s mechanic is the Ice Kana. These Kana will keep sliding in the direction you move them until they make an invalid move. These Kana are a good mechanic, but no where near as easy to work with as the One Directional Kana. They have a large amount of design space, they have interesting interactions with most other mechanics, and they can make some very fun levels. But the problem is that you can’t just through one of these into a level. Even if the Ice Kana is supposed to be a minor element to a level, you have to build the entire level around the Ice Kana to accommodate it.  This is not a bad thing as it allows you to create a nice change of pace for the player at points, its just something that needs to be treated with care. Another small problem is they tend to demand levels be a fair bit larger than a similar level without them would be. Other than that, I think Ice Kana are great.

SlimeKana

The Slime Kana are another mechanic in a similar vein of the Mystery Kana as they both play around the sound matching aspect of the game. And so what they do is they will change the vowel sound of any kana you use them with. However unlike the Mystery Kana, these do not get highly irritating after a while. The main reason for this is that they often feel like they are helping you, rather than getting in your way. And because of this is they can just be plugged into a bunch of levels to add a little bit extra. But the biggest weakness of them is that they struggle being the core element of a level. Where the Ice Kana can’t help but be a diva, the Slime Kana struggle with it. Another problem with the Slime Kana is that because the Kana that appear on them can only be Slime Kana it does mean that the Kana on them just get seen less than every other Kana. But the gameplay of them is still solid enough that I made two variants of them.

 

GhostKana

This is a Ghost Kana. Ghost Kana, cannot move and cannot match. But they will come back from the dead once the player has made a group of Kana equal or greater than the number on their head. This is a tricky mechanic. And honestly they represent the biggest disparity between what its like to work with them, compared to what its like to play with them. Because playing with them is honestly pretty good. They make interesting scenarios, and force you to think about the level in a different way. But from a designer’s perspective these things are so hard to work with. You have to engineer levels so carefully around these to make them fun for the player. They have very limited amounts of design space too, so I honestly struggled to finish the world where these were introduced. And what’s worse there are some mechanics that this straight up does not work with.

YaSlimeKana

So this is the first of two Slime Kana variants. This is a Blue Slime Kana. Blue Slime Kana are different because they only ever attach to Kana that end with an “i” sound… and they add an additional vowel to match with rather than completely changing the vowel. This is because of an actual function in Japanese. See Blue Slimes can only have the following letters や/ゆ/よ. And these letters can attach to other letters to make slurred sounds. For example き(ki)+や(ya) = きゃ(kya). So きゃ will match with “i” ending kana, “a” ending kana and “k” starting kana. This makes the mechanic quite satisfying for the player to use because it opens more doors for them than regular Slime Kana do. And its for this reason that they can be a bit frustrating to design around as a game designer. Another problem with them is they have to attach to a kana that ends with an “i”. This over the course of the game makes “i” ending kana being over represented in comparison to other kana. Whats more is that often you have to design levels in which fully utilise the multiple vowel sounds. But this often leads to further exacerbating the over represented “i” problem. But other than these issues, these kana have all the strengths of regular slime kana. And they allow me to illustrate an important part of reading Japanese.

Paralysis These are the Paralysis Kana. They can be moved once… but after that they turn to stone and cannot be moved. These are probably my second most useful mechanic, just after One Directional Kana. They allow for interesting level design, and they have a good amount of design space to them. Not quite as much as One Directional Kana, but still a large amount. They are also very easy to understand what they do. And they can be the focus of a level, or be used as a back up element. The biggest problem that they have though is they have a hard cap on how difficult they can make a level. This isn’t a bad thing as it does mean it’s basically impossible to make a level that is too difficult with these but it does make them a bit more restrictive as one might like in later levels.

Transform

Transform Kana are pretty straight forward. Then can become any Kana, but they can only be one Kana at a time. This mechanic probably has the least frills of any of my mechanics, and you what that’s ok. It works just fine. They ask a simple question of the player, and that question is “where am I needed, and what do I need to be?”. So the trick to designing around these Kana is making sure there is a spot that can only be connected with a Transform Kana. Which is fine as long as one is careful with the other Kana that are used within the level. If you aren’t careful the player will just plop the transform kana anywhere and not have to think at all. They also suffer the same problem that Slime Kana face in that they struggle to be the focus of a level, but they do slot into lots of levels pretty easily.

MaruKana

Here is the final Slime Kana variant. And this is yet another instance of me basing a mechanic off an actual function in Japanese. There are small added strokes called “tenten” and “maru” for Hirgana and Katakana. These will change the consonant of the letter they are attached to. In the game this often is something that is a disadvantage, not an advantage like the other two Slime Kana. Because of this you cannot finish a level if there are any Purple Slime Kana left in play. This forces the player to find the part of the level that can accommodate losing its consonant sound. Basically everything that applies to the first two applies to this one.

  DickheadKana

This is an “n”. Because they don’t share a consonant or a vowel with any other Kana they cannot match like a normal Kana. So I decided to make them the Unfriendly Kana that all other Kana hate. So for as long as an “n” is in the level, you cannot complete it. So how do you get rid of an “n”? You dump them into a rubbish bin. Which looks like this.

Bin

Once an “n” is moved into a rubbish bin both are removed from play, and the spots they occupied become empty spaces on the board. This mechanic requires a fair bit of set up to get working, but once you set up a level to accommodate them its a solid mechanic that has a solid amount of design space. One unique problem with this mechanic is using effectively uses up twice the amount of space that a regular Kana would. Because of this levels with this mechanic tend to look very cluttered and can be a bit difficult to process. Outside these problems they are a solid mechanic that just needs a bit of preparation to make work.

 

Finally we have Kana Sliders. The art for these is still under way, but what these do is they move every Kana in a row or column down one spot as long as there is an empty spot on the board in that direction. This is a very easy mechanic to design around and offers a lot of design space that had not been available for me for most of the game. Because Kana Sliders care about empty space, it allows them to interact with Slime Kana and Unfriendly Kana that no other mechanic has been able to do so far. The biggest problem with them however is they tend to make levels with ridiculous amount of moves required to complete them. There are levels that require more than 70 moves to complete with this mechanic. This can be problematic especially if the player makes a mistake early on as they will be punished especially hard for that error. Other than that issue, I love working with Kana Sliders.

And with that this weeks Kana Quest Devblog comes to a close. Next time I think I’ll pick out a handful of choice levels, analyse them, talk about how I made them, and talk about why I think they are special.

First thing’s first, I know I missed the January devblog. I’m sorry it wont happen again. But… it’s here now, and it’s a new year, which means this is the first devblog for 2019! This is going to be a big year for Kana Quest as this is the year we are going to release! Knowing the end is in sight is a strange feeling as I’ve been working on Kana Quest for the last two years of my life. But I hope you all will be there with me as we run headlong down this final stretch!

So what does this “final stretch” look like in terms of development? Well for me personally that means making all the levels. I had spent most of 2018 finishing the art and making all the visual assets, but in terms of gameplay, very little was being made. But now that I’ve finished all the visual assets and Reuben my programmer has finished programming in each mechanic, I am able to churn out levels very quickly. How quickly is that? Well since last month’s devblog, world 5, 6, and 7 now have all their levels made. Of course these levels still need play testing before they are 100% good to go, but they are playable, and reasonably balanced.

So, seeing as levels are all I have been doing this past month, I’m gonna tell you how I have been making them. And some of the weird things I have to pay attention to when I’m making levels.

The first thing I do when I start making a level is I figure out, how hard I want this level to be, and what kana I want the player to see.

flowchannel

Sorry if this is a bit too game design 101 here buuut… This is the flow channel. Flow is that feeling where you are in the zone. But getting the player into the zone requires very careful balance from the game designer. So something I’m sure you will notice when you play Kana Quest is that every three to five levels will build in difficulty, only to drop back a bit and then continue ramping up in difficulty.  The reason you do this, is that it’s just more fun for the player.

In Kana Quest there are a few different ways you can control the difficulty of any given level. They are:

  • The amount of Kana in a level
  • Size of the level.
  • Potential board state permutations
  • Number of potential solutions
  • Complexity of solution.

So lets go through each of them. And first up is the amount of Kana. So in my experience, you have a hard cap of about 14 -16 different Kana in a level. Why is this? This is because past this number, there is too much information for the player to comprehend. And personally, even I can’t process levels with this many Kana. It’s also a difficulty that isn’t a lot of fun for the player. Solving the puzzles is fun, recognising kana… not so much.

The size of the level like the amount of kana, also has a hard cap. This time its not so much about overwhelming the player though. The largest you can make a level in Kana Quest is 7×4. This is simply because if you make the level any bigger, it will not fit on the screen. I know that sounds silly, but due to the way pixel art works, there is no easy way to just “zoom out” without also causing a lot of pixels to bunch and stretch. But honestly, most of the time this is plenty to work with. If you are smart about how you construct things this is not actually as bigger constraint as one might think it is.

What I mean by “potential board state permutations” is how many possible unique configurations can be made in any given level. So for example.

These two levels have the same kana, and the same starting positions but the first level is significantly easier than the second because the number of possible configurations of kana has been significantly reduced. Forgive me if my maths is wrong but the level on the left has only 120 unique board positions, whereas the level on the right has 362880 unique board positions. And while an advanced player can see through all the unnecessary information in the second level, it doesn’t actually make the puzzle any more fun for the advanced player because in both scenarios, the solution only requires two moves. So while you are giving advanced players a disappointing level, you are giving new players a level that is so information dense they will almost always solve the level by brute forcing the solution. What I’m trying to convey here is that when designing puzzles you need to control the amount of possible states so that you can guide the player to the solution. Now for more advanced levels its fine to offer levels that are more open ended, but you do need to be very sparing with how you do so.

Next up is the number of potential solutions. This category is a tricky one as personally I feel as though levels with multiple solutions make the level harder, not easier. Why you might ask? Well because it means that your players are less guided towards the optimal solution. It means they are more likely to get caught on unintentional red herrings. It also means that if the player wants to get a gold medal for a level, but they have only ever completed the level using an alternate solution that is more move intensive than the planned solution, they could spend way too long trying variations on the “wrong” solution. Really this is a side effect of having too many potential board state permutations, but every now and again its fun to have levels that offer multiple answers. Lots of levels in Kana Quest only have one solution, and lots of levels have multiple, the important thing is using this technique intentionally.

The final technique that I can use to control the difficulty for the player is probably the most important one. And that is complexity of solution. If the solution only requires two or three moves, its not a particularly complex solution. This usually means that the level isn’t super difficult. However, completion critical moves increase the complexity. A completion critical move is a move that if not made, the level cannot be completed.  Of coarse this can then be balanced with previous techniques. For example.example3

This is a level from world 1. And is in my opinion one of the best levels in that world. This has a very low complexity of solution, but in contrast to the all the levels before it, it has a slightly higher difficulty. But that difficulty comes from a larger number of potential configurations, multiple solutions, and a larger level size. The result is a level that isn’t too difficult, but does force the player to stop and think about the solution. But as the game ramps up in difficulty, ramping up the complexity of the solution is usually the safest way of doing so. Why is that? Well, it means you can control the amount of information you throw at the player to a far greater extent. Remember, you don’t want to overload the player with information, if they do they just start brute forcing the puzzles and have a bad time.  So an example of a good level made by giving the player a complex solution is this level.examplesolution

The reason this level is good is because it requires a good amount of moves to complete, and there are only two completion critical moves required (using the Slime Kana on the correct Kana), and those moves can be executed by the player at any point. Whereas, here is a level that has gone way too far on the complexity of solution.example3

This level is way too hard and is to date the most difficult level I have made. And the reason is, that every singe move in this level is a completion critical move that requires being done in the exact right order. If you make one wrong move, you cannot complete this level. The fact that this level has a relatively constrained number of possible configurations is its only saving grace. And I wouldn’t be surprised if I remove, or rework this level before the launch of the game.

I think the real take away from this blog if you are making, or thinking of making your own game is; What are the different vectors for making a game difficult? Are there enough? Are there too many? What are the implications of using one of those vectors? What are the implications of using multiple of those vectors at once? How far can one push any and all of those vectors before a game becomes impossible? And most importantly, at any point in a game, what vectors of difficulty does the situation call for?

Anyway, these are the things that I’ve been thinking about for the last month or so. I’ll see you next month. If you have any questions about game difficulty or you disagree and you want to start a discussion, feel free to leave me a comment and we can have a chat. Until next month, take care.

Hi all and welcome back to the Kana Quest devblog!

This last month was a busy month for Kana Quest development because for the first time, we’ve had to deliver to an “official” deadline. There have been unofficial deadlines before, like PAX and AVCon last year, but those deadlines were a bit fuzzier. They were more “make sure your game is in a presentable state by this time” sort of a deal. This deadline was much more concrete.

So what was this deadline? Well as a part of receiving funding from Film Victoria I have to complete milestone reports to prove to them that their money is being well spent and that I am on track to completion. For this milestone I said I would have the game’s art complete, and the game’s mechanics complete. And… we got there. All that remains at this point in time is bug fixing, level design, tutorials and balancing. That’s actually still quite a lot of things but lets not focus on that. Let’s focus on fun stuff. Like the full list of all the different kinds of Kana in the game!

STONE KANA: These poor kana have been turned to stone, and thus cannot move.

CtStoneHa

 

MYSTERY KANA: Look at these shifty looking Kana. They’re hiding something… Oh wait they’re hiding their true face! Pay attention to what they do and do not match with to discover their true identity.

mystery

 

ONE DIRECTION KANA: These Kana can only be moved in one direction. They have a big arrow on their head showing which way that is.

OneD

 

ICE KANA: These Kana have been encased in super slippery ice. They will keep moving until they can’t. Getting them to go where you want can be challenging.

IceDemo

 

GHOST KANA: These kana have lingering regrets. Mostly not wanting to pass onto the other side. But that’s no problem, you can bring them back to life if there’s enough friendship to go around. Make a chain of Kana the length of the number on a Ghost Kana’s head and they’ll come back!

GhostKana.gif

 

SLIME KANA: These gooey Kana don’t like to make friends. But they do like helping other Kana! Attach one of these Kana to any other to change their vowel sound!

SlimeKana

PARALYSIS KANA: These Kana are sick! You can move them once before they turn to stone!

Paralysis

 

BLUE SLIME KANA: These Slime Kana are a bit picky in which Kana they help. They will only help Kana with an “i” sound. But once they are attached the affected Kana will have two different vowels to match with other Kana. This mimics how the “y” sounding letters in Japanese attach to “i” ending kana to create blended sounds.

Eg. (yo) よ + (ki) き = (kyo)きょ (as in Tokyo)

YaSlimeKana

 

SHAPE-SHIFTER KANA: These Kana can become anything! Whatever you need them to be, they can be it!

Transform

 

EVIL SLIME KANA: These Slime Kana nice like the others. They are angry and will stop you from completing a level unless they are attached to another Kana. But they make it harder for you to match with other Kana. This mimics the tenten and maru symbols in Japanese. You attach these symbols to letters to change the consonant. E.g. a (ta) た becomes a だ when you attach those two dots called tenten to it.

MaruKana

 

JERK KANA: This kana is called “n”. “n” for “n”obody likes them, because they are a jerk. They’re mean, they call the other kana names. They are so unpleasant that other kana cannot be happy if there is one near them. Fortunately there is a way to get rid of them. Move a jerk kana into this little portal thing and they will GO AWAY. Where do they go? Don’t worry about it.

 

And that is all the Kana! Its been a long road getting all of these in the game, and I can’t wait for you to figure out all the puzzles they are going to make.

Anyway, I’ll see you in the new year! Have a happy and safe holiday season, and from me and the Kana “明けましておめでとう” (Happy new year in Japanese)trailerWIP2

 

Hi all, welcome back to the Kana Quest Devblog!

A whole lotta stuff has been happening for Kana Quest this month so lets get to it!

Firstly is THE NEWS. There is only one really big piece of news and it came at the end of Melbourne International Games Week last month. Now I had known about this for a while, but I am now officially allowed to talk about it. Kana Quest was successful in receiving Film Victoria Funding in the most recent funding round! I’m really proud of myself for getting this funding, there were a lot of awesome games asking for funding in this round and I was one of the lucky ones to get through.

Here’s a link to the official announcement: http://gamesweek.melbourne/film-victoria-games-investment-greenlights-14-new-projects/

But enough tooting my own horn, onto the new stuff! And as of this month, I can say that Kana Quest’s background art is now 100% complete. Last month there were two more worlds needing to be completed. Well, they’re done now!

world12Complete.gif

So this is world 12 in the game, showing off the parallax effect. So the idea behind the last three worlds was a three part story of a Kaiju (Godzilla type monster) coming to Japan, getting into a fight with a big Mech, and then the aftermath. World 12 is the the fight with the Mech. A couple of small details with this piece. The buildings in the background are the same buildings that appear in World 9 which were based of the main street in Akihabara. These buildings though were scaled down, had their colour changed and had a bunch of bits torn out of them to show the impact the fight was having on them. Also the Mech has a カ on its chest with is the Katakana for “ka” and the Kanji for power (Chikara). I was also going to give the Mech and the Kaiju simple idle animations, but the animation for them and nothing else looked weird. I also chose this colour pallet to make this world feel dangerous and scary. A lot of villains from TV shows have a purple and green colour pallet so I decided to lean into that. Also this world is the first time I’ve used outlines in Kana Quest’s backgrounds. Choosing if you are going to outline in pixel art is one of the biggest stylistic choices you can make, and I decided pretty early on that I wouldn’t use them for the majority of the backgrounds. But As I wanted to draw attention to the Mech and the Kaiju in this world I broke my usual rule.

world13ProcessGif.gif

world13wipBorderOff.png

And here we have, THE FINAL WORLD. So the conclusion to the three world “story arc” is that the Mech has defeated the Kaiju and stands victorious looking to the sun. But in the foreground we see the destruction that the fight has caused. A couple of notes, this scene was definitely inspired by FLCL and the scene where Haruhara Haruko leaves at the end of the series. It had everything I wanted from the final world, it had dramatic imagery and it was used to close one of my personal favourite shows (don’t watch the second season though, its awful).  I also decided to change the sky for this world. Every previous world has had a gradient for their sky. And that gradient was achieved with dithering so I could keep my colour count low. But for this final world I went with a flat off white with a bright red sun in the middle of it so that it would look extra unsettling next to the other worlds, but also to mimic the Japanese flag. I also talked briefly about how I have generally avoided outlines in the backgrounds. In this world I deliberately broke that rule to further hammer home that this world is not like the others. The final little detail that I put in here is the dog at the front. He is my actual real life dog. He always looks very dramatic so I thought he would fit right at home in this world.

Next up is how the game is progressing in terms of Mechanics. And I can say, now that Reuben has been working on the game for a month, very very well! Since coming on board he has cleaned up a bunch of code behind the scenes, added in FIVE mechanics into the game. This brings us up to 9 out 13 mechanics in the space of a month! And now that the world art is done I have even started making art for some of these mechanics.

GhostKanaDemo

This is a Ghost Kana. Ghost Kana, cannot move or match with other Kana. Also you might have noticed, they don’t have a Hiragana/Katakana on their head. This is because once you make a group of Kana with a size equal to a Ghost Kana’s number, they will come back to life as a normal Kana. This is got some great play to it especially when you add in some of the other mechanics. Once all the levels for this mechanic’s world are done I’ll do a break down of this mechanic on how it can be used and how much depth it adds to the game.

So anyway, that’s basically all I have for this month. If you have any questions, please don’t hesitate to ask. Until next time, take care of yourselves and have a good month!