News for hackers. Stuff that matters.
Re:Behavior trees for AI: How they work by skybrian on Saturday April 25, 2015 @07:26PM (#9439891)
Nice article. This looks a bit like a way to implement a scripting language that uses lightweight threads in a system that doesn't have it built in.

If you're using a language that has either lightweight threads or async/await built in, would you still use a behavior tree, or would you just write code?

Re:Behavior trees for AI: How they work by seivan on Sunday April 26, 2015 @06:08PM (#9443481)
You still need to be able to plug in stuff like decorators to say, invert values, have a throttle or a counter and etc.

Essentially you're going to need a wrapper to create a tree from either a DSL or e.g JSON from a GUI.

Re:Behavior trees for AI: How they work by Jare on Saturday April 25, 2015 @08:06PM (#9439995)
A behaviour tree can be data-driven easily, which opens opportunities for easy editing via DSLs, graphical tools and even changing the AI on the fly at runtime. If you can afford it, do BTs.