JLJac on April 07, 2012, 11:24:15 PM:

Update 15

Limited the lizard's angle of vision.



Since the main thing making the game easy already is the croc not knowing where you are, the limitation is more in terms of not being able to see backwards rather than only being able to see forwards. Anyways, this allows you to wait in a side tunnel for a lizard to crawl by, and then crawl out behind it and get away.

You see the little bulge of vision covering the tail? If the point that's tested is close enough the angle is not tested, to simulate some kind of spatial sense and so that the player can't crawl into its tail without being noticed.

In an open level like this a lizard in the right position can cover huge areas, and two of them can see pretty much the whole level.



I think this works well, because open areas are not the crocs' favourite environment to move in. This creates a balance - close quarters: they won't spot you, but if they do you're done for. Open spaces: they'll spot you, but you have a fair chance of getting away.

JLJac on April 08, 2012, 12:45:54 PM (Last Edit: April 08, 2012, 12:52:42 PM):

Update 16
Gave the lizard hearing. To keep things simple and clear to the player the only thing that can cause a for the lizard hearable sound is landing on a floor after being airborne. If you make the tiniest possible jump by just tapping the button you'll make no sound at all. The variable of lizard hearing is how big the radius is within which it'll register this sound.

It doesn't know where you are, as when seeing you, and it doesn't know which player it heard. All the sound does is that if a croc is idling or snooping around and hears a sound it'll go to the place the sound came from to check it out. When chasing a known target it'll ignore sounds.

It is communicated to the player that a croc heard something in the way that it stops in its tracks for a second, as if listening. Once it eventually gets a head it will probably turn this towards the source of the sound as well.

JLJac on April 09, 2012, 12:37:04 AM:

Update 17

Made the croc able to kill the player. Not eat, that's a matter of animation and will be attended to later, but magically kill on touch. The croc is now able to lash out to a close by player, making it impossible to jump over it on a floor.

As I mentioned the croc is already slower than you out on open floors, and that together with you being able to jump and it only being able to turn made it possible to jump over its head again and again for ever. The new mechanic means that you can't do that any more. You can still jump over it by using a wall though.



Almost all the mechanics I imagined for the game are in now, but there's a lot of number tweaking to do. However, I feel that I'm finally at the end of the huge chunk of this project that has been the croc AI, and hopefully no other part will take as much time. There will be a revisiting to this though, when I have a little less schoolwork to do so I can try the game out with a friend. I have no idea how the crocs handle multiple players, it could be just fine, it could be in need of some redesign.

It's too hard to cath the A-creatures, need to tweak that a bit. Another thing I was thinking of was that maybe the player shouldn't eat the creatures on touch, but rather just catch them, and then you have to go find a safe place to consume your prey. I like this idea, will have to see how it plays out in reality.

Been thinking a lot lately about how I will render levels. Have some kind of semi-voxel idea going on, more on that later. However, with level rendering comes art, and with art the devlog becomes interesting! Hopefully the daily five page essays on how a virtual lizard finds its way around a maze has finally come to an end... A brighter future awaits!

JLJac on April 09, 2012, 01:35:39 AM:

Yeah, looking forward to drawing some more for this! Here's a little video showing some Croc path finding:
http://www.youtube.com/watch?v=sOzuv2QxyLo&feature=youtu.be

You see how it paces back forth a little bit at times? That's when the path is being calculated. I don't want it to be standing still during this process, because its speed will be a que to what behaviour it's engaged in. I prefer that it runs back an forth as in a bit of initial confusion, then suddenly realizes what path it'll take. Path finding speed is a stat, and some lizards may be slower than others.

JLJac on April 09, 2012, 11:13:19 PM:

Update 18

Moved the level rendering code over to the level editor, and overhauled it completely. The system is now working in a semi-voxel kind of way, where one tile is 20*20*10 pixels. I also made the level editor able to save a level in the format that I think will be final. Didn't try loading yet though... The level seems to be very light, so I'm happy about that.

The voxel format allows me to do some interesting stuff such as fog and light...



