2 months ago #9
    Okay. When I get some time free I guess I can fire up fceux and check on that myself. Your suggestion does sound plausible, but I'm hesitant to change it without verification.

    Another possibility is that $566 is a set of multiple values -- that would explain the initial check, which checks bit 3 (for pre-emptive strike, perhaps) rather than bits 0 and 1. DW3 does continue DW2's annoying habit of storing multiple values within a single byte. Unrunnable checks do not seem to occur within 1who's pseudocode, but it's not hard to imagine that flag hanging out in bit 2, come to think of it...