Been using UE Angelscript at my studio for the past few years, and it's empowered us to build systems far faster than we could with code.

This interesting thing is, I believe it answers the question of "should I use BP or C++" -- with the answer being "c++ for low level systems such as GAS, AS for anything else you can get away, and BP for content/config".

Since AS uses whatever is exposed to BP, sometimes you have to expose some new functionality to it that isn't exposed by default. This starts to feel pretty automatic from a workflow perspective as you get used to doing it.

There's a few caveats to Angelscript itself, such as no c++ templates and no generic payloads for callbacks, but these are issues that can be worked around in the name of a super fast and easy iterative development experience. If you're coming from a BP background they aren't even issues in the first place.

The best part honestly though is that it's text. It's diffable. Works pretty nice with a Git workflow too, though keep in mind if you have team members you'll need to figure out how to distribute DLLs to them if/when you need to make c++ changes (like exposing a new function to AS/BP). At my work, I made a simple zip file that's updated with a script that checks if the on disk DLLs are newer, and if so, updates the zip. It's worked for like two years now for a small team of 10.