Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Hey Lumina! So glad you wanted to reach out to me. I've gotten a lot of questions as to how the game itself is programmed, but I haven't had the time to make a detailed walkthrough of how everything works. We're still changing things around and adding new features, so the code base is a little messy at the moment.

Basically how the game works is that there's an ENUM (enumerated list, where every entry has a constant value) that contains every state the player could possibly be in. This includes things like being Idle, crouching, attacks, getting hit, getting up, intros, etc. On each frame, the game uses a switch statement to process the code that correlates to each state. This allows states to have their own logic that's separate from other states. Some states like Idle, Crouching, and Hitstop are processed outside of the state machine, since doing so inside the machine would cause 1 frame delays between player input and game action.

That's a bit of an oversimplification of how it works, but that's basically the gist. 

Here's an image of the code. the states themselves are collapsed to show how many there are, as some states can have quite a lot of code.

As for contact, here's my Discord if you wanna inquire further. jazz_boy (originally jazz_boi#6109) Hope this helps! Sorry it took a bit for me to respond.