Unused monster bit flags?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Hajo
    Adept
    • Aug 2010
    • 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
  • zaimoni
    Knight
    • Apr 2007
    • 590

    #2
    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

    Comment

    • Hajo
      Adept
      • Aug 2010
      • 142

      #3
      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

      Comment

      Working...
      😀
      😂
      🥰
      😘
      🤢
      😎
      😞
      😡
      👍
      👎