BCEG Conditional Operators that don't appear to be working anymore

I've noticed that some of the Conditional Operators previously available in BCEG don't appear to be working anymore, or something has changed that I'm not aware of when this was updated by Moon Wizard. If my assumptions are wrong about the expected functionality, please educate me. :)

First is the ability to use a [creature name] as an additional filter in the RANGE Conditional:

Code:

---

RANGE((N), ![faction]*, ![creature type]*, ![creature name]*, ![target])
True if the actor is within the specified range (N) of at least one other actor that is not incapacitated. Filters can be applied to match only specified.

---

This was used successfully for Warding Bond (2nd Level Cleric Spell): "You touch another creature that is willing and create a mystic connection between you and the target until the spell ends. While the target is within 60 feet of you, it gains a +1 bonus to AC and saving throws, and it has Resistance to all damage. Also, each time it takes damage, you take the same amount of damage."

Previously, this Effect worked:

Code:

---

Warding Bond; IF: RANGE(60, Bob the Cleric); AC: 1; SAVE: 1; RESIST: all; SHAREDMG: 1

---

(SHAREDMG is from Life Ledger or Life Drain.) However, the IF: RANGE(60, Bob the Cleric) doesn't work anymore. In general, IFT: RANGE(60) works, but lacks the ability to check the range to the cleric specifically.

Second, is the ADV/DIS Conditional (True/False if the attack roll has (dis)advantage).

I used the IF: !DIS Conditional in an Effect for Brutal Strike (5.5e Level 9 Barbarian Feature): "If you use Reckless Attack, you can forgo any Advantage on one Strength-based attack roll of your choice on your turn. The chosen attack roll mustn’t have Disadvantage. If the chosen attack roll hits, the target takes an extra 1d10 damage of the same type dealt by the weapon or Unarmed Strike, and you can cause one Brutal Strike effect of your choice."

Code:

---

Reckless Attack; GRANTADVATK; IF: !CUSTOM(Brutal Strike); ADVATK; [SELF]

---

and, combined with

Code:

---

Brutal Strike; IF: CUSTOM(Reckless Attack); IF: !DIS; DMG: 1d10; [SELF]

---

However, the IF: !DIS doesn't work anymore as far as I can tell.

Are these operators still supported per the original documentation?

RANGE is no longer handled by BCEG at all; just the standard CoreRPG version that handles RANGE({operator}#). I'll remove from the README.md in BCEG.

I'll look at IF: DIS and IF: ADV; since I believe those should still work.

Regards,
JPG

I'm looking at the original code; and I don't see where it would have been supporting the usage you showed.

In your Brutal Strike example, the ADV/DIS data is only available during the attack roll (both in old and new versions of BCEG); so the DMG: 1d10 would always trigger.

As I'm reviewing the code in general for ADV/DIS (both old and new), it is unclear how it ever worked as a conditional,
given that the data used to build the conditional ADV/DIS data in BCE doesn't even have the data from the core ruleset to work with at the point the data is built,
and never had a mechanism to update ADV/DIS based on the other attack roll modifications that got applied after the data built (such as ADVATK, Poisoned, etc.).

For now, I'm going to go ahead and remove those from the README documentation, since they do nothing, and it doesn't look like they worked as documented in the old code either. I've also removed the out of date PDF from the forum thread.

Regards,
JPG

Quote:

---

Originally Posted by Moon Wizard

I'm looking at the original code; and I don't see where it would have been supporting the usage you showed.

In your Brutal Strike example, the ADV/DIS data is only available during the attack roll (both in old and new versions of BCEG); so the DMG: 1d10 would always trigger.

As I'm reviewing the code in general for ADV/DIS (both old and new), it is unclear how it ever worked as a conditional,
given that the data used to build the conditional ADV/DIS data in BCE doesn't even have the data from the core ruleset to work with at the point the data is built,
and never had a mechanism to update ADV/DIS based on the other attack roll modifications that got applied after the data built (such as ADVATK, Poisoned, etc.).

For now, I'm going to go ahead and remove those from the README documentation, since they do nothing, and it doesn't look like they worked as documented in the old code either. I've also removed the out of date PDF from the forum thread.

Regards,
JPG

---

Thank you for the reply and the research. I can’t recall a situation where the ADV/DIS conditional was actually tested, so I guess it was always overlooked. I can live without that one…

For the CoreRPG version of RANGE, however, is there (or will there be) a way to again check for range to a specific target in order to automate the many features that require “a target within x ft of you”? Mr. DDT suggested possibly using AoE effects in a roundabout way to mimic these features, but RANGE(N, [creature name] would be much easier to deal with.