Printable View
The update went through, it shows 1.13 in chatlog. But I tested and still had 2 unconfirmed crit hits that did not trigger the d100 mirror image roll. I then turned off Keen to see if that made a difference, but still was not able to trigger the d100 mirror image roll on unconfirmed critical hits. It triggers successfully for normal hits and near misses.
Attachment 52825
Attachment 52826
Attachment 52827
Could you turn of my extension and test again (extended automation and overlays)? :) May be an incompatibility with my extension, I am not always up-to-date about the mirror image handler because I may miss an update :)Quote:
Originally Posted by Schneiderpants
(if that does not remove the problem, then start a new campaign and just test the mirror image handler to see whether or not it is an incompatibility with some other extension)
I just tested this with only Mirror Image Handler and Remove Effect Tag extensions loaded, and it appears to be working for unconfirmed crits:
Attachment 52832
Turning off Extended Automation and Overlays resolved the issue. It is now completing mirror image d100 check on unconfirmed crits.Quote:
Originally Posted by Kelrugem
Attachment 52833
I see :) Then it is an incompatibility with my extension :) Darrenan probably changed parts of his code which I also need to implement in my code for compatibility. I try to fix this soon, but currently I am heading to bed :)Quote:
Originally Posted by Schneiderpants
Sweet dreams! I (and I'm sure the community) really appreciate both of you being so responsive!
hehe, thanks :)Quote:
Originally Posted by Schneiderpants
I hope I can look at that today :) in some hoursQuote:
Originally Posted by Schneiderpants
Schneiderpants, I now updated all my versions of extended automation and overlays; can you test again? :)
@darrenan: Some parts of your code may be a bit "outdated" in sense of some smaller changes of the attack code, needed for compatibility with other extensions (like adding script names in front of local function calls), and the modifierstack script got deprecated and may be erased completely somewhen such that one needs to switch to ModifierManager :) (the current attack script already does that, so you would just need to copy that :) )
I must have forgotten to do a diff at some point. Usually, I make sure my script is identical to the original except for the specific changes I make.
No worries, I thought so that this may have happened :)Quote:
Originally Posted by darrenan
v1.14 released to Forge and attached to post #3 for FGC users. This is a FG 4.2.0 compatibility release, no new features or functionality.
is line 500 of manager_action_attack supposed to be rRoll? it still says rAction.
Did I miss one? I'll fix it, thanks.
EDIT: 1.15 pushed to the forge and attached to post #3. Thanks bmos.
Sory if I missed this, but when I attempt to add another stack (of mirror image) to a PC, I get an 'Already Exists' message instead of an increasing count of images.
EDIT: disregard. Operator error. It helps to activate the extension before you load the campaign...
Sorry it took me so long to reply, but this is now working correctly. Thanks to both of you!Quote:
Originally Posted by Kelrugem
Cool, you're welcome :) And no worries, no need to apology of course :DQuote:
Originally Posted by Schneiderpants
Hi Darren
Thanks for this extension, we have installed it for our weekly game but are struggling to work out how exactly to use it.
- How do you set the number of mirror image? Is that the purpose of the manual Xn Mirror Images effect?
- On a successful hit, does the player/GM manually then alter the Xn Mirror Images effect to count track hits?
So, in essence the extension handles the hit/miss calculations but not the number of images currently in view?
Thanks
Christopher
You have to add the appropriate number of images to the combat tracker, but then those images are automatically removed one by one as appropriate and the d100 miss chance roll adjusts accordingly. Manually roll a dice to determine the amount of images. Then go to the Actions section of character sheet, and to right of the Mirror Image spell (character sheet must be set to "Standard" or "Combat" mode), click the appropriate Effect button. You can hover over each button to see how many images it is set to apply, and there is also an "EFFECT: [SELF]; STACK; mirror image" button. You can click this one time per image, and it will stack that number of images on the combat tracker.
I'm pretty sure I had to edit all the effects to apply "mirror image," not "Mirror image." The capitalization made a difference for it to work correctly.
Note, per screenshot below, you may not see all the same Effect buttons for mirror image. I have some other Extensions that may alter this.
Attachment 53852
Fantastic, Schneider- thanks for the description and screenshot
The casing issue was fixed in version 1.8, so quite a while ago.
Currently, the pattern that is matched is: one or more numeric digits, followed by a single space, followed by 'mirror' in any combination of casing, then another single space, and then 'image' in any combination of casing.
If you are fluent in regular expressions, this is the pattern being matched: "(%d+) [mM][iI][rR][rR][oO][rR] [iI][mM][aA][gG][eE]". I thought about changing the spaces to "%s+" to make it more flexible, but have not implemented that change as of yet.
ive tried posting before. im on classic and your extension comes up with an X on the selection page on load.....
so i cant get it....to run on classic....
help please
Did you follow the advice in the first post that you need to have the Player Effect Removal extension loaded?Quote:
Originally Posted by wakhere
Also, @darrenan you might want to update the Effect Removal Extension link in your post as it points to Nickademus' thread rather than your continuation thread.
I will do that, thanks for noticing that.
I'm seeing it show up as an X as well. I thought it was because extension.xml had 4.1.12 for the <root> version, but I changed it back to 3.0 and it still shows as an X. Can someone enumerate all the different reasons that an extension might be X'd out in FGC?
Maybe because of the dependency tags?Quote:
Originally Posted by darrenan
maxversion should probably be 2.3 or 2.99 or something?Code:<dependency>
<name>PF Remove Effect Tag</name>
<minversion>2.0</minversion>
<maxversion>2.0</maxversion>
</dependency>
Yep, that was it, thanks!
Ok, the extension directly attached to post #3 should now be compatible with FGC again. Let me know if you see any problems.
I haven't tested it, but it looks like it still says maxversion 2.0?Quote:
Originally Posted by darrenan
I am having issue with the mirror image stacks. The % dice rolls properly only if a number is applied, but no stacks are removed. Also, Only 1 stack applies when cast.
Attachment 55235
Attachment 55236
Attachment 55238Attachment 55237
When I add a # to the stack it performs as below:
Attachment 55240Attachment 55241Attachment 55242Attachment 55243
When I add a # to the stack it performs as below:
Attachment 55240Attachment 55241Attachment 55242Attachment 55243
Quote:
Originally Posted by Taij
You haven't loaded the PF Player Effect Removal extension (or if you have, it's not working). See post number 1.Quote:
Originally Posted by Taij
Quote:
Originally Posted by darrenan
yes ive had the removal effect extension loaded for ages....Quote:
Originally Posted by bmos
in the past i had your extension running in classic and it was great.....
but i went to unity........and now for various reasons im back down on classic.....
and it as i said IT comes up with an X on the selection panel in load
The Effect Removal Extension is loaded, both my myself and the DM.
Well it is not working, so either it's incompatible with something else your GM is running or it's the wrong version. Only the GM extensions get loaded, so don't bother installing on your own computer if you just join their games.Quote:
Originally Posted by Taij
@darrenan
The remove effect extension link from your forge page still points to the old thread :)
@darrenan
This extension is lagging behind the 3.5E ruleset which as resulted in incompatibility with AmmunitionManager, HitMargins, and any others that have been updated and touch this function.
The change is that last summer the parameters/arguements of onPostAttackResolve were replaced with rSource, rTarget, rRoll, rMessage.
Version 1.16 has been released to the Forge. This fixes the compatibility issues called out by bmos, thanks dude.
The links on the store page have also been fixed. Back into hibernation...