 | | | oset <item > affect xaffected | oset <item > affect xaffected 2004-02-15 - By Joshua Halls
Back
I was trying to add an affect to an item and it was beyond the normal 31
bitvectors and noticed that affect affected would only work with normal
bitvectors. I noticed xaffected was an option but it was not coded in
fully in do_oset. Is this something with 1.4 only since that is what I
started with or do you guys have the problem in 1.4a. Here is what I am
talking about
if (loc >= APPLY_AFFECT && loc < APPLY_WEAPONSPELL)
{
bitv = 0;
while (argument[0] != '\0')
{
argument = one_argument(argument, arg3);
if (loc == APPLY_AFFECT)
value = get_aflag(arg3);
else
value = get_risflag(arg3);
if (value < 0 || value > 31)
ch_printf(ch, "Unknown flag: %s\n\r", arg3);
else
SET_BIT(bitv, 1 << value);
}
if (!bitv)
return;
value = bitv;
}
//////////I added this part here
else if (loc == APPLY_EXT_AFFECT)
{
value = get_aflag(argument);
if (value < 0 || value > MAX_BITS)
{
ch_printf(ch, "Unknown flag: %s\n\r", argument);
return;
}
}
/////////Down to here
else
{
one_argument(argument, arg3);
if (loc == APPLY_WEARSPELL && !is_number(arg3))
{
value = bsearch_skill_exact(arg3, gsn_first_spell,
gsn_first_skill - 1);
if (value == -1)
{
/* printf("%s\n\r", arg3); */
send_to_char("Unknown spell name.\n\r", ch);
return;
}
}
else
value = atoi(arg3);
}
The area I have the comments on I added in to make this work. Anyway,
if this was not implemented in 1.4a might want to add it if you want to
use affects later, that is unless
I am missing something.
--Josh
Earn $52 per hosting referral at Lunarpages.
|
|
|