@Hellrunner - I’d love to help you mate, but I haven’t been involved in UE4 projects lately, and I never delved into components much. Tbh I’d go with the easy way: directly call the event on the component when its triggered in the base class.
@anonymous_user_6be47971 - You are absolutely right, its just one of those “golden rules” where its actually a guideline, of course, it depends on what you’re trying to achieve. But trying to reply directly, as what you say makes perfect sense:
1- Absolutely. Thing is, its not always about shiny features, its about bug fixes, incremented or added features which will save you a lot of work. Not less important, are designer features which may help boost the visual capabilities of your project, saving designers time and actually helping them out.
2- My experience showed me - unfortunately - that it is often not the case, sometimes even changing a few lines is enough to mess up the whole merging, but it might be my fault, I probably messed up along the way
3- Absolutely. But between possibly preventing engine updates and creating something a tad ugly… I’d go with ugly with some frostin on it
