Our scripting api is one of the cornerstones of this engine. A core unifying layer.

Channels are now connected!

test

good to go

Ah, what's this channel for?

> 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/ pasted erlends last message

Ah, I see.

I think its meant to be something like the fish folks/spicylobster engine built on top of bevy, with the scripting youve been working on

I was thinking about that a little bit ago, and wondering whether or not even Punchy and Jumpy might end up eventually being able to merge into a single engine with different assets and scripts.

It's not necessarily something we should try to do, but it might just kind of happen, if it makes sense.

The merging of them, I mean.

surely at least some parts will have overlap

Otherwise we just end up with a kind of shared framework, like you're saying.

Exactly.

idk how much it makes sense to intentionally merge right now but 🤷‍♂️ I imagine we will figure out more about whether that might make sense as we progress

That's what I was thinking.

I've run into the issue of premature abstractions before, and I'm finding out that you often want to start making a little bit at least before designing abstractions.

Then we'll get a feel for what can actually be shared or not between them.

yeap totally makes sense to me

I think we can probably leave it as a known open question + keep it in mind as we continue

👍

Now that the scripting mvp is merged, here’s an interesting wasm exploration to keep an eye on and maybe get some inspiration from: https://github.com/bevyengine/bevy/discussions/5908 https://github.com/afonsolage/wabi/discussions/1

Also fyrox talks about the latest iteration of its scripting system here: https://fyrox.rs/blog/post/feature-highlights-0-28/

do keep in mind that Fyrox' "scripting" is programming in Rust which gets statically linked to the rest of the game. Not exactly the same thing as the TS thing that got setup

Yep. I’ve been wondering to what extent we can also support ‘Rust scripting’ as an alternative to the JS/TS approach.

depends on what you define as scripting I'd say 😅

Something akin to Godot’s GDExtension, except it’s just Rust.

because, personally what Fyrox calls scripting isn't what I would call scripting....

Yeh the semantics are a bit tricky to nail down.

for me, scripting would be about quickly doing small things. Like making a bullet pattern for a gun not, create the entire gun, the bullets and the damage mechanic from scratch 😅