Debug tree history #311
Description
It can be rather annoying to debug issues with the behaviour tree, unless one knows exactly the place in the tree that causes the issue so one can set a breakpoint there. To discover why something does not behave how it should, it would be nice to have a 'time slider' to go 'back in time' e.g. 100 ticks so one can see what the state was in the tree.
This could be implemented by storing the last state of the debug tree in the linked list.