joemanaco

What happend: The game publisher System 3 has released a trailer for a new Legacy collection of James Pond games. The trailer was full of AI slop. After backslash in the comments (where Systen 3 claimed that NO AI had been used at all), they published a blog post showing how they created everything by hand. It’s just hilarious.

I don't have looked into Flame too much, but I would say the main difference is that Flame builds on top of Flutter while right now Bullseye2D only builds on the web package.

Flame offers more out-of-the-box features, while with Bullseye2D you have to build many things yourself, but it doesn't force you into a predefined structure as much. The API is more prodcedural style, making it relatively quick to learen in its entirety, without too much "magic" happening under the hood.

I think for most people Flame would be the better choice (it is also been around longer, which means better support...), however, I really love extremly simple approaches. I also believe it has advantages when you tailor your systems and architecture to your own requirements. Lots of stuff in 2D Game Development is also extremly simple (so often having to deal with a complex physics module or rendering pipeline or entity component system is contraproductive).

You're right. I fixed it ;)

Yes, maybe it's a stupid thing to say. My thought was that the simplicity of the API takes out a lot of the complexity of it compared to engines with complex structures, entity hierarchies, event systems and features that need to fit a wide range of genres. Especially if you want to make something simple or just a prototype.

Thanks. Hearing that from someone who works on Dart and wrote two books I’ve read makes the compliment really special to me :)

Thank you.

I ported this game from the Book "Code The Classics" which was written in Python/PyGame. It should be relativley easy to add mobile touch inputs to it, but I didn't have time for that yet.