Chacal wrote:We should also consider the asset developer's point of view.
What would be the use of creating 3rd-party assets if no one used them is scenarios?
An interesting solution I've seen is that some scenario authors publish two versions of a scenario: one with DLC and one with "default" assets.
Once the scenario is working with DLC assets, it is a simple matter to swap them out with default ones, without affecting the scenario's logic.
I've seen some of those, too, and it is a great and considerate way of handling DLC. Many thanks to those who do so!
