Re: [Tads3] knowledge / 'seen' / npc knowledge base

["Mike Roberts" <mjr_@xxxxxxxxxxx>]

"steve breslin" <versim@hotmail.com> wrote:
> Let's have two vectors for each actor, one for 'knowledge' and one for 
> 'experience' or something like that.
I'd probably use a lookup table rather than a vector, since it's much faster 
to find a key in a lookup table than a value in a vector.

> If we have a basis for this in the main library, any modules which need to 
> deal with NPC knowledge don't have to write a new mechanism for doing this.
My inclination has been to leave things as they are in the base library, 
which already has the necessary *interfaces* to track known/seen status per 
object and per actor.  I suppose it might end up a wash in terms of memory 
overhead, though, if per-actor knowledge is optional at run time according 
to the existence of each actor's knowledge tables.  I think it would cost a 
bit of cpu, though, since there'd be a lot of testing for the existence of 
the PC's knowledge tables.

--Mike

_________________________________________________________________
Use custom emotions -- try MSN Messenger 6.0! 
http://www.msnmessenger-download.com/tracking/reach_emoticon