George wrote:
>
> On Thu, 4 Feb 1999, Angus Mezick wrote:
>
> >Yup, that's what I get for posting after getting upset at work:)
> >Ever have your Spec radically altered and still be expected to
> >hit a HARD deliver date?
> >As to max_exist: I removed it and went completely percentage.
>
> I went a different route and added a qualifier to the max existing to make
> it per world, per zone, or per room. I didn't do percentages but it would
> have been easy to make the max exist qualifier say "percent" instead. At
> last check, I had my code working but its been so long I don't remember. I
> could probably replicate the code, but it's relatively trivial to
> implement anyway.
>
Did you add in a variable that is stored in the .zon files? or was it a just a
check in the code? (i.e. using the max exist number to say there can only be
one per world/zone/room?)
Trying to figure out the easiest way to add something like this, which will
not conflict with current zone files.
Since:
Format: 'M' <if-flag> <mobile nr> <max existing> <room nr>
the max existing is in the middle it would be difficult to change it to look
something like:
Format: 'M' <if-flag> <mobile nr> <max world> <max zone> <max room> <room nr>
doing this would require changing all the zon files. (pain in the ars)
hmmm
Any other idea's? maybe adding it to the mob files?
Adding,
MAX: <max world> <max zone> <max room>
Do the check during load?
And adding it to OLC?
+------------------------------------------------------------+
| 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