`ACT1Q1_Callback08_MonsterKilled` set flags incorrectly.
#226 opened on Jul 8, 2026
Repository metrics
- Stars
- (159 stars)
- PR merge metrics
- (PR metrics pending)
Description
these two lines bitwise OR the flag value (0x20), but the actual code from 1.13c assigns the value:
04125907 . C647 14 20 MOV BYTE PTR [EDI+14],20
0412594D . C647 14 20 MOV BYTE PTR [EDI+14],20
D2Game is based at 040C0000
pQuestData->dwFlags is only ever used to update the quest log, so this only affects the two quests that have progress updates via the log (DoE & Rescue on Mt Arreat), however this update is only ever going to start from zero or 0x20, so it is unnoticeable when playing.
this also happens to be one of only two places where the flags are ever set to anything other than zero, the other function, ACT5Q2_UpdateQuestState has the same bug: https://github.com/ThePhrozenKeep/D2MOO/blob/19019806df7f3e877fa105b05395d1e3597e2316/source/D2Game/src/QUESTS/ACT5/A5Q2.cpp#L982
the assembly from 1.10:
6FCB3218 |. C643 14 20 MOV BYTE PTR [EBX+14],20