makspll / makspll/bevy_mod_scripting
ScriptCallbackEvent is actually a bevy message
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 649
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
Bevy has clarified the difference between a message and an event therefore making the name ScriptCallbackEvent missmatch its derive.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in crates/bevy_mod_scripting_core/src/event.rs at lines 199-201, then search for ScriptCallbackEvent references across the repository. Align the name with Bevy's message terminology and update its references; done means the project still compiles with the renamed message type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- game-dev
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100