This is just 20 minutes of coding to test it, but I like the potential it has. Because of the voxels I don't have to create separate solutions for everything, stuff sorts itself out automatically. If you look at the detail in the lower right corner maybe you can imagine what a hassle it would be to calculate how the shadows would look in every special case like this, now it just works by itself.

It's flawed, yes, I have noticed the stripy floors. Also it will demand some patience, rendering it pixel by pixel will take a minute or two for an entire level. But I see a lot of potential in it!

JLJac on April 10, 2012, 10:52:06 AM:

Yeah, the creatures won't "take" or cast shadows, unless I want a framerate of... let's see... about one frame each 8 seconds

Thing is that the huge, complicated process of generating graphics for a level will have a slightly anticlimatic ending; one picture that's behind the game objects and one that's in front of them... But the process is still necessary, if those two pictures are to look good!

JLJac on April 10, 2012, 11:54:55 AM:

Update 19
The level editor can now save a level, and the game can load it. What this means is that the limiting factor of how long a level can take to render is how long you're willing to wait after having made a level, not how long you're willing to wait when starting a game.

This makes testing stuff a slight bit more awkward for me, as I have to actually save a level first. That's why I waited until now to do it.

Soon I might actually get around to some art stuff.

JLJac on April 11, 2012, 12:26:07 AM:

Update 20

Gah, most frustrating day ever... I've been struggling with the shadow renderer, and... that's pretty much it for today. This is what it looks like currently, flaws and all:



Right now the major problem is that objects don't self shadow, there's only cast shadows. The choice is between that and having the objects self-shadow even on the surfaces that should be lit...  I have no idea how to solve this, but will probably come up with something...

JLJac on April 11, 2012, 11:44:01 AM:

Update 20

Almost no progress what so ever... It turns out my code for raytracing the vision of the camera doesn't actually work. However something else (still unknown what) was obviously broken in a matching way, so the code gave me the right output anyway... Fine, up until I need to fix a problem and really have to understand the code. Then I realize it shouldn't work, but it kind of does, except from that problem I was trying to fix. If I fix the code so that it should work it doesn't work at all. So I settled for the broken code, with a dirty feeling of not having actually solved the problem.

With a horrible hack I managed to make it so that platforms are at least shaded on the underside. This is what it looks like now, with a thousand flake-thingies suspended in mid air to test the shadows.



There are some horrible bugs in there but hopefully it's mostly me who can see them. Right now - bye bye shadow code for a while, I'm painfully tired of this...

Tomorrow I will do something else.

JLJac on April 11, 2012, 01:01:48 PM:

Gah I solved it... Went back to an old approach and solved it.



No one except me can spot the difference I guess, but the difference is that now the shadows are CORRECT! Rendering time is something like 7 minutes or something though... But that's OK with me... At least it WORKS!

JLJac on April 11, 2012, 11:27:33 PM:

Update 21
I made the game considerably uglier today... That feels weird of course, but I think it's a necessary step towards starting to incorporate some kind of art direction. I want the game to be mainly flat colors, I believe, but still want the shadows around, so I'll have to find a way for those two to work nicely together.

JLJac on April 12, 2012, 11:33:09 AM:

Update 22
I think I finished the shadow renderer today, hopefully to never return to it. The game still looks bad, but now I think I have the tools to start fixing that. However, my entire level renderer is messed up at this point, it doesn't even render the slopes. Well well, two steps forward one step back. Hopefully I will get around to support for tile sets some time soon.

It's nice to see how the different part of the game work independently, when I open one of my new levels to see how it looks ingame the croc's AI navigates through the new environments with ease - obviously, as the level is mathematically the same, but still nice to see.

Today I also did some thinking on the game's overall concept, the reason why the player does what it does and how the world the game is set in will work. I'll give you some of this together with some art at a later point, ideas always sound cooler with some tasty art to go with them.

JLJac on April 13, 2012, 01:26:58 PM:

Update 23
Now there is a tile editor, though there are no tile sets. The level editor will work like this:

