[Entitas:] New ReactiveSystem to process only one entity
See original GitHub issueThe current ReactiveSystem passes in a list of entities and you probably end up writing code like this
public override void Execute(List<Entity> entities) {
foreach(var e in entities) {
// Do sth
}
}
The idea of having another ReactiveSystem like the following came up again
public override void Execute(Entity entity) {
// Do sth
}
Any thoughts? Would you use that?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:8
- Comments:11 (4 by maintainers)
Top Results From Across the Web
[Entitas:] New ReactiveSystem to process only one entity
When I use ReactiveSystem, I don't care about what each entity in entities is. They are just matched to trigger. ReactiveSystem processing them....
Read more >Reactive System
Hello, I tried Entitas some time ago, and they had a ReactiveSystem, which means that it was notified when a entity was created...
Read more >Entitas for Flutter. Alternative way of building reactive…
There can be only one entity instance carrying a component of such type. It's kind of like a singleton marker in a dependency...
Read more >They call me Reactive System - feedback wanted.
They want to iterate the entities that are in the group have all T... s and no U... s, so it makes sense...
Read more >Entity System Architecture with Unity - Unite Europe 2015
But for some games, a more data driven approach ( Entity System ... Entitas on the Unity Asset Store: ... Entitas - What's...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@JuDelCo It would be an addition, not a replacement. The list approach is the most flexible and fits well with the Entitas idea of aggregation. The other approach on the other is a veeery common use-case I guess.
It would be a separat system. Another reason to add this new system is performance. Currently you iterate once to filter, than you iterate to execute. With a single entity system we could save 1x iteration which might be noticeable when having thousands of systems.