Thank you so much for such a thorough answer, .
I mean, I couldn’t be happier with what you wrote. Allow me to contextualize.
Before Able, we created our own AbilitySystem. We don’t have an Ability Editor as Able offers, but in terms of Developer Experience, it is awesome. Our pain points were in the semantics: replication, overall performance, etc etc. So we checked GAS out. Unfortunately, GAS is quite imperative and doesn’t easily integrate with the thing we created - and, for what it’s worth, if we had to migrate everything from our system to GAS, I’m talking about months of work (which is the reason we decided to avoid it).
Then we found Able. And it seemed to us that, by design, it’s smaller than GAS and less opinionated. Since it was on sale last week, we decided to give it a go. And after some exploration this weekend, as I mentioned, I stumbled upon all the questions I wrote above.
Now, after reading your answer, I must say that this is the perfect world. Able is almost non-opinionated, giving us the flexibility to use it in pair with the system we created, without having the fatigue of migrating all the things to a brand new system.
I believe the only thing left now is for me to debug further how I can expose BP Function Libraries to Able consistently, b/c I personally adore stateless functions - it’s just a time saver when you gotta refactor something. Oh, and by the way, perhaps 4.27 might be our solution. Check this out. Fingers crossed!
Last but not least, thank you again. That was quick and on point!
Take care my friend,
Gui.