I repeat it to you again. We are speaking different languages. It has nothing to do with object-oriented C++ code, but rather the way in which the modules are organized and the poor decoupling that the current C++ code has internally, making you have to depend on all the modules.
That is, the object-oriented C++ code is not the problem, for the umpteenth time, it is the way they currently have it assembled in C++, making the dependencies dependent which makes your UE5 project little by little weigh more. and more, in other words, that it tends to infinity. This is explained how it should be done in the publication that from what I see you did not read. Repeating what has been repeated would make me seem a little boring, don’t you think?
Solution:
1 - You use the best practices and updated modularity patterns.
2 - Automation systems for the deployment of applications within software containers providing an additional layer of abstraction and automation or even other software systems.
ㅤ
This post has nothing to do with OOP. That’s for starters. Someone has gotten completely confused on the subject.
ㅤ
Old School:
Summary
Note for older people who are never going to retrain with OOP: I recommend a book called java: The Complete Reference by Herbert Schildt or any other important book, be it C++, Javascript, GO… And Cut out the nonsense and stop listening those who did not study correctly.