Very sorry about that :( Thank you for the description of the problem, we'll look into it.

Glad it sparks your interest!

Yaaaaay!

It has been a pleasure and liberating experience to work on a cool concept that is neither a big project nor a game jam thing.
Shoutouts to @camillecee.bsky.social, @msvk.bsky.social, and @vinz120.bsky.social for their time and input! Thanks a lot <3

The concept was to build a tightly-scoped turn-based strategy kick centered on small grids, an even smaller number of units, and a reactive system centered on a single action: pushing other pieces around. It's all about the chain reactions!

It doesn't matter if you know your chess rules or not: this is a chaotic, knockout-style version of chess in which you BUMP other pieces to PUSH them out of the board!

It is, really helpful in that instance. Thanks for the kind words!

After some dev stuff, the resulting bump chains went kind of crazy. It may be a little too much for the serious tactical value of the game, but it’s fun and it speeds up the game. So we’re going to try that.
Chessbumping is the name of the game and is going to be a free web game. Stay tuned!

Overall, “cool idea, but not chaotic enough” is what we gathered and one possible solution was to double down on the bumps and chains. We were already planning to add walls at some point, so we put the focus on increasing the bops!

So yeah, the Carmelina Script is an important tool for MMS; it controls the different aspects of the game and put them together to tell a story. But obviously, this is not the only thing there is. So, see you next week for a different subject!

Setting when, where, and how dialogs and characters are displayed, managing text effects, setting different visual and audio effects, controlling and checking story flags, altering the player's resources, launching scene transitions, activating the town map, starting fights, enabling encounters, ...

Overall, the script is written in big flat text files containing events. Every piece of scene and dialogue is an event. Events are uniquely identified and branch to each other, building the narrative flow. And besides containing the actual written content, events are responsible for a lot of stuff:

I think we made a good choice; while I worked on the core of the script engine for LtD, Camille worked on everything else. And we mostly kept that methodology when we started to beef up the system’s capabilities for MMS.

That’s some true happy ending right there for your Sunday. See you next week!