[^2] [^3]

Bevy Scripting

Although Bevy doesn't directly support scripting, efforts are underway to incorporate it. This crate represents an initial attempt to enable scripting within Bevy's existing framework. It's important to note that this is a work in progress and not yet optimized or complete. As Bevy evolves, significant changes to this API are anticipated.

Why Use Scripts?

• Update your game mechanics without the need for re-compiling
• Encapsulating game logic in scripts paves way for modders to create custom content easilly
• Scripting game logic/UI in a simpler language broadens development accessibility to non-programmers on your team

Features

• Script management via commands
• Hot loading
• Support for multiple scripting languages
• All script bindings managed in one place (ScriptDynamicFunctionRegistry)
• Customizable event driven communication between bevy and scripts (on_update, on_init etc..)
• Automatically generated bevy bindings
• Documentation generation temporarilly on hold[^1]

Support

The languages currently supported are as follows:

Documentation

For examples, installation and usage instructions see our shiny new book

Bevy Compatibility

BMS generates code based on each bevy release, which is why we pin the patch version of bevy too.

Supported Platforms

[^1]: Due to the recent re-write of the crate, documentation generation as well as rune support are temporarilly on hold. They will likely be re-implemented in the future.

[^2]: the coverage does not include generated bindings.

[^3]: The crate strictly enforces no unwrap, expect, panic or todo's via clippy lints.