Custom actions; New pathfinding features; Move along curved paths & more.
It's designed to be easier to use and better organised than functions. Instead of relying on a global list of functions that use "copy picked" (which is implicit and doesn't actually specify any particular object type), you can essentially list functions in the action list of the object type it is relevant for. That alone helps organise functions across the project and make it clear that functions affect specific object types rather than being global or general purpose things. And that's before additional features such as integrating with families.
Still, everyone uses Construct differently, so some people may choose to use them and others may not! That's fine, it's not mandatory to use it.
That's understandable.
If multiple event triggers for functions / actions cannot ever be supported. How about at least add some flexibility? For example: Call 'custom' action by name.
At least we have an option, it's not mandatory to use. If some people find it unorganized, they don't have to use it.
I think that's a fair balance for organization and functionality.