SeanOMik
/
lyra-engine
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity
lyra-engine/lyra-ecs
History
SeanOMik 4c0b517127
Implement despawning entities 		2023-12-21 23:33:36 -05:00
..
.vscode Create queries and views 2023-12-21 23:33:32 -05:00
src Implement despawning entities 2023-12-21 23:33:36 -05:00
.gitignore early version of ecs working 2023-12-21 23:33:18 -05:00
Cargo.lock Implement despawning entities 2023-12-21 23:33:36 -05:00
Cargo.toml Implement despawning entities 2023-12-21 23:33:36 -05:00
LICENSE early version of ecs working 2023-12-21 23:33:18 -05:00
README.md Implement despawning entities 2023-12-21 23:33:36 -05:00
shell.nix early version of ecs working 2023-12-21 23:33:18 -05:00

README.md

Lyra ECS

An ECS for the Lyra game engine.

Why does it exist?

I couldn't find anything that fulfilled my needs, specifically an ECS that can store arbitrary components without knowing about the types. This makes it easier to implement into a scripting engine that has the ability to create its own components.

Features

  • Archetypes
    • Spawning entities
    • Despawning entities
      • Delete entities from archetypes
      • Find some way to fill in the gaps in component columns after entities are deleted
        • This was done by moving the last entity in the column to the gap that was just removed.
    • Grow archetype as it fills up
    • Borrow safety of components inside Archetypes
      • Its wonk right now; a component can be borrowed mutably from a non-mutable reference.
  • Querying components from archetypes
    • Views
    • Mutable views
  • Resources
  • Relationships (maybe this can be done through queries, idk)
  • Dynamic queries
    • Needed for scripting engines that can create their own components that Rust does not know the types of.
  • Systems
    • Dispatchers/Executors

To be honest, the name may change at some point