Yeh, maybe what I’m talking about now shouldn’t be put in the scripting bucket. But it’s definitely part of our modding system as a whole.

All I know is that we’d like to facilitate Punchy mods as advanced as Kunio-kun dodgeball.

I don't know what that game is so can't comment on it. I do know that rimworld and minecraft allow its level of modding level by having mod hook directly into the code. No API just abusing reflection to sometimes rewrite entire parts of the game 😅

I don't think you will be able to get to that level of advanced mods unless you make the game compile to .NET bytecode or similar 😅

Yeah, I was thinking about WASM modding a little bit. Technically we can kind of already do it by compiling Rust to WASM and then loading the WASM from a JavaScript mod, I think, but that's not going to have the best user-experience unless we streamline the process more than we do now.

As far as "infinite power" scripting in Rust, I think you could do that on native if with dynamic linking eventually, if we can get around the rust

TypeId

issue. Essentially we'd have to use

TypeUuid

everywhere in Bevy that we currently use

TypeId

, I think. There was a little bit of a discussion about that very early on in Bevy when they were loading plugins as dynamic modules, but found out that it wasn't really viable yet until we fix the

TypeId

issue, but there could have been more discussion I haven't seen yet, too.

I think that's a little ways away, but I think that there are people who will be trying to make that happen in Bevy eventually, if they aren't already.

--- I think if we wanted a pure WASM scripting API, we could get that working similar to the JavaScript API we have today, with some caveats:

- It wouldn't end up more powerful than JS scripting, it might just be more performant.

- It also might not end up more performant on Web because it'd have to go through JS, unless we get some kind of WASM linking working, but WASM linking or linking alternative proposals are still work in progress I think, so I'm not sure if that's usable yet.

---

Anyway, as far as wanting super advanced mods, I think our scripting API will allow for some pretty advanced stuff when it's done.

Even designing alternative damage mechanics and guns and bullets, etc.

At least that's the goal. It should be almost as powerful as Rust, the limit may end up being more performance, than anything else once we finish adding lots of the dynamic APIs to the Bevy ECS.

At least as far as gameplay. Obviously hardware access is limited, but that's a good thing for most mods.

Yeh I really like what we’ve got. We can leave the wasm-scripting experimentation to others for now.

I haven't been following it super closely but it seems like from what I have seen people have been having significant challenges with a pure wasm scripting/plugin/modding API

or like it hasnt been as simple as one would hope on the surface

but it seems like something multiple projects across rust ecosystem are all working towards

👆 Holler when you’ve seen this @Pit

It’s up to you whether we try this out on bomby or do something else.

I'm in favor of trying this out on Bomby. It seems like an exciting step towards more fishfolk coherency and the scope of Bomby makes it ideal for experimenting with this, I think. Let me know what I can do to help

Awesome!

Just continue as you were for now. Zicklag can reach out to you on #bomby or the repo when he’s ready to move this forward.

Perfect! There's definitely some independent experimentation to do for the minimal ECS and WASM execution, along with the Jumpy MVP I'm trying to get finished first, but I'll absolutely let you know how things go along, and when we'd get to collaborating on it.

Could this work in this new WASM architecture? https://github.com/ceifa/wasmoon

That might work.

Right now the open question has to do with how to share the WASM memory between multiple WASM modules without them stepping on each-other's toes.