First, there will be the level editor. Here, two players can work at the same level simultaneously and create the layout of the level. You'll be able to save the level in som kind of test version, with no real graphics, just to try it out and make adjustments. Once you're happy with the geometrics you move on to the graphics phase.

In the tile editor, you can place objects that correspond to the level you've already made. Here I think it's going to switch to mouse control, it would be too tedious otherwise. So you look at your level and place tiles, but you're only editing the appearance of the level, it will still function exactly like it did when you tested it. Right now you can decide if a tile will be smooth concrete or rough rock, but there'll be much more to that as I start to produce some actual graphics.

Then there's the effects editor. Here you add plants and the like, it'll make sense to you when you see it (or I describe it in more detail later). Essentially it'll be stuff that grows on/hangs from/is applied to the tiles you've placed earlier.

After the effects are applied you'll move on to the exciting procedure of staring at light being raytraced for two minutes.

Finally the level is rendered and can be saved.

With the art editor I'm struggling with a balance, on one hand I want the editor to be free enough to make the level look like you want it, on the other hand I want it to be somewhat constrained. This is because not all people are artists, and you should be able to make a level that looks better than you would've been able to draw free-hand. Also I don't want you to be able to make a level that strays too far from the game's general art direction. We'll see where on this scale of freedom/constraint it finally ends up.

JLJac on April 16, 2012, 07:30:14 AM:

Update 24
I'm alive and stuff is happening. The stuff that's happening is mainly level editor stuff though, and I don't really have anything to show you. Personally I find user interfaces the most hard/boring thing to do, and it's a lot of that going on in the level editor. The user interface is going to suck, but I don't mind too much as I don't really think of the level editor as an official part of the game.

It's also important to me that the level editor I release is the same as the one I use to make the built-in levels, I don't like the dummed down level editors that are included in some games where it's obvious that the developers had access too a much wider variety of tools. So, in conclusion, the level editor is becoming ugly and hard to use, but it's more of a development tool that I'll also let you guys play with than an actual part of the game. I might include some kind of little tutorial on how to use it, though.

In other level editor news the tile editor is up and running, even more so than before. It works, it displays little previews, it's fairly fast and easy to use and it doesn't have any tile sets to work with yet. Still, the boring technical parts are more or less done by now.

Damn, it seems the level editor is the new croc path finding... Well, if I'm ever going to arrive to the point where this dev log is going to flood with juicy images there needs to be a level editor to generate those images, so it's all good I guess.

Over and out!

JLJac on April 16, 2012, 11:27:44 PM:

Thank you!

Update 25
This is what the tile editor looks like:



Just to give you an idea what I've been working on lately. With the wasd-keys you can change tool and with the mouse you place tiles. All tiles are loaded from a folder on initiation, they require much less space as external files. The little dark square to the right is the tile's requirements. It shows what kind of terrain a tile can be placed on. Some tiles can only be placed on slopes, some require open air in the middle and so on. This is what I meant earlier, that you first create your level and then you're only able to change its appearance.

After you've edited your tile layout you'll move on to the effects editor, which I haven't started on yet. After that you'll move on to a light editor, which I haven't started on either, but that one is going to be fairly simple. Basically it's going to be about drawing a black and white image which determines where there will be light and where there won't. Then the light will be rendered.



During this process you can go get a cup of coffee...

Finally the level will be rendered in its final colors. Currently this looks like this, but I don't plan to keep it that way. This is still just technical progress, I've started thinking about the art but haven't gotten around to it.



Tiles come in two versions, "box" version and "voxel" version. The boxes are basically six textures, for the front and the sides of the tile. Those occupy less space on the hard drive and are faster to render, but are limited in what they can do. The "voxel" type are actual voxel structures, more or less, and can describe more complex three dimensional shapes. The fans or whatever in the above image are voxel structures. If you look at the close up you can see that they have another set of grates inside them. I needed the voxel format to be able to do complex three dimensional stuff like that.

Now this framework is set up, and it's possible for me to start working on the graphics!

