Hello.
Since 4.4 release, blueprint generated functions have been reworked as described below:
Whilst in majority of the cases, this change can be considered beneficial for security reasons, it also cuts off blueprint workers from fast way to implements features, such as cheat codes in their projects.
My suggestion is to add an additional parameter (disabled by default), which will control whether given function/event is generated with FUNC_Exec flag.
This way, developer can control, whether they want to expose given functions to the end user.
As for the usage of ke */ce, it’s good for developer and/or debugging but does not work well for implementing actual cheat codes for the end user. It significantly extends the length of the code and has no autofill hints.
Here’s a visual representation of what do i have in mind:
Cheers