Readme has wrong methodname for ecs.render() about ent-comp HOT 5 CLOSED

Thanks! Want to submit a PR?

from ent-comp.

If I actually add anything I will. I've got an idea for that actually, not
sure if I'll have time to implement it...

On Sat, Apr 30, 2016 at 6:11 AM, Andy Hall [email protected] wrote:

Thanks! Want to submit a PR?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#1 (comment)

from ent-comp.

Too late. Let me know what you're interested in adding, please, or what you think is missing!

from ent-comp.

I was thinking of expiring components.

ecs.createComponent({
name: 'isSwingingSword',
state: { },
onRemove: function(id, state) {
ecs.addComponent(id, 'canAttack');
},
expiry: 500
});
ecs.addComponent(id, 'isSwingingSword');
ecs.tick(100);
ecs.hasComponent(id, 'isSwingingSword'); // true
ecs.getState(id, 'isSwingingSowrd').expiry; // 400
ecs.tick(401);
ecs.hasComponent(id, 'isSwingingSword'); // false
ecs.hasComponent(id, 'canAttack'); //true

Would be useful for short-lived things like attack animation, where you
need to know the time-remaining but otherwise don't have anything to put in
system(). Not hard for the user to do themselves, but seems like it'd be
so common a use case that simplifying it would be a nice addition. Not
sure if it should key off of of system time or render time, or both
(meaning, have expiry and expiryRender). Whatcha think?

On Sat, Apr 30, 2016 at 9:36 PM, Andy Hall [email protected] wrote:

Too late. Let me know what you're interested in adding, please, or what
you think is missing!

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#1 (comment)

from ent-comp.

Well, I haven't thought deeply but my first reaction is that something like that might be better left in client code? Unless there's a reason why it's better done inside the library than out (e.g. it needed to mess with internal data structures).

from ent-comp.