Showing posts with label features. Show all posts
Showing posts with label features. Show all posts

Monday, November 7, 2016

Major UI update in v0.7.4

BlogLine

Hello there!

We've just added a new Early Access version of Kalaban to GameJolt. We wanted to highlight a couple of new things from this package:




  • Food mechanics

Now, this feature hasn't actually changed, but now we've highlighted how it functions. In Kalaban, when your food meter drops to zero, Bob will not starve. Instead, the food value determines your regeneration rate. The more food you have in your stomach, the faster you recover. With zero food, player does not regenerate.




  • Drag & drop inventory

We've had a lot of feedback from our testers about the bugs in our inventory hotbar. Now we've rehauled the system, and made it more "click & drop" than "drag & drop", eliminating a lot of the issues that we had before. The inventory still features the standard dropdown "Use/Drop" menu, which you activate by right-clicking an item. Third way to activate an item is by double-clicking it.


Okay, so those are main things in this new version. You can download version 0.7.4 from our GameJolt page

Friday, April 8, 2016

Friday diaries #1

BlogLine
Hello!

This time I thought I might take you through the pain of what it's like to develop Kalaban. Not to be too whiny here, but just an insight to the things we struggle with all the time:

1) Y-sorting 

Because Clickteam Fusion 2.5 is a purely 2D engine, it cannot handle the Z (depth) dimension in its code, only the X (horizontal) and Y (vertical) dimensions. This means that overall it's much simpler to handle than a full-blown 3D engine. But also, that when you're creating an isometric game, you'll have to pull all kinds of tricks in order to get the depth effect by using just the Y axis. We mostly use the 'Layer object' in Fusion, but that only works well with moving objects and not the environments. Luckily though, with careful planning and a bit of case specific coding, you can get pretty stable results. The method we're using for Kalaban could never be replicated for a Diablo type of game, with randomized maps and environments.

And then, something like this happens:




After hours and hours of scripting, it still breaks down. Well, occasionally anyways. Just a small detail in the overall game, but a very noticeable at that. Of course, every one of these bugs can be fixed, but it just requires a lot of time and patience.


 2) Creating the environments
A problem, or more of an integral part of the whole development, are the custom-made environments of Kalaban. We chose to keep the size of the game world smaller, but opted for a completely unique look for all the areas. This means that all of the maps are created by hand, with very few assets being re-used. Well, it is quite obvious why this creates a lot of work for development, not only with the art creation, but also scripting all the individual areas. In addition to this, we chose a unique perspective for the whole game, which is not purely isometric.




 To make things a little easier, a lot of the props and map pieces are first modeled in 3D and rendered to sprites, using a virtual camera that has the right distorted perspective. After this, the rest of the environments are mashed together, painted and partially created from scratch in Photoshop.
 

  An example of the gas station scene I'm working on now. Notice the touches that have been made to the original 3D pieces. The final part is of course bringing these environments to the game engine, and giving them the proper lighting.


3) Inventory & UI 
This was special pain in the butt for us during the early days of development. Tagging the inventory items to specific places in code requires a ton of work. There's also the scripting which is required for item interaction, dragging and dropping, using the items, etc. All this has to be done as many times as you have different inventory items. For this reason alone Kalaban will never have 400 different objects named "dirt", "trash" or "scrap", in the style of Fallout 4 or other Bethesda open world games.


Well, I could add a few more items to the list, but I think that's it for now. For now, have a great friday, everybody! :)

Thursday, March 3, 2016

New and very tasty

BlogLine

Howdy y'all!

It's been busy here at Rayhouse with the Kalaban's development heating into full gear again. We've had some lengthy discussions with our four guy power team, and from our creative director's initiative we've decided to put our focus on the first act of the game. Kalaban was originally meant to span over the course of three acts, with a total playtime of over 5 hours. Now we've decided to put the environments to a better use, and flesh out the scenes more. This way we will not (maybe) work ourselves to death, and will be able to deliver a finished game, maybe during this year even!


Indiedb Verticalslice
So yeah, the original plan was pretty suicidal from the start, but it became even more evident during the development. We've been working on Kalaban for over a year now, and a couple of things have become very clear to us. First of all, gamedev is friggin hard, which should come as no surprise. Secondly, the environments take a load of time to make. The optimal time to make one scene is one month, but for example the Scene 3 took us three months to build. There were some heavy iterations, yes, and the game was still in very early stage back then. Even the plan for Act I includes a total of 13 scenes. We currently have six of them under construction, so there is still A LOT of work to be done.

Bob fighting against a Spitter in scene 7.


Indiedb Morefleshed
Of course this new arrangement won't mean that the game will be an hour-long experience. We're aiming for the core gameplay to be a total of four hours, plus bonus content and side quests. The most interesting thing about Kalaban is the setting and how it affects the art direction. The story is set in an alternate past of Finland, so we're constantly making sure that the elements in the game match that. The gameplay will be more like a detailed and unique adventure game, in the style of DreamWeb (1994), than just a top-down shooter like Alien Shooter (2003) or Crimsonland (2003).

A check-list of things Bob must collect in order to complete his quest.


Indiedb Rewritten
In favor of making the game more engaging, we've re-written the main quest for the game. Originally, the Act I served as an introduction to the story, and told the very first steps of the outbreak. Now, the objective is to find a car and escape to the city, and hopefully reach safety there. Of course we still have a general plan for the future events of what happens when Bob reaches the city. If this game does really well, and there is a serious demand for it, we will continue with part 2 and part 3 of the story.

Bob has reached the momentary safety of the local pub and its beer storage.


Indiedb IntroducingNPC
The original plan for the whole game was to have maybe one or two brief NPC encounters, but to keep the game otherwise a desperate one man battle against the mutant horde. This was largely inspired by the way System Shock (1994) and its successors handled the story. Now, the locations will feature a number of other survivors, fighting for their life. One of them is Keijo, your former boss and owner of a sawmill. He has seen better days, but is still sane and has been able to fight off the invasion. Some of the NPCs you will be able to save, and maybe even take with you to the city.


That's it for today, thanks a bunch for tuning in! To stay updated on the development progress, either follow us on IndieDB, or keep reading our blog and add it to your bookmarks. See ya!

-

Friday, May 15, 2015

New features under way

BlogLine

Hello there! We're currently developing the pre-alpha version 0.2004. So far, the light and shadow system has been a real issue and challenge for us. Now we've made another re-work on it, and revised the flashlight's light circle with more directions. Current light sources in the game include the flashlight and the torch. The shapes of the light have also been made softer in the newest version.

 
The circular shape of the torch light.

The problem with the light/shadow system is to make it as fluent and optimized as possible. And also visually as good-looking as possible. If the game would not be targeted for a very wide range of computers from very low to high end specs, it would be easy to just jam in a system which would require a huge amount of memory and CPU power.

We're also working on a new inventory and also a map screen at the moment. They are only visual at the moment, and have no interaction coded in. The map screen will feature a Scene and Act map, and also a short objectives list.

   
Shots of the incoming inventory and map screen.