Lacking essential coding utilities in the Blueprint Editor.

[MothDoctor]

@Ledii

2. Being able to freely choose accessability for Custom Events.
   Custom Events is required in order to use latent functions like the Delay node, which is saving SOOO much time.
   But it’s rarely I want these events to be something other blueprints should fiddle with.

Use Timers instead of relying on Delay nodes. Delay nodes are a quick hack, so it’s no regret with using Timers instead of them
Then you can set the access level to functions, it works since 4.25.

@Ledii

6. Some variable types like UWorld especially, should be exposed to blueprints.
   Using strings to load in levels is not really a solid method, as they are prone to spelling errors and they dont update if you change the names.
   How ever, nothing stops you from creating a Load Level Instance (by Object Reference) node and converting its UWorld Soft Object to a variable.
   This is super useful and most likely not supposed to be intended. But I think it should be!.

Actually, it’s a matter of adding a simple method like “Load Stream Level (by Object Reference)”. Load Level Instance also has 2 versions, accepting string and accepting TSoftObjectPtr<UWorld>.
Using Soft Object Ptr is all good and definitely intended, but IIRC it was added thanks to a pull request.

It would be a trivial work to add proper StreamLevel methods, I could look into it. Now, can’t promise if they would pull that in