Post by Admin on Jul 16, 2016 3:45:48 GMT
Brandon Catcho @bcatcho Aug 08 2015 11:02
FYI I will be plugging Entitas on twitter for #screenshotsaturday tomorrow with this blogpost and some gifs: c.atch.co/sneak-preview-of-a-nano-rts/
I will be doing a followup post on an interesting (however naive) realization: Entitas Systems are easily prone to Temporal Coupling in my experience so far. You quickly realize that the order in which these systems run are very important as they tend to overlap on the type of components which they operate on.
However, the beauty of Entitas is it just makes this ordering of systems and behavior more obvious. You have these temporal problems no matter what your architecture is. For example: When do you despawn an object? When it's health goes to zero or on the next frame after that? When do other components get a chance to stop referencing the despawned object? etc etc etc.
So far lot's of positive experiences...
FYI I will be plugging Entitas on twitter for #screenshotsaturday tomorrow with this blogpost and some gifs: c.atch.co/sneak-preview-of-a-nano-rts/
I will be doing a followup post on an interesting (however naive) realization: Entitas Systems are easily prone to Temporal Coupling in my experience so far. You quickly realize that the order in which these systems run are very important as they tend to overlap on the type of components which they operate on.
However, the beauty of Entitas is it just makes this ordering of systems and behavior more obvious. You have these temporal problems no matter what your architecture is. For example: When do you despawn an object? When it's health goes to zero or on the next frame after that? When do other components get a chance to stop referencing the despawned object? etc etc etc.
So far lot's of positive experiences...
