Violet Martin

Calling `e.sprite(3, 1)` should work. The `sprite` method is overloaded -- you can pass in either coordinates or a name. The example is just showing two different ways of calling...

> let actual = (cardcard, cardsuit); I think this is the root of your confusion here -- it looks like you're thinking of `actual` as a tuple, but unfortunately that's...

What _is_ the error event? Is it [stalled](https://developer.mozilla.org/en-US/docs/Web/Reference/Events/stalled)?

Hmm, we do actually listen to the error event for audio. We [always reach the line](https://github.com/craftyjs/Crafty/blob/develop/src/loader.js#L217) `obj.onerror = err`. (It's outside of the media type `if` blocks.)

Well, I'm still alive at least. :) But, as the commit history (and lateness of this response) makes clear, haven't had time in a while to contribute or tend to...

We effectively don't support collisions between layers with different response factors right now -- it doesn't seem like a common use case, and would interact badly with the broad-phase collision...

Hmm, after thinking about it -- is the point to know when another element overlaps the sun entity? If so, that's pretty similar to what we do [to detect mouse...

Hmm, why a separate component, and not an additional capability of "Tween"? It might be worth thinking about whether there's an easy way to abstract the notion of chainable actions...

This will depend on how you're performing collision detection/resolution -- it's hard to diagnose without seeing the code!

@mucaho Those seem like valid points. It's probably not worth mandating the up-to-date checks if that's causing problems with accepting PRs; we haven't had a lot of issues with conflicts...