(2026-03-02) New Landing Page!

I’m really not a webdev dude and it shows lol, but we got a new landing page now! The previous one looked “unique” (better on my screen in my defence) to the point I’m being cited as a part of the “anti-design” movement. You can’t take the artist out of me it seems.

This solves a few problems around communication, the first being that most progress was not really accessible unless you were already in the community. This shows how active the project is a bit better! It was also a bit tricky to keep up with the weekly video, and until its quality improves I believe it’s not currently worth the effort of translating them. So instead of having to spend big time every week, this style of short update is probably better? I was already doing it before, so it’s not like it takes much. Might be able to rig it to videos too, once I improve my pipeline a bit.

One of my next objectives is to move the Castagne community towards this website. Discord was a useful crutch there, but information easily gets lost, and it becomes more walled over time. This is going to happen slowly, as I also want to develop the engine, and being currently mostly a solo thing that means I’m already pressed for time lol. But this is a priority, as my gambit to develop a full engine in 3 months didn’t pan out as fast as I hoped so I’ll need to switch gears into more paced and clear development instead of a short intense period. I’m still very satisfied with the project’s progress, and you can see how many features are already in on the page.

This doesn’t change much my plans, except that March might be filled with more “admin” and “surrounding” work rather than pure programming, but it might make more people aware of the engine, which is nice! My next programming steps are going to be structured types (especially vectors) and either the physics or graphics module. Input already works, so this is some of the last steps to make the engine usable. Knowing the extra features coming, I can’t wait to port my own games to it!

(2026-02-24) Input Works!

Quick preview of changes:

• Input layouts are a bit heavier handed now and don’t customize the name as much, which prevents many beginner errors
• The main stick is now separate from stick, because it has much more assumption built in for motion and the like.
• Multiple type inputs are a bit more generic and can be derived, or depend on derived inputs.
• Derived inputs have been split into the new input events system, which enables a bunch of stuff. (No derived inputs yet as the main ones rely on physics)
• Input events now replace the Press/Release thing, any input can have input events and they linger for a bit until explicitely consumed. This makes input much cleaner and reliable. It’s more KOF style, which is think is the best implementation.
• Some extra events like DoublePress, or motion inputs, can be added in the future
• Interface supports multiple inputs per frame, although I’m not sure I want to keep this? food for thought.

The syntax is a bit different, check this:

# Assuming L is a button
IL: # Is L currently held down ?

IL.Press: # Is an L press buffered ?
# The buffer lasts around 8f at the moment, and is unbuffered if released
# If going into this branch, the event is consumed.

IL.Press?: # Same as previous, but doesn't consume the press.

(2026-02-17) Inter-Entity Communication

I’ve worked a bit too much today to finish the CHECK in time lol so I’m giving a real quick preview

• Targetting works ! And it’s robust and now properly handles the delay. You can also now read variables from nascent (= yet to be born) entities.
• As a simplified reminder: reading gives you the variables at the start of the frame, writing is done at the end of the frame. Subentities have a faster pathway.
• Variables from targets are much easier to access using Target.VariableName, peep some examples:
  • Set(V, Target.V): Copies the value of V from the target inside of our own V.
  • Set(Target.V, V): Writes the value of our own V into the target’s V.
  • AttackDamage(Target.HP): Makes an attack that does exactly as much damage as the target has HP, killing him instantly if it hits!
• As dev starts to take longer and my other commitments are arriving sooner than expected (PhD as you may guess), I’ll be switching some gears for better communication !
• I’m likely going to ask for help on some stuff soon-ish! Some stuff around the engine, some stuff more on research on existing fighting games. Be ready for that!