what i mean
This way, those plugins that “TheGameFeature” currently depending on would be loaded before it’s own module, which i think is the correct behavior.
Currently, the GameFeature would always load it’s module first(in the “Mounting” state), then waiting loading plugins it’s depending on(in the “WaitingForDependencies” state).
This bring me a problem: I want to use an UClass from one plugin(which is also a GameFeature) in my module, but when constructing the CDO from the module, the class has not been loaded yet.
Then, I revisited this video,
I notice Krzysztof Pachulski did emphasize that GameFeature plugins should be self-contained and should not be referenced by any other part of the game.
i realize that I misunderstood it.
(I was thinking GameFeature is a more feature-rich plugin, and try to write every new game plugin as a GameFeature )
So, by design,
a GameFeature could depend on plugins but not any other GameFeatures ?
(like game-specific layer features depending on base layer features)
(If so, looks like it’s more of a little “game module” rather than a “plugin”)