Combat Groups Extension (Fantasy Grounds Unity 5E Ruleset)

[PaulChatterton]

Is there anything equivalent to this for Classic D&D 2E? I have been trying to set up the AD&D 1E tables for weapon to hit modifiers vs. armor class, and nearly got there but I hit a performance issue when the defender has his weapon equipped that I think would be resolved by the ActionOnly tag. I have the Action Only box on the advanced effect page of the weapon sheet, but it doesn't work, nor even does it appear to be transferred to the combat tracker. I was hoping this extension my fix it but it doesn't seem to be approved for 2E.

[SilentRuin]

Is there anything equivalent to this for Classic D&D 2E? I have been trying to set up the AD&D 1E tables for weapon to hit modifiers vs. armor class, and nearly got there but I hit a performance issue when the defender has his weapon equipped that I think would be resolved by the ActionOnly tag. I have the Action Only box on the advanced effect page of the weapon sheet, but it doesn't work, nor even does it appear to be transferred to the combat tracker. I was hoping this extension my fix it but it doesn't seem to be approved for 2E.

I have no idea what you are asking here. Are you sure you are in the right forum thread? See page 1 or watch video there. This is only supported in 5E though it does allow bringing up in a limited set of UNSUPPORTED other rulesets of which 2E is not one of them.

[PaulChatterton]

Apologies, you are correct; I was posting in the wrong thread. I was intentionally posting in a 5E thread but somehow managed to jump to the wrong one.

[SilentRuin]

V1.76- Bug - removed redundant code where some function names were duplicated when V1.66 was updated. Moved trigger for update of token tooltips (for combat group and owner names) from when the CT window entry is updated and calls onFilter() to their own addHandler functions. This should make some token movement that can trigger CT window entry updates like AURA and Step counter from rubber banding so much. Does not prevent it - just reduces it.

[MrDDT]

Awesome work dude.

[Farratto]

V1.76- Bug - removed redundant code where some function names were duplicated when V1.66 was updated. Moved trigger for update of token tooltips (for combat group and owner names) from when the CT window entry is updated and calls onFilter() to their own addHandler functions. This should make some token movement that can trigger CT window entry updates like AURA and Step counter from rubber banding so much. Does not prevent it - just reduces it.

If only some idiot would completely rewrite their extension to stop that rubber-banding. Jeez, people these days.

[SilentRuin]

If only some idiot would completely rewrite their extension to stop that rubber-banding. Jeez, people these days.

Ha. You've done plenty, and been super responsive (only way I use someone else's extension in fact) - luck on the rewrite!

[Farratto]

Ha. You've done plenty, and been super responsive (only way I use someone else's extension in fact) - luck on the rewrite!

:-)

[SilentRuin]

V 1.77 - Bug - accidentally removed code that handled invisibility effects in V1.76. Fixed.

[SilentRuin]

Generic Actions Layer - V1.78 - Bug - invisibility effect is not respecting isactive effect parameters for token visibility, shifted some processing to Generic Actions Layer extension due to order of processing problem. Fixed.