[MUD-Dev] Population container

Wout Mertens Wout.Mertens at rug.ac.be
Thu Jul 3 17:31:26 CEST 1997


On Tue, 1 Jul 1997 clawrenc at cup.hp.com wrote:

>    at 07:57 PM, Wout Mertens <Wout.Mertens at rug.ac.be> said:
> 
> >Well, the only feasible solution to both problems seems to me: Allow
> >only a certain number of instances max. to run loose in the area
> >controlled by the population container.  It would involve a slight
> >redefinition: The population container is a virtual container, that
> >contains both the real and virtual ('real' meaning virtual to us, of
> >course. This is getting philosophical :)) instances of the
> >population, and the model is calculating the numbers. 
> 
> I prefer something like:
> 
>   If a mobile has travelled a minimum of X unique rooms, during which
> time he has had available a minumim of Y alternate routes (ie
> different exits from a given room), and if during that time he has not
> passed or encountered any objects which either queried any of his
> methods, or redirected his IO (ie outgoing descriptions, entrance/exit
> strings etc), then that object can be de-instantiated.

Very nice. As long as the object is not something special (like a major or
a queen or so, I think this is a good solution

> >Which leaves me to think that maybe it should be called Population
> >Model and not Container... Or how a clever idea turns into a standard
> >solution :)
> >Ah well, it's not as if I'm not used it on this list :)
> 
> You put up the targets and we'll do our best to shoot them down or
> paint them a different colour.  Heck you guys have sandblasted enough
> of my own already.

Yup, great list :)

Wout.




More information about the mud-dev-archive mailing list