Crimson

Crimson Used AI

9 devlogs
42h 1m
•  Ship certified
Created by DoMax

A simple and powerful 2D game engine designed for learning game development fundamentals. Built with modern C++ and focused on providing an easy-to-understand API that doesn't hide the underlying architecture.
Crimson's focus - simplicity and learning game development at a lower level with an intuitive API.
Crimson's purpose - passion to understand low-level game engine architecture myself, and to provide an open library for the community, requiring no licensing fees and providing true cross-platform compatibility for simple 2D game development.

Timeline

Added a randomizer utility using which the ball can bounce off at random, making the OutBreak sample game more entertaining.
Brightened the background of WASM builds' unsupported system error page.
Added filename hashing for WASM builds, avoiding browser and Cloudflare cache on new build releases.
Made GitHub actions and Docker builds use this advantage.
Updated README and configuration for easier, more predictable and cleaner building approach.

Update attachment

Ship 1

1 payout of shell 572.0 shells

DoMax

about 1 year ago

DoMax • Covers 8 devlogs and 37h 41m

Added simple prevention of mobile usage of built WASM games as the engine is not yet compatible with mobile games, just as the demo.
The demo can be played on desktop browsers using arrow keys. More at outbreak.domax.lt
Also added credits for the ball asset.
Crimson Demo is finally released! To check out all of its capabilities, read the README.md and try creating a game yourself! ;D

Update attachment

Implemented game centering to OutBreak, removed Crimson demo game I used for testing and added Docker build support so I can easily host the WASM demo game!
Added a texture for the ball.
Made a GitHub action for OutBreak's Docker build.
Updated the README so it's more clear on what to do with this engine.
Fixed scripts so they work as expected too. Crimson is finally a full-on game engine ready to be developed with!

Update attachment

Finally added a demo game - OutBreak!
Fixed MANY issues with collisions:
- Too agressive transform and collision component integration with each other ended up often blocking initalization.
- Redefined API, and now game dev chooses when to block and when to not using transform component manually. Collision component provides only calculations.
- Implemented more features to the collision system, like normal and hit point vector calculations which help when developing something like OutBreak - where accurate normals can be used to calculate how to bounce off of objects.
- Made map collision tiles be lightweight entities for easier collision integration and later manipulation.

Also made multi-game builds possible:
For WASM:
- Each game has its own sandboxed subdirectory under build-wasm/bin/{config}/{game} with index.* files ready to be hosted.
- Each game links everything in statically and is meant to be hosted separately.

For native builds:
- One unified launcher, built with a game selector (with the help of wxWidgets) lives under build-native/bin/{config}.
- Each game is under build-native/bin/{config}/games/{game}, where its DLL and data are stored.
- The game launcher knows which games are valid based on game's Manifest presence under config/Manifest.json.
- When launching the launcher, it lets user select which of available games to play. This was done to avoid having a hardcoded game target into the launcher, adding the ability to mod and freely create many games using Crimson.

Removed a LOT of legacy code, introduced more utils and components to cope together with OutBreak and more games in the future.
Crimson is really close to its first ship. Remaining things post-ship are:
- Tweaks to the OutBreak demo (visual and game loop upgrades that make the game more exciting) (might do this pre-ship and sip the OutBreak game with tweaks already made for an exciting gameplay experience).
- Docs and UI systems (this engine lacks these still).
- Nothing more? Maybe bug and convenience issue fixes (if any are present).

Update attachment

Finally - a good entity and map collision system, taking advantage of LDTk's (map editor's) intGrid feature and existing ECS.
Made it customizable with future-proof structure and architecture, for further implementations from me and other devs.
Implemented easy to understand development cycle - components do their job alone, game devs not having to DIY the built-in systems (unless they want something extra).
Updated entity systems as well - added initialization to components on addition and made entity scripting in their own files possible, instead of implementing them in a level script - fixed scene lifecycle, which prevented such things.

Next steps:
- Demo game for a ship (I'm thinking about an Atari Breakout clone).
- Docs.
- UI system (maybe?).
- Nothing else, at least for SoM I have planned, regarding Crimson. Maybe more simple demos (like Flappy bird or Space Invaders clones, remade purely in Crimson). Most likely I'll just start a new project and leave Crimson for people to use, maybe use it in a game jam.

Update attachment

Made some real fancy advancements since the last devlog:
An entity component system.
Subtle refactoring and clearer API for game developers.
A better and fixed way of creating new games - now Crimson comes with a sample game generation script, which is the best way to start.
It's starting to become more and more like a game engine ready for games, than a DIY project.
Best thing is, with the new ECS it will be easier for me to implement a collision system and complete a few web demos.
Next steps:
- Collisions (of course).
- Docs (similar to EchoTuner's).
- None, unless someone who actually ends up using Crimson for their games begs for extra features, like particle and lighting systems, or even a working sound system (hasn't been tested yet).
The engine now supports dual-configuration builds. Current testing went smoothly, without much issues or bugs.

Update attachment

After about a month of forgetting this project and focuding on EchoTuner, I have finally decided to get back - and with good news!
WASM support is fully implemented! A bit sloppy, but not for long.
Crimson engine now supports standalone windows and linux builds, as well as WASM web builds, making it very easy for me to ship a demo!
Wish me luck and wait for the full release!

Update attachment

Added a sound system for reference, might expand it later to account for physics and collisions in a world.
Implemented a better and less-repetitive init point.
Updated cleanup for engine core accounting for audio.

Update attachment

Implemented a new way to add a player to the scene! (Or any other entity, really)
Instead of having to manually set the position of an entity, now everything's possible through the same level editor used to edit levels!
Crimson's going to shift towards adding sounds, collisions and UI systems for better developer experience. After that, Crimson's game building itself awaits!

Update attachment