Unused monster bit flags?

Hajo · August 27, 2010, 17:03

I'm still working with the old Angband 2.9.3 codebase, and saw that some of the monster bit flags seem to be unused (in defines.h)

Code:

#define RF2_STUPID			0x00000001	/* Monster is stupid */
#define RF2_SMART			0x00000002	/* Monster is smart */
#define RF2_XXX1			0x00000004	/* (?) */
#define RF2_XXX2			0x00000008	/* (?) */

Are these really unused, or is it just unknown if those are used (e.g. potentially hardcoded somewhere)? I'd like to use some of them for a few new features that I want to test.

zaimoni · August 28, 2010, 05:47

While one should always verify (grep the source code for them), generally the _XXX flags aren't used meaningfully.

Hajo · August 28, 2010, 10:47

Ok, thanks.

Maybe I'll introduce a 7th bitfield for my own flags. I see that the other fields are thematically sorted, and the flags in question would fit to the first field, which is already used up fully though.

August 27, 2010, 17:03	#1
Hajo Adept Join Date: Aug 2010 Posts: 142	Unused monster bit flags? I'm still working with the old Angband 2.9.3 codebase, and saw that some of the monster bit flags seem to be unused (in defines.h) Code: #define RF2_STUPID 0x00000001 /* Monster is stupid / #define RF2_SMART 0x00000002 / Monster is smart / #define RF2_XXX1 0x00000004 / (?) / #define RF2_XXX2 0x00000008 / (?) */ Are these really unused, or is it just unknown if those are used (e.g. potentially hardcoded somewhere)? I'd like to use some of them for a few new features that I want to test. __________________ I have a project problem? I have no project problem. I start a project, I work on it, it fails. No problem

August 28, 2010, 05:47	#2
zaimoni Knight Join Date: Apr 2007 Posts: 590	While one should always verify (grep the source code for them), generally the _XXX flags aren't used meaningfully. __________________ Zaiband: end the "I shouldn't have survived that" experience. V3.0.6 fork on Hg. Zaiband 3.0.10 ETA Mar. 7 2011 (Yes, schedule slipped. Latest testing indicates not enough assert() calls to allow release.) Z.C++: pre-alpha C/C++ compiler system (usable preprocessor). Also on Hg. Z.C++ 0.0.10 ETA December 31 2011

August 28, 2010, 10:47	#3
Hajo Adept Join Date: Aug 2010 Posts: 142	Ok, thanks. Maybe I'll introduce a 7th bitfield for my own flags. I see that the other fields are thematically sorted, and the flags in question would fit to the first field, which is already used up fully though. __________________ I have a project problem? I have no project problem. I start a project, I work on it, it fails. No problem

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Temp Branding Weapon Flags	APWhite	Variants	15	February 23, 2010 12:21
changes on resistance flags in char screen	bebo	Vanilla	4	August 5, 2009 19:59
Too darn many flags. :-(	PaulBlay	Development	9	April 4, 2009 22:59
Monster friend/friends flags	CunningGabe	Vanilla	5	February 20, 2009 23:30
Something a bit different	Aknight	Variants	22	June 25, 2008 21:13

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)