emerald VS bevy_webgl2

[dependencies] emerald = { git = "https://github.com/Bombfuse/emerald", branch = "master", default-features = false, features = [ "physics", "aseprite"] } inline_tweak = { version = "1.0.8" } futures = { version = "0.3.18", optional = true } lazy_static = { version = "1.4.0", optional = true } flume = { version = "0.10.9", optional = true } bytemuck = "1.7.3" steamworks = { git = "https://github.com/Bombfuse/steamworks-rs", branch = "master", optional = true } image = { version = "0.23.14", default-features=false, features = ["png"] }

Now for the rusty bits, the game is written on top of Emerald which is built on top of various rust gamedev libs. This community has been amazing and extremely helpful throughout the development process, I wouldn't have gotten this far without you, thank you!

Here's another one: https://github.com/Bombfuse/emerald

Emerald engine that aims to be cross platform and can target WASM. Emerald is built over miniquad which is what macroquad is built over.

Emerald: This is a recent game engine that uses miniquad and kira for audio.

Been working on this for a few months, the game is built on top of Emerald, a game engine I'm writing to be as portable as possible. Wishlist the game on steamto be notified on release, aiming to release sometime this September!

There was a rust game jam in September 2021 and some games are playable in the browser. In that game jam the most used game engine was the bevy game engine. But most of the games made in bevy were not made playable in the browser, the ones that were playable in the browser used a third-party bevy plugin called bevy_webgl2. However now bevy has been updated to version 0.6 that has new built in WASM support, so there seems to be no need for bevy_webgl2. Targeting WASM with bevy might mean that not all features of the engine are available, so you need to limit the game’s features used to the ones that are compatible with WASM.

For web assembly there is the unofficial bevy_webgl2 plugin. Official bevy web assembly support would probably use the wgpu webgl backend, which still needs some work, and is currently untested in bevy.

Thanks to bevy_webgl2, this is actually very straightforward. I just need to add the plugin WebGL2Plugin and disable the default features of Bevy to only enable the one available on Wasm.

Bevy has bevy_webgl2, which is supposed to enable a way to compile bevy for wasm and consequently run in a browser.