What if, instead of a mad scientist as the villain of a game, you had one as the developer?
Looking at the scope and design goals of this project, it feels like it really should have the "Joke / April Fools" tag. Looking at the actual execution, it becomes obvious that it really should not.
The Boom game, in particular, seems to be a complete software-rendered 3D game implemented in typescript, transpiled into Lua, and rendering to [png: texture modifiers; the fact that it actually runs at all on my laptop from 2012 is amazing. Bit's Battle demonstrates that it's not just pure tech demos that run in this environment, but games with actual gameplay and progression, albeit only a rudimentary amount as implemented so far.
To enjoy this "game" to the fullest, it helps for a player to understand the spectrum of games that have been created in Minetest, and understand how much this is abusing the game engine to make it possible. It feels like something in the same spirit as arbitrary code execution in NES games. Rather than being "immersed" in the experience, it sort of demands that you remember that this is all running inside Minetest. There's not a ton of depth and it won't keep you occupied for hours (especially if it crashes MT in a few minutes; I don't know where the "B" in "BOOM" comes from, but I know where the "OOM" does) but it's a spectacle worth witnessing.
What if, instead of a mad scientist as the villain of a game, you had one as the developer?
Looking at the scope and design goals of this project, it feels like it really should have the "Joke / April Fools" tag. Looking at the actual execution, it becomes obvious that it really should not.
The Boom game, in particular, seems to be a complete software-rendered 3D game implemented in typescript, transpiled into Lua, and rendering to
[png:texture modifiers; the fact that it actually runs at all on my laptop from 2012 is amazing. Bit's Battle demonstrates that it's not just pure tech demos that run in this environment, but games with actual gameplay and progression, albeit only a rudimentary amount as implemented so far.To enjoy this "game" to the fullest, it helps for a player to understand the spectrum of games that have been created in Minetest, and understand how much this is abusing the game engine to make it possible. It feels like something in the same spirit as arbitrary code execution in NES games. Rather than being "immersed" in the experience, it sort of demands that you remember that this is all running inside Minetest. There's not a ton of depth and it won't keep you occupied for hours (especially if it crashes MT in a few minutes; I don't know where the "B" in "BOOM" comes from, but I know where the "OOM" does) but it's a spectacle worth witnessing.