The core idea is simple: entities are observable objects, and systems are plugins. An entity holds its own data, behavior, and events — a position, a sprite, a collision handler, a Solid component — and plugins subscribe to the parts they care about. Physics doesn't know about rendering. Rendering doesn't know about physics. Swapping Pixi for p5, or adding Matter, means changing the plugin list with minimal modifications.
State management is handled using my own universal state management library Jabr, which has no ecosystem lock-in — unlike most state libraries, which tend to be tied to a rendering framework like React or SolidJS. That makes it a natural fit for fusing the domains of web development and game development.
The design leans functional rather than object-oriented. Composition is declarative, systems are external functions over shared state, and capabilities are added by declaration rather than inheritance. The entity model itself is closer to a scene graph than to ECS — entities are real objects with identity and lifecycle — but the way logic composes borrows from ECS: systems are external, and every part of the engine was built for separation of concerns and interchangeability.
The same core runs many demos on the site — a platformer with Tiled maps, Matter physics, and a Solid UI, and a two-player Pong game rendered with p5, and many other demos. The renderer, the physics engine, and the game logic are all plugins and entities. None of them import each other.
Grandparental Controls is the first full game released with Lili's Game Engine — published on itch.io.
How your grandparents describe trying to use a computer: A chaotic physics game that got completely out of hand — but don't hit your life alert just yet.
You're babysitting a screen full of troublemakers: captchas, wordles, minesweeper boards, tic-tac-toe, and mazes with their own tiny physics simulations running inside them. Solve them before the timer runs out and you'll earn rewards. Fail, and the game throws TNT, homing missiles, and gravity-flipping chaos at your precious little hearts. Lose all your hearts and it's game over — but the high score board remembers everything.
- 5+ minigames, each with its own timer, sound effects, and win/lose consequences
- Physics everywhere: drag, stack, knock over, and watch everything tumble
- Rewards like hearts, shields, coins, piggy banks, and more
- Punishments like TNT, gravity modifiers, and heat-seeking missiles
- Multiple difficulty levels, from a chill sandbox to full chaos
- Creative mode with an admin console so you can spawn anything you want
- High scores for every difficulty — how long can you survive?
It's silly, it's stressful, it's satisfying. Welcome to why your grandpa can't read his email.
If you'd like to have some fun and see what the game engine can do try playing with the demos!
Some of the demos include:
- Pong using p5.js and MatterJS (Source)
- An interactive space themed satellite motion simulator (Source)
- A top-down zelda style game using the Tiled editor (Source)
The main demos can be viewed on the website's demo page (a fun place to start), and the full list of demos can be viewed in the project's source code
To begin using the game engine it is recommended you install the command line tool (though not mandatory):
npm install -g lilis-engine
Once that's done there are a variety of demo projects for you to toy around with. To view the list of available demos use the "create" command without additional arguments:
lilis-engine create
To learn more about any of the available demos use the "info" command with the demo name as the first argument, like this:
lilis-engine info topdown
Once you've decided on which demo you'd like to try out you can use the "create" command, with the demo name as the first argument and your project name (no spaces) as the second command:
lilis-engine create topdown my-zelda-game
If you'd like to view the full list of demos in your web browser as well as view their source code try visiting the examples directory in the engine's source code.
Please note that all of the example projects are made using SolidJS for interactive HTML and Astro as the website framework. While these tools are not mandatory for the game engine to run learning the basic of using them will help you greatly both in understanding the example projects' source code and in building web based games & apps going forwards.
If you'd like to see a minimalist version of using my game engine without using Astro or Solid consider checkout my vite-minimalist demo (source code here) which uses only two small files to define the project's source code.
You can learn how to use this engine by visiting the documentation!
This game engine has a number of built in integrations for common game development libraries, for example:
- matter.js (physics)
- P5.js (rendering)
- PixiJS (rendering)
- Tiled map editor (tile map support)
One of the core features of this game engine is that adding support for new libraries is very easy. If there's a library you'd like to add support for consider making a pull request or opening an issue.