I'm experiencing difficulties adding new affect flags to my MUD. Eventually, of course, I wanted to go past "ee", but doubling the value for "ee" as seems to be the pattern for the other affect definitions yielded a number large enough to flag a warning. When I tried to use a number for "ff" that was just 'any old number', people with sanctuary seemed to be affected by it, or at least, those who shouldn't have been, were... so what should I do? It's obvious that doubling the value of "ee" to get "ff" is necessary, but I can't really do that... ------------------------------------------------------------------------ --------------------- FF is the last you can get to. You can NOT go past ff as you can't use more than 32 bits (unless you've installed an unlimited bv system)... If you're running into problems with the large flag warning, like you are, what I'd suggest is , try using the hex bit conversion table below (please note, you WILL have to use the entire table, not just a part of it)
#define A 0x1 #define B 0x2 #define C 0x4 #define D 0x8 #define E 0x10 #define F 0x20 #define G 0x40 #define H 0x80 #define I 0x100 #define J 0x200 #define K 0x400 #define L 0x800 #define M 0x1000 #define N 0x2000 #define O 0x4000 #define P 0x8000 #define Q 0x10000 #define R 0x20000 #define S 0x40000 #define T 0x80000 #define U 0x100000 #define V 0x200000 #define W 0x400000 #define X 0x800000 #define Y 0x1000000 #define Z 0x2000000 #define aa 0x4000000 #define bb 0x8000000 #define cc 0x10000000 #define dd 0x20000000 #define ee 0x40000000 #define ff 0x80000000 That'll solve your too large int problem.. I changed these a year or so ago and haven't had a problem since. However, you won't be able to go past ff in any respect.. Time to check out aff2 flags it looks like TJW
