Just pushed a new build.
Opportunity attacks should hopefully be being flagged when a client machine triggers them, as well as the DM machine.
Try it out and lemme know :)
Cheers, Steve.
Printable View
Just pushed a new build.
Opportunity attacks should hopefully be being flagged when a client machine triggers them, as well as the DM machine.
Try it out and lemme know :)
Cheers, Steve.
Hi there. I'm looking for guidance on how to set this up to use with Riposte. I've read and re-read the instructions on the Forge page and am still a little lost. Here's what my Combat Superiority power group looks like:
Attachment 63735
Hi sdclarknc,
I've not looked at this extension for a very long time, so had to refamiliarise myself with hiow it works :P
Firstly, 'Riposte' needs to be added as a feature on the character, then the effect groups need setting up. I've attached a couple of screenshots which show how it's done.
Hope this helps.
Cheers, Steve.Attachment 63736Attachment 63737
Thank you so much. This is very helpful.
Cheers to you.
Hello Stv,
we hit an incompatibility of this extension with Automatic Mirror Image (tested with only those two loaded). I suspect there is a function overwrite which prevents the other extension to work. Error only occurs when a mage has Shield spell and applied Mirror Image to himself and it is checked if an image is hit instead of the mage. No output from 5e Reactions but image is correctly removed and the following error occurs:
Unfortunately, the other extension is in the vault so I cannot trace further - perhaps you can check with Kent McCullough what he is doing with rRoll.sResult which seems to be empty in the strings.match call.Code:[ERROR] Script execution error: [string: "5e Reactions:scripts/reactions.lua"]:78 bad argument #1 to 'match' (string expected, got nil).
This likely should be fixes on Kent's side as he needs to send a string and not another way, this would correctly better link into other features of other EXTs and is the better passing of the information.
They could put a nil check but it would end up not having all the information they need for a roll result. I believe we had the same issue for Rolling Mirror ext and added that in. The issue will also come up with other EXTs that need the string info like Requested Rolls (suppressed dice feature).
@MrDDT has it right I think. You may want to reach out to @kentmccullough. I'll try and add in a nil check in the next day or so to suppress the error meantime, but it's a bit of a cludge fix tbh.
Cheers, STeve.