nonsensical-dev/zenyx-engine

Fork 1

ECS implementation design #7

New issue

Open

opened 2025-04-20 22:18:46 +00:00 by bitsyndicate · 2 comments

bitsyndicate commented

2025-04-20 22:18:46 +00:00

Owner

We need to discuss how to layout the ECS and before implementing it.

bitsyndicate added this to the ECS milestone 2025-04-20 22:18:46 +00:00

bitsyndicate added the

Priority

High

Kind/Discussion

labels 2025-04-20 22:18:46 +00:00

bitsyndicate self-assigned this 2025-04-20 22:18:47 +00:00

caznix was assigned by bitsyndicate

2025-04-20 22:18:47 +00:00

lily was assigned by bitsyndicate

2025-04-20 22:18:47 +00:00

bitsyndicate added this to the Zenyx project 2025-04-20 22:18:50 +00:00

lily pinned this 2025-04-21 19:44:31 +00:00

bitsyndicate commented

2025-04-30 20:48:15 +00:00

Author

Owner

I would opt for storing components independently of systems as described by the EnTT author¹ and then transition into the grouping sorting as described in the same blog post.

We would have to have some kind of structure that keeps sparse sets of components around as well as stores entity Id, trigger events for systems, and handles parallelisation.

What are your thoughts on this?

https://skypjack.github.io/2019-03-07-ecs-baf-part-2/#independent-sparse-sets ↩︎

I would opt for storing components independently of systems as described by the EnTT author[^1] and then transition into the grouping sorting as described in the same blog post. We would have to have some kind of structure that keeps sparse sets of components around as well as stores entity Id, trigger events for systems, and handles parallelisation. What are your thoughts on this? [^1]: https://skypjack.github.io/2019-03-07-ecs-baf-part-2/#independent-sparse-sets

lily commented

2025-04-30 22:22:35 +00:00

Owner

@bitsyndicate wrote in #7 (comment):

I would opt for storing components independently of systems as described by the EnTT author1 and then transition into the grouping sorting as described in the same blog post.

We would have to have some kind of structure that keeps sparse sets of components around as well as stores entity Id, trigger events for systems, and handles parallelisation.

tl;dr looks good just make sure that the nuances are sorted out.

I'm inclined to agree as systems and components serve independent purposes. Systems provide a method by which to interact with components and modify them according to external inputs and inter-system interactions. On the other hand, components store information related to one or more entities through sparse sets.

I think the bigger question is how should systems, hooks, and inter and intra-system interactions be handled? The way systems function and interact is paramount to the utilization of components later on and becomes a question of flexibility.

@bitsyndicate wrote in https://code.lilyvex.dev/nonsensical-dev/zenyx-engine/issues/7#issuecomment-198: > I would opt for storing components independently of systems as described by the EnTT author[1](#fn:user-content-1) and then transition into the grouping sorting as described in the same blog post. > > We would have to have some kind of structure that keeps sparse sets of components around as well as stores entity Id, trigger events for systems, and handles parallelisation. > tl;dr looks good just make sure that the nuances are sorted out. I'm inclined to agree as systems and components serve independent purposes. Systems provide a method by which to interact with components and modify them according to external inputs and inter-system interactions. On the other hand, components store information related to one or more entities through sparse sets. I think the bigger question is how should systems, hooks, and inter and intra-system interactions be handled? The way systems function and interact is paramount to the utilization of components later on and becomes a question of flexibility.

bitsyndicate referenced this issue

2025-05-01 23:12:23 +00:00

WIP: feat(ecs): add basic sparse set per component ECS #17

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: nonsensical-dev/zenyx-engine#7

No description provided.

Rows
Columns