Yep, could have. You can always make multiple solutions. I did this one, it works, tested.. and well people now have a fix. :)
----- Original Message ----- From: "Jef Waite" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[email protected]> Sent: Saturday, January 26, 2002 4:45 PM Subject: Re: STOCK ROM BUG: Duplicating Affects on PETS. > > First, Its been 5 years, and I still find some stock ROM bugs. This > > one eluded every mud coder I spoke to.. anyways.. here it is. > > > > this is also on my buglisting.txt file on > > www.mageslair.net/snippets/snippets.html page > > > > > > You could also just not save the affect to the pfile if it's a perm > affect. I ended doing this in the fwrite_pet: > for ( paf = pet->affected; paf != NULL; paf = paf->next ) > { > if ( paf->type < 0 || paf->type >= MAX_SKILL ) > continue; > > /* Don't save affects that are permanently set on a mob, create_mobile > adds them */ if (permaset(pet, paf) ) > continue; > > fprintf( blah... > > } > > And permaset checks the pet->pIndexData->affected_by to see if > paf->bitvector is set. > This way you don't have to worry about adding in extra affects that will > just be immediately recycled when a pet loads. > Jef > > > > > > -- > ROM mailing list > [email protected] > http://www.rom.org/cgi-bin/mailman/listinfo/rom > >