On a completely different note I've been thinking about how the Croc will look visually. Hopefully I'll be able to show you something soon!

JLJac on April 17, 2012, 11:14:51 PM:

Update 26
I worked on the art today. Still don't have anything I want to show you, but I'm getting there. It's a lot of fun to work with the voxels, any three dimensional shape I can imagine I can create, and see with (decently) correct shadows.

I've been working on a system for palettes. Basically the goal is to convey both light and distance using as few colors as possible, which is not as easy as you might think, especially if you want to make the depth of the graphics justice.



The reason I want to have few, flat colors is because a level will be pasted together from hundreds of graphical elements. By greatly restricting the palettte like this I achieve three things:
1) Some visual harmony, with many many colors it would hurt your eyes
2) Color will mainly be conveying level information, decoration is its second purpose. For the sake of conveiance three colors is actually enough (Look at the level editor), so ending up at 15 colors would be hard to motivate
3) Maybe most importantly, flat patches of color blend together. If everything has its own color every splice between graphical elements would be visible. If there are fewer colors, however, there's a much greater chance that two neighbouring fields will have the same color, making the joints invisible.

Right now I'm at 8 colors, a number I'd like to reduce to 5.

JLJac on April 17, 2012, 11:41:32 PM:

Yeah, sorry, I should've said something about that... The way the game will be colored will be somewhat unconventional, but worry not, I do have a plan! Once I've been able to produce a screenshot, or at least a mock-up, I'll do the concept / art style reveal and things will start to make more sense. Or they probably won't, but there will at least be some cohesion to the insanity!

JLJac on April 19, 2012, 12:14:44 AM:

Update 27
Added glass tiles, which are in every way the same as walls except that creatures can see through them. It's fun to see the lizards spot you through a glass wall and then find a way to get to the other side of the glass. Don't know how much I will actually use this in the levels, but it'll be in there somewhere just to point out the divide between visual contact and path finding, showing off some croc intelligence. Possibly there'll be some level that's a maze of glass with only a few blocks of solid material, where you'll have to move quickly from cover to cover waiting for a croc to face the other direction.

JLJac on April 19, 2012, 09:50:45 AM:

Wow, those are some really cool palettes!

Thing is though, that the game will be pretty heavily stylized art-direction wise, using a more or less black and white palette. This is for artistic reasons that I hope will be more clear once I get more visual stuff up here. Talking of which, I did some pen and paper designs for the croc today! Also started to implement it a little bit, it now looks like a little sasuage moving around rather than three dots. A first few steps towards giving it an actual body!

Update 28
I stepped away from my computer a little and did some sketches for the earliest single player levels in the game. I think this is a reasonable way to start, because if I know what levels I want to make I can make art assets that fit those, rather than making a lot of random art assets and then trying to fit those into the levels.



Those are likely going to be the very first levels, but they are also likely to look different from this. These levels will teach the players the controls and the basic premiss of the game. I'm trying to do this as best as I can, keeping

in mind. I won't go into too much detail, but level 1 basically teaches you how your basic moves work, and level 2 teaches you the basic mechanics of A-creature/B-creature interaction.

The main thing that happened today, aside from all this, was that I split the level editor and the game into two different applications. It got too cluttered, and I also figured that this way I might be able to release the two separately. That way people who're not interested in making levels get a smaller file size, and I can also release them at different dates, meaning I don't have to polish the level editor to perfection just to release the game.

JLJac on April 20, 2012, 11:29:34 PM:

Yeah, the project is starting to get big, so stuff like that might be necessary o.0

Update 29
Created spawnpoints for the players, and tied in the system with player and croc spawning in the shortcut system. This is mainly a question of lazyness, as now I won't have to make separate animations for a creature entering its hole and a creature entering a short cut. Basically the spawn points/home holes are shortcut openings, but instead of leading to another shortcut opening they lead to an invisible little flag, saying "this is a bear spawnpoint" or "this is a croc hole".

The croc is becoming more and more animated, now it has a body and a tail. Legs next, or head.