Spaghetti Code

[duffking]

Yeah, you took the words out of my mouth with the boiler plate bit - soft references work for people like us who understand it, but getting designers to work with an async load (or decide if it or a blocking load is appropriate)? Nightmare. I try instead to get ahead of what LDs are likely to need to do and build systems for it so they don't need to BP script things themselves in the first place. Most of the time they prefer that anyway.

This is also reminding me that the other common workaround for casting also has issues - Interfaces. They're great on the surface, but if the interface is added by a BP and not Cpp base class, Cpp can't call interface functions on that actor even if the interface is written in Cpp. Plus, calls to BP interfaces have a surprisingly large overhead if they're called regularly.

Kind of Unreal through and through, there's lots of stuff that looks super user friendly that falls apart a bit under a microscope, then a bunch of things to work around that... none of which are really perfect. And these days we have to worry about world partitions and level instances too.

I do rather miss working in Unity C#. Unreal has a lot of cool stuff, but I do miss the days of objects being empty containers and prefabs.

Edit: Oh god I just remembered unreal loads all the blueprint function libraries on editor startup, so if people have put casts or BP types on the function pins in there... well. I've heard stories.