[BUG FIX] sprintbit (was <INVALID BITVECTOR>)

From: Amy & Ryan Biggs (nauvie@netcom.ca)
Date: 10/03/96

>On Thu, 3 Oct 1996, Amy & Ryan Biggs wrote:
>> I keep getting <INVALID BITVECTOR> popping up in affects, room flags and
>> such, and it only affects with the (1 << 31) flags.  The flags themselves
>> seem to work (My ROOM_NOJUNK does work and it is (1 <<32))  Is there any
>> way to get these things to show up?  I wanna SEE the bitvectors.  (and
>> don't suffest a MOB2_ set...that's out of the question....I am NOT editing
>> the mob files AGAIN)

There was actually a typo here, it should be (1 << 31) in BOTH cases.  The
(1 << 31) didn't show up properly.  But I fixed it.  In the sprintbit in
utils.c, I made it an unsigned int (and in the declaration in it utils.h
too)  That fixed the whole problem.  I recommend having that changed in the
next patch of circle as it allows for proper displaying of all bitvectors.

The Husband and Wife team from heck!
E-mail: nauvie@netcom.ca
Amy Biggs:  http://www.geocities.com/SiliconValley/3461
Ryan Biggs: http://www.geocities.com/SiliconValley/3460

| Ensure that you have read the CircleMUD Mailing List FAQ: |
|   http://cspo.queensu.ca/~fletcher/Circle/list_faq.html   |

This archive was generated by hypermail 2b30 : 12/18/00 PST