Why post is named “GD: dev log #11” instead of “GD2D: dev log #11”? Because at the moment I develop two games: GD2D (only me, without others) and Fire Strike (code name: “Gloomy Dungeons Cartoon”), with help of Otabek Gulomov aka Leo, who redrawed from scratch almost all graphics from GD2 in cartoon-style.

I have not written anything for a long time, and this has a strong reason…

Continue reading

A brief summary of last two weeks progress:

• Debug panel to configure weapon;
• Show weapon in the HUD and ability to select weapon;
• Weapon selector screen;
• Many under-the-hood improvements.

Continue reading

This time I tried two things:

• Circle colliders on objects, decorations and characters;
• A little 3D.

Continue reading

I try to load big level, and found that FPS is super low. Time for optimization 🙂 I think of three things that can be slow:

• Colliders debug draw;
• Tilemap;
• Non-tile entities (eg. player, enemies, objects).

Continue reading

Starting from this post, I will write less technical details, because more and more code is written, and writing a detailed post may take more time than actually writing the code.

During this week colliders, opening doors and “actions” were added to the game. This week’s video.

Continue reading

Now I want to render level. This task consists of several subtasks:

• Output some random tiles from GD2;
• Read level from GD2, output it (just tiles, without objects, doors or enemies);
• Output objects, doors, hero and enemies (as they can move, they should be separate sprites, and not be displayed in the tilemap.);
• Add another camera (for level), move it along with hero.

Luxe already have built-in tilemap, so at first I decided to try it. I don’t found any documentation or examples how to use Tilemap directly, instead of every example of tilemap use TiledMap to load map from file.

Continue reading

This time it will be very small post. Did you know, that luxe engine has built-in debug console, that is enabled by default even in release builds? To reveal debug console, press grave accent key on desktop or simultaneously put 4 fingers on the screen on mobile devices.

While it is useful when debugging, I think that is should not be included in release build. To disable it on release builds (and leave in debug), add following to your project.flow:

if : {
    "!debug" : {
        build : {
            defines : ["no_debug_console"]
        }
    }
}

See you later!

P.S. If you know that the game is written using luxe engine, try to reveal debug console 🙂 Maybe game authors forgot to disable it before publishing.

Today I want to add initial support for Android and iOS devices. I want to handle hardware back button on Android, and handle onResume / onPause events both on Android and iOS (I’m not an iOS developer, so I guess it will be viewWillAppear / viewWillDisappear or applicationWillEnterForeground / applicationDidEnterBackground or something like that).

Initially I think that onPause / onResume will be the hardest part, but hopefuly luxe is based on show, which is based on SDL2 itself, and it handle these events for me.

Continue reading

Next what I want is to create several screens (menu and game), transitions between screens (simple fade in and fade out), add preloader with simple progress bar, output background image on menu screen and render some text.

Luxe has built-in state machine, but this state machine is tightly coupled with game lifecycle (eg. can receive onmouseup, onmousedown, etc.), what makes it sitable for screens and transitions between them. There are several examples which demonstrate how to use states properly.

But these examples have one “feature”…

Continue reading

This time I should chose tool to convert vector fonts into bitmap ones (with distance field support), than I should choose base screen resolution and render something on the screen.

I already know about bmGlyph and Glyph Designer, so I download demo versions and try them.

Continue reading