makspll / makspll/bevy_mod_scripting
Auditing Determinism in BMS
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 649
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
Making BMS deterministic
Blanket issue for determinism issues within BMS
Spawned off of discussions in the discord.
Currently BMS is very likely not deterministic:
- queries for entity script components will not be deterministic as they don't use the ordered versions of bevy queries
- we store various bits of state in
HashMap's which will have non-deterministic retrieval between machines - the order in which the asset server loads scripts will affect in which order they are executed too
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 by auditing BMS entity-script queries, HashMap state, and asset-server script loading, as identified in the issue. Done means establishing deterministic query, state-retrieval, and script-execution order across machines; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- game-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100