I haven't used Flame engine, but I know it already exists as a way to make games in Dart. So, if someone like me is curious about making a game in Dart, it would be nice to know the pros/cons of using this versus using Flame.
Maybe remaking Flame's Klondike tutorial, or one of the others, using Bullseye to help show the distinct advantages that this engine brings over other solutions? It's not very obvious to me when this would be the right choice for me over Flame.
Nevertheless, it's cool to see something new come to the scene for game dev in Dart. Thanks for making this!
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).
Was it not before? The only parts I've not enjoyed in the past has been working with a team that didn't pull their weight. What part of this makes it fun again?
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.
This is promising. I just did a review of some of the code and the premise of the platform, this is clearly not your first rodeo in gaming. I wish you luck! I might consider sponsoring as well.
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.
Nevertheless, it's cool to see something new come to the scene for game dev in Dart. Thanks for making this!
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).