Adding more details to hooks and events to match modLoader changes #26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As the title says, this enhances the modApiExt hooks and events to provide the same level of details as the modLoader hooks/events. This relies on the ModLoader PR: itb-community/ITB-ModLoader#230
Below is an example of an intentionally injected hook and event failure. Before this it was a one line error on the specific line. This should allow for easier debugging of hooks especially that are failing in lower level, generic code
To test, add code that will intentionally fail and trigger the hooks. In this case, I added podLanded hooks with a few layers of fns just to show the stack trace is working correctly
Then enter a mission and trigger a pod landing via console with the
podcommand