Adam Arold

Thanks, @MrBergin this is a great observation! I'm gonna ad this to the next release.

@BobG1983 can you elaborate on this issue? I'm planning to code the next release of Amethyst (for the refurbished Caves of Zircon tutorial) and I'm not sure I understand this...

I agree. I think I'll draw a diagram with all these things, and write some examples just to give ourselves some ammunition for thinking about this.

You were right, the `Facet` composition is a good solution to create a command dispatcher and we can just send specific `Command`s to an `Entity` when we want to try...

I'd do this similar to how `Behavior`s are composed now. The reason for this is that we can take advantage of operator overloading and we can also define boolean operations...

That's a good idea, yes. But first let's think about the kinds of compositions we might want to implement. `+` can be used to compose but what about `and` and...

So `StairAscender` takes `GoUp` and `StairDescender` takes `GoDown` so `StairTraverser` takes both `GoUp` and `GoDown` so it is an additive composition. Job well done, we can go home, right? 😄

`or`/`and` I think is not really meaningful here. We have it with `Behavior`s and it is useful because they return a `Boolean` value so we can determine whether it performed...

Bump. Is there some progress with this? I dont want to have to maintain more than one GitHub profile if I can help it but without this I have to....

I think for most of us the main point of this feature is to *have a separate email for merging pull requests*. This is literally true for everyone who has...