What is expected case?

1. Disable All - Disabling only non choosed gameplay modules? Then we must provide "Custom Gameplay" for full manual choosing modules
2. Disable All - Disable all except rendering module? then we needs implement some metanames/tags for modules. It must handle requirement like "rendering tag", which say what you need one of rendering module.

So there are probably two phases to this topic.

1. Fixing current buggy behavior: Disable all should deactivate all modules except the actively selected gameplay template and its mandatory dependencies. This would include disabling CoreRendering (but it is a dependency on most if not all gameplay templates at present). Not too hard, but not alone either, there are several config related bugs in this area.

2. Improving the overall setup: It used to be that BuilderSampleGameplay (now TutorialMinimalEngineDemo, no longer in the Omega lineup) would be a minimal gameplay template you could effectively use as a "custom template" without involving CoreSampleGameplay and its increasingly larger set of dependencies. And now we do need some special modules like CoreRendering to be handled differently, effectively serving as orphaned but mandatory dependencies unless an alternative is provided. And we need to better distinguish between server and client specific modules (I think there are use cases for both). And support changing (at least some) modules in an existing save.

Probably this issue can be resolved by fixing 1), although it would be nice to also figure out the related bugs, such as why it seems like a restart of the game may lose all selected modules from the previous run, meaning you don't have any modules and no world to generate, at least in some cases. There can also be some weirdness overall when you activate/deactivate modules on the Advanced Game Setup screen we should review / stabilize.

Part of the buggy behavior in this area has probably been fixed by #4213, not sure if anything remains, haven't retested.