The conditional button since the new update isn’t working as intended. When you drag it into the scene it does not work as expected.
Missing Items text does not appear.
Not Enough Items Event does not trigger.
On Activated Event triggers on first interaction, even if the condition of Key Item required is not met
I’ve also a previous project with conditional buttons in, and they seem to work. I can duplicate them no problem. However, tested in a completely empty project and not working at all.
@JallsoppPL Thank you for your report! We would like to look into this further, would you be able to submit a bug report using the form available here? Fortnite Creative
Do you have “Infinite Resources” enabled in your new project, but disabled in your old project? That could explain the difference. It’s enabled in new projects by default, and it appears to break the Conditional Device. If you have Infinite Resources the Conditional Button may think you have an infinite number of any Consumable that is classified as a Resource. Some Consumables like Keycards or Ammo are fine, because they’re not counted as Resources.
If this fix works for you like it did for me, this is the third post I’ve seen with a creator getting mixed up by the Infinite Resources setting, with multiple comments agreeing. So whether this is an intentional feature or not on Epic’s part, it’s clearly confusing for creators. IMO by “Infinite Resources” should only apply to Building Resources not all World Resources like Consumables, so that the Conditional Button will work for all Consumables by default. I’ll make a feature request later once I hear back from you and the second poster that Infinite Resources was the culprit.
@GraemeBB the disable “Infinite Resources” fix I mentioned above might work for you too? Let me know because I’ll add you to the list of people who had this problem when I write a feature request.
I actually responded on that other thread but yes, that solved the issue. We definitely need a feature request put in to allow that if possible. At least, it should be in the docs perhaps if it isn’t. Thank you for the response! I ended up sorting it out myself by fluke but now it’s confirmed what solved it.