Re: Behaviour Tree PropClass
Christian Van Brussel <[email protected]>
| Newsgroups | gmane.comp.graphics.crystalspace.devel |
|---|---|
| Organization | UCL - TELE |
| Message-ID | <1340811235.2137.591.camel@scylla> |
On Wed, 2012-06-27 at 16:14 +0100, Sam Devlin wrote: > Following on though with the wrapper comment, should I keep > celBehaviourTree as a special BT node (allowing trees to be created > the old way) and write celPcBehaviourTree as just a propclass wrapper > > or > > should I carry on as I intended, with making celPcBehaviourTree and in > doing so limit it's use (I think) to only when tied to an entity? That's true that limiting the use of a BT to an entity might be a good idea, it's also in the spirit of CEL to put everything as a propclass instead of as external tools. Therefore, probably continue as you intended, just ignore my comment about that. You might still try to remove the description of "cel.pcfactory.behaviourtree" from your "behaviourtree.csplugin" though, that may be linked to the problem you face. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/