or something similar

You could do what bevy is doing and make your own UI that you dogfeed

Yeh. Our UI strategy is game-centric anyhow, as opposed to engine-centric and general-purpose.

We will build game-specific editors. Whatever general editor experience those editors have in common will reveal itself organically.

that is an option. I am not that familiar with Miniquad but it would have to be using this, if so, as macroquad doesn't really give enough low level access, as far as I know

would have to work directly with opengl, if so, I believe

I c

This is the UI lib that is most likely gonna be the new default for Bevy:

In the far future we might look into making rendering backends pluggable, though, to allow more freedom with UI, as well as support for vulkan etc

Mhm. All post v1.0 stuff for sure. What we’ve got right now will remain Good Enough for a good while longer.

yeah, for sure. Depending on what happens in the future, project-wise, I can look into this. I have experience with both opengl (lots) and vulkan (some/rudimentary)

would love to do a renderer at some point

making a batched 2d renderer, like the one MQ uses, in opengl, is relatively easy, though

already made that, many times, in C++

Don't all 3 of those perspectives function the exact same way anyway? :p

Just an artistic choice rather than gameplay difference.

Mostly just tile based overhead maps.

Some with the first style put the sprite to the top part of the tile to give it more depth when at a wall, so the wall is actually behind you.

yeah, they do. Same with overhead vs platformer; just a matter of toggling y-axis movement and gravity

if y'all ever switch to Emerald let me know, would love to be able to support you guys on the engine level!

will do!

is changing from macroquad to emerald something someone is working on?

would be curious to follow the progress if it is

No, we aren’t gonna do that as we’ve got an equally mature engine of our own. But maybe we’ll collaborate on some shared libraries together.

yeah, though it seems more ergonomic than plain macroquad in some areas, I think it is better for us to focus on making a pluggable rendering backend, if we are to make such a massive change at some point. We really just use file loading, keyboard input and render calls in macroquad, as well as ui, for the time being and have made our own API for most other things

after seeing what it’s capable of w/ docs… that would be A++ absolutely to have w/ the fairly large Lua API surface heavy has/will have

The fishbones toolkit?

Since our custom engine is no longer happening, what we’re actually building towards with Fishbones nowadays is some sort of Bevy meta-engine.

Basically what Corgi is to Unity: https://corgi-engine.moremountains.com

@odecay can you give zicklag access to this one as well?