Concord
Concord copied to clipboard
A feature-complete ECS library
This example should say: ``` -- Retrieve all Components -- WARNING: Do not modify this table. It is read-only local allComponents = myEntity:getComponents() for ComponentClass, Component in pairs(allComponents) do --...
The current documentation for assemblages looks like this: ``` -- Make an Assemblage function -- e is the Entity being assembled. -- cuteness and legs are variables passed in function...
The current concord docs are not enough for first time users of ECS. More examples would be great which showcase simple games being made using concord. Can you add a...
Add examples on how to use the different parts of Concord. Some of these already exist in the README but could see some improvement with in depth explanations, for example,...
A common requested feature is a way to store Entities (or references to Entities) inside Components while keeping the data serializable. That is, the next startup the Component data can...
This function would allow you to define a callback that would be called before an event is emitted. This is really useful for debugging event delegation. This callback would get...
This function would allow you to `:give` or `:ensure` a Component directly from another Entity. Meaning all the data would be cloned over. The cloning mechanism would rely on `:serialize`...
Sorting Pools before looping through the Entities could be useful for rendering and collision checks. The feature can be easily added to Lists and Pools would inherit it. I have...
The idea is that Pool Filters should be able to reject an Entity if it has a given Component. I already have this working in [`a00ee08`](https://github.com/pablomayobre/Concord/commit/a00ee0821d83ff183baf863260f759c3b63522a5)