Yeah thats a good point because I have made some intermediate systems (actually the hitscan is a perfect example) which I was toying with either keeping in my base project, moving to a plugin, or moving with my content into a game feature plugin since none of my base code depends on hitscan, only a select handful of content.
In terms of dependencies: I have weapons as primary data assets and I’m pretty sure that even if they are introduced in a game feature plugin they will still be picked up by the asset manager. However, there is still a major issue I thought of: For certain game modes such as
gun game, the gamemode needs to depend on pretty much all of the guns and even possibly other forms of content in the game. This means the gun game mode would need to be in another game feature plugin which depends on all the rest, but I’m hesitant to go down that path since it seems like bad practice / will lead to some tight spots, to have a plugin that depends on game + every game feature plugin.
EDIT: I should note that i have no intention to use game feature plugins for the sake of turning them on or off or any of the actual utility they provide. I just want to use them for project management.