The confusion that you are experiencing is the difference between affects
that modify some of the values of the player data and AFFection flags.
MAX_AFFECTS is the former. This define determines the maximum number of
affects (i.e. Strength +4, AC +2, Save_Spell +7, etc) that an item can have
on it and the reason that it says DO NOT CHANGE is so that you wont ruin
your player rent files.
Inherently, the way that CircleMUD handles these AFF flags is by bitvector
handling, which is dependant upon the size of the variable that you use.
Circle uses either int or long for this and the size that these can handle
depends on the machine you are on. Regardless, a nice maximum is to set it
at 1 << 31 or 2^31 or 2147483648. This will give you 32 flags (0 through
31). If you want to use more than 32 flags, you must use a different
system, which is available in the patch "128bit.patch". Find it on the
CircleMUD ftp site, patch it, use it, love it.
Take care,
Rick
-----Original Message-----
From: Igor <imestric@PUBLIC.SRCE.HR>
To: CIRCLE@post.queensu.ca <CIRCLE@post.queensu.ca>
Date: Wednesday, November 04, 1998 4:01 PM
Subject: [CODE] MAX_AFFECTS
>Still having problems with affection flags...
>Although for MAX_AFFECTS in structs.h says DO NOT CHANGE i've changed it
>from 32 to 100 but AFF_FLAGS after 30 don't work...
>Spells make those affects which don't work so i've changed the
>MAX_SPELL_AFFECTS to 100
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST