Bevy Remote Protocol has so much potential and soon it could have even more 👀 I am getting closer to getting JSON Schema exports for types registered in Bevy Registry. I took the great work of @crobocado for #blenvy and standardize it a bit and make it work with the BRP. Here's the PR: https://github.com/bevyengine/bevy/pull/16882

If I make it into main next thing I am going to do is get BRP a OpenRPC support so it will be easier to generate bindings to other languages.

#bevy #rustlang #indiedev #gamedev

BRP registry JSON schema endpoint by Leinnan · Pull Request #16882 · bevyengine/bevy

Objective Resolve #16745 Solution Provide a way to map AppTypeRegistry types into a JSON Schema that can be used in other applications. I took code from https://github.com/kaosat-dev/Blenvy as a st...

GitHub
Been very sick for weeks now, so progress is sluggish, but getting there.
More clarity & structure & improved Ui for levels & blueprints in the #blenvy #blender add-on for #bevy
- you can visualise & edit your per level assets
- you can also see the list of used blueprints per level
- added option to force systematic export of specific blueprints / levels
- in depth change detection is vastly improved & can even detect small changes to materials & modifiers (including geometry node trees !)

More work done tonight on #blenvy (potential name, not quite sure), the #blender tools for #Bevy
- improved UI & workflow for Assets: the per level/world assets are displayed in the assets tab
- since blueprints are a logical "unit" (ie reusable hierarchy of components, meshes AND their associated assets), the assets for blueprints & any other future data related to blueprints are under the "blueprints" tab

If you have feedback, remarks, criticism, don't hesitate !