I am following an interesting blog called 'Game Ai for Developers '. It's quite new and has frequently interesting updates. It's especially interesting for people thinking a bit about architectural aspects like the behavioral approach Virtools uses for schematic scripting via their BuildingBlocks. I already mentioned it a couple of times that the approach of creating reusable scripts that you attach on entities has it's benefits but in many cases it's better to go data driven. Virtools supports data-driven implementations even since 1.0.1 but unfortunately they didn't use that approach often enough. This also lead to many people choosing the wrong design where data-driven was the better choice.
Moreover with the multi-core problematic, all this might change when trying to do processing like a GPU.
I don't know how Virtools does approach this challenge in their Next-Gen MP product. We see that they have something called Task and Task groups – common terms in this context. So maybe you will schematically script tasks that act on data – or if we consider 'task-groups', on data-context/isle/zone. I don't know.
That's also where we can come back to the Game Ai For Developers blog. It's related to this topic! Very interesting! 