Open
Conversation
Contributor
Author
|
Added functions to get the feat ID, target oid and script type. Results from the example script in readme.md:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
It's feedback time. I decided to go with a new plugin because this didn't fit any of the existing plugins and I have to add other combat engine related functions later on.
I still have to do thorough testing and the custom scripts only have access to the attacker oid (
OBJECT_SELF) at the moment. I will expose the attacked object and other relevant information (damage, feat ID...) soon.If there is any other info that could be useful to expose to the custom scripts or any other features that someone wants to be added, leave a comment here.