Closed xavieran closed 3 years ago
State flag is a bit more complicated than usual Following table of offsets was found:
dac0:b09 set to 0x01
daca:b0a set
dacf:Nothing set, presumably this is only used for reading a particular offset
dacf: Seems to shift right by 1...
dad4:b0b set (this doesn't actually exist)
dade:b0c set
dae8:b0d set
daf2:b0e set
db7e:b1c set
dc32:b2e set
dc3c:b2f set
dc46:b30 set
Looks like the address in the save can be found by dividing by 10 and adding -2775 (-ad7). This points to the single byte associated with the event.
Disassembly for doing complex event choices explained how they work. Just need to finish off with partial reads/partial writes (dacc/dacf)
Done. Refer RunDialog: 0x23c7 for evaluating complex events and RunDialog: 0x1607 for writing complex events
Most events are simply setting a flag, but some are more complicated.
e.g. Captain Belfort at Lamut Garrison:
This goes to
The "SetFlag {dac0, [01ff]}" seems to set a full value rather than just a boolean flag.