UEFN – VFX Powerup Device Fails to Remove Effect with Specific Exclusivity Index

On my island, I’m using multiple VFX Powerup Devices that apply and remove different VFX on players via the Custom Effect Exclusivity Index.
One VFX Powerup Device intended to remove an effect with a specific Exclusivity Index does not work, while another VFX Powerup Device on the same map with a different Exclusivity Index functions perfectly.​

Steps to Reproduce

  1. In UEFN, place a VFX Powerup Device and assign a Custom Effect (Niagara System).

  2. Set the Custom Effect Exclusivity Index to value A (e.g., 0) and configure it to display the VFX on player pickup (Infinite Effect Duration = true).

  3. Place a second VFX Powerup Device on the same map to remove the effect with Exclusivity Index A (e.g., via “Disable Effect on Pickup” or identical Exclusivity Index).

  4. In-game, pick up the first (working) VFX Powerup (effect displays correctly), then pick up the second VFX Powerup intended to remove the effect.

  5. Observe: The effect from the first VFX Powerup remains active and is not removed, while other VFX Powerup Devices with different Exclusivity Indices on the same map work correctly.​


Expected Result

When a VFX Powerup Device with the same Custom Effect Exclusivity Index is triggered, the existing effect should reliably be removed or overridden, regardless of the Index used.​


Observed Result

For at least one Custom Effect Exclusivity Index(3), the effect is not removed, even though other VFX Powerup Devices with different Indices on the same island function as expected.
I’ve tested various Exclusivity Indices, deleted and re-placed the affected VFX Powerup Devices, and reset settings, but effect removal still fails.​


Additional Notes

  • All VFX Powerup Devices use Custom Effects (Niagara Systems) and are set to Apply To = Player and Infinite Effect Duration = true.

  • The issue affects only specific Exclusivity Index values; other values work flawlessly with identical configuration

You should report this as a bug by clicking the New Issue button here.