Jump to content

Rod of absorbtion/smiting usability


igi

Recommended Posts

BUG:

"Rods of Absorption and Smiting were incorrectly usable by Fighter/Druids and Monks"

 

CAUSE:

Incorrect usability flags.

 

FIX:

Correct usability flags.

COPY_EXISTING ~rods01.itm~ ~override/rods01.itm~
 WRITE_BYTE "0x001f" "24"
 WRITE_BYTE "0x0021" "96"

 WRITE_BYTE "0x0029" "120"
 WRITE_BYTE "0x002b" "255"
 WRITE_BYTE "0x002d" "128"
 WRITE_BYTE "0x002f" "63"
 BUT_ONLY_IF_IT_CHANGES

COPY_EXISTING ~rods04.itm~ ~override/rods04.itm~
 WRITE_BYTE "0x001f" "24"
 WRITE_BYTE "0x0021" "96"

 WRITE_BYTE "0x0029" "120"
 WRITE_BYTE "0x002b" "255"
 WRITE_BYTE "0x002d" "128"
 WRITE_BYTE "0x002f" "63"
 BUT_ONLY_IF_IT_CHANGES

Link to comment

Updated to be more patchy:

 

COPY_EXISTING ~rods01.itm~ ~override/rods01.itm~
 READ_BYTE "0x001e" "1e"
 WRITE_BYTE "0x001e" (%1e% BOR  0b01000000)
 READ_BYTE "0x001f" "1f"
 WRITE_BYTE "0x001f" (%1f% BOR  0b00011000)
 READ_BYTE "0x0020" "20"
 WRITE_BYTE "0x0020" (%20% BOR  0b01110010)
 READ_BYTE "0x0021" "21"
 WRITE_BYTE "0x0021" (%21% BOR  0b01100000)

 READ_BYTE "0x0029" "29"
 WRITE_BYTE "0x0029" (%29% BOR  0b01111000)
 READ_BYTE "0x002b" "2b"
 WRITE_BYTE "0x002b" (%2b% BOR  0b11111111)
 READ_BYTE "0x002d" "2d"
 WRITE_BYTE "0x002d" (%2d% BOR  0b10000000)
 READ_BYTE "0x002f" "2f"
 WRITE_BYTE "0x002f" (%2f% BOR  0b00111111)
 BUT_ONLY_IF_IT_CHANGES

COPY_EXISTING ~rods04.itm~ ~override/rods04.itm~
 READ_BYTE "0x001e" "1e"
 WRITE_BYTE "0x001e" (%1e% BOR  0b01000000)
 READ_BYTE "0x001f" "1f"
 WRITE_BYTE "0x001f" (%1f% BOR  0b00011000)
 READ_BYTE "0x0020" "20"
 WRITE_BYTE "0x0020" (%20% BOR  0b01110010)
 READ_BYTE "0x0021" "21"
 WRITE_BYTE "0x0021" (%21% BOR  0b01100000)

 READ_BYTE "0x0029" "29"
 WRITE_BYTE "0x0029" (%29% BOR  0b01111000)
 READ_BYTE "0x002b" "2b"
 WRITE_BYTE "0x002b" (%2b% BOR  0b11111111)
 READ_BYTE "0x002d" "2d"
 WRITE_BYTE "0x002d" (%2d% BOR  0b10000000)
 READ_BYTE "0x002f" "2f"
 WRITE_BYTE "0x002f" (%2f% BOR  0b00111111)
 BUT_ONLY_IF_IT_CHANGES

Link to comment

If the only bug is the f/d and monk usability, why are we setting all of the usability stuff anew? For now, I've included the relevant bits for the specific issue as otherwise all of the bits beng addressed here are already set.

 

Coded as such in alpha 1:

COPY_EXISTING ~rods01.itm~ ~override~
             ~rods04.itm~ ~override~
 READ_BYTE  0x1f "fd"
 WRITE_BYTE 0x1f ("%fd%" BOR 0b00010000)
 READ_BYTE  0x21 "mo"
 WRITE_BYTE 0x21 ("%mo%" BOR 0b00100000)
 BUT_ONLY_IF_IT_CHANGES

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...