Well, I think the reason why it was not originally done like this was
because with your idea an aggressive mob would always attack the first
person who entered the room.  This is especially important when dealing with
groups.  The leader of the group would be first to enter and would ALWAYS be
the first (and only) to be attacked.
     This would make it easy for players to predict who would be the tank
and thus make things less interesting from the angle of game play.  The way
aggr_update() polls now, it randomly chooses who the attacked player will be
by polling and then going through the whole list of players in the room.
     We're talking about legacy code which was load tested back on a 386
with like 8 megs of ram.  I think that optimizing that section of the code
when we're dealing with P2-P4 generation processors is moot.

- Will

Strife Daemonkin

----- Original Message -----
From: "MarkD" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, January 10, 2002 8:02 PM
Subject: question about removing aggr_update


> Hey list,
>    I was just thinking about ways I can optimize my mud and I thought
about
> removing aggr_update. What i'm wondering is whether calling a function
> every time a player moves into a room with a mob in it would be better.
The
> function would check if the mob has the ACT_AGGRESSIVE flag set and
whether
> or not it should attack, etc. I'm not sure if what i'm saying would work,
> but any feedback would be appreciated.
>
> Thanks a lot,
>
> Faramir
>
> _____________________________________________
> Free email with personality! Over 200 domains!
> http://www.MyOwnEmail.com
>
>
> --
> ROM mailing list
> [email protected]
> http://www.rom.org/cgi-bin/mailman/listinfo/rom
>


Reply via email to