Re: positions

From: Tony Robbins (tonyr@pacific101.com)
Date: 02/05/99


----- Original Message -----
From: Edward J Glamkowski <eglamkowski@angelfire.com>
To: <CIRCLE@post.queensu.ca>
Sent: Friday, February 05, 1999 6:09 PM
Subject: Re:  positions


>>I don't know what your mount system looks like, but I'm assuming that
>>within your char_data struct there is a pointer to the mounted mob.  The
>>easiest way to achieve your goal is to just put a check in your "mounted
>>only" skills sorta like this:
>>
>>  if (!GET_MOUNT(ch)) {
>>    send_to_char("You can only use this skill when mounted.\r\n", ch);
>>    return;
>>  }
>
>That only partly works - if I want to let players
>charge into combat with a lance in order to skewer
>their opponents, that works ok, but if they don't
>kill their opponent and they start fighting, the
>lancer is moved from POS_MOUNTED to POS_FIGHTING
>and they can no longer use any mounted only skills
>for the duration of the fight.
>Which is not what I want.

I believe what he's saying is that SOMEHOW you relate the person to what
they are mounted upon--"POS_MOUNTED" can't tell the MUD who they're mounted
on.  If there is a pointer on the char_data structure called "mount" (struct
char_data *mount), you can check to see if ch->mount is not NULL...  if it
isn't NULL, then they're mounted.  In any case, you have to have more there
than the fact they're mounted as a position, so you have to make use of that
extra information.

-B.


     +------------------------------------------------------------+
     | Ensure that you have read the CircleMUD Mailing List FAQ:  |
     |  http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html  |
     +------------------------------------------------------------+



This archive was generated by hypermail 2b30 : 12/15/00 PST