As part of porting the Archipelago mod to ModEngine2, I made an attempt to move its hook detection to the ME2 extension API's register_hook function. However, the first AOB I ported over failed, and the failure crashed the entire DS3 process without any diagnostics or even any logs being written. This makes it very hard to even begin to figure out why it's not working and how to fix it. Since AOBs are likely to be somewhat fragile, especially as new patch versions get released, it would be very useful to have better diagnostic tooling for why they fail when they fail. Some things that would be helpful:
Ensuring that logs get written even if a failure occurs during extension activation.
Associating a name with each scan so that when one fails it's easy to tell "oh I need to update the hook for ItemGib" or whatever.
Specifically indicating the address that was detected, or whether no address was detected at all.
Maybe even popping up a dialog box with relevant information on failure.
As part of porting the Archipelago mod to ModEngine2, I made an attempt to move its hook detection to the ME2 extension API's
register_hookfunction. However, the first AOB I ported over failed, and the failure crashed the entire DS3 process without any diagnostics or even any logs being written. This makes it very hard to even begin to figure out why it's not working and how to fix it. Since AOBs are likely to be somewhat fragile, especially as new patch versions get released, it would be very useful to have better diagnostic tooling for why they fail when they fail. Some things that would be helpful:ItemGib" or whatever.