arvidsson

Yeah, I haven't thought about serialization issues really. One work-around is to make sure the IDs are the same every time yourself, using `Component::GetID()` and always in the same order...

Even though I don't recommend adding/removing components much inside the game loop, and it's not really how the design of this library was intended, it should be easy to add...

Might make it into a .cpp/.h pair, instead of having implementation in the header.

Observer pattern or something. But how to control the order of consumption?

When I get some spare time I can try to create a project in VS2015 and fix any errors. Would it be useful to also have the vs project/solution in...

Maybe useful constants and general stuff like clamp and whatnot?

There is already a shared blackboard for each behaviour tree, which can be passed to every leaf. But yes, I was thinking of something similar for the blackboard when it...

When you create the leaf you pass the blackboard which exists within the behaviour tree. But you are correct that the current implementation of the tree builder does not support...

Yeah I will create more examples and create more proper documentation for the different nodes you can use in the behavior tree. Thanks for the kind words! :)

I have added a first simple example, and plan to add more in the future.