Function and Macro Libraries 

My dude, greetings from Canada. You are the best teacher I could have ever found. Not only do you describe things plainly and in terms anyone can understand, but you also explain that there are other valid methods too, and encourage ourselves to practise around. You don't just say "Ok do this. Don't ask why. Now add this. Don't worry about what that does" like some of the channels here I won't name. They show you how to create something that is good for exactly one situation with no scalability. Not the case here. I'm so happy I found your channel, it has been beyond helpful and even goes into subjects I would never have thought of or had no idea even existed. Hard VS Soft refences? What the hell is that and why haven't I heard about it? Well now I know, and I'm absolutely going to remember it. The most friendly and pleasant experience I've and I cannot state this enough. Never ever stop!! I never ever do the comment thing but I really just needed to tell you how much of a huge figure you've become for me.

Another cool feature of Macros is you can use Nodes which you can't use inside functions, these includes things like Timelines, Delay nodes and other latent nodes(If I am not mistaken), which is why I only ever used Macros in unreal engine other than that Blueprint Function library is far more superior in every sense. As for C++ I read somewhere that although Unreal uses a lot of macros for reflection system but it is recommended to use inline functions instead of macros for gameplay related purposes.

great video please keep em coming! I don't really understand the point of macro libraries though. For function libraries it makes sense a bunch of generic functions that you might need all over your project ezpz. But for macro libraries if it needs to inherit from a particular class anyway whats the point of not just throwing the macros directly in the parent class?