Hi All
This has been covered a few times, but to clarify.
Last year we switched over to the TCCP 2.0 system for DLC pack submissions. This changes a lot how DLC packs are now packaged, including the handling of freeware/payware content. Note that older DLC packs may not be updated to this, unless they are specifically updated through TCCP2.0.
As it stands now, it is entirely up to the creator of the DLC pack to specify exactly which content is to be marked as payware. So in a route DLC pack, this will normally be the route itself, plus often the sessions, and maybe specific content that they consider to be 'payware' content (ie if the route includes locomotives that would otherwise be released as payware if released separately). This avoids content being accidentally marked as payware, as it is now within the control of the DLC pack creator.
This means that content in a DLC pack will have two statuses when installed (at the current time at least).
installed, payware - This is for the content specified by the creator as being payware.
builtin - This is for all other content included with the DLC pack (including all dependencies on the DLS, and any non DLS assets not marked as payware by the creator).
We also have better support for non DLS dependencies. Specifically, creators
can include these in their DLC pack. But they must get authorization from the original creator through the TCCP system (basically the original creator needs to sign into TCCP, and authorize either individual assets, or the whole lot). This should help avoid content being packaged in DLC packs without the original creator's permission
For DLS content that had updates packaged in a DLC pack prior to the TCCP2.0 system being introduced (and hence being marked 'payware', as that asset revision wasn't on the DLS), please submit a helpdesk ticket with the assetID numbers and we can look into this. This will normally involve either the same asset being placed onto the DLS, or an update to the asset being placed onto the DLS.
In regards to DLS content being included in DLC packs, this is done to ensure that anyone who purchases/installs a DLC pack has all dependencies needed for it to work installed in the one download. It is an extremely common complaint with content about having to download lots of dependencies, and so we have designed our DLC system to avoid this as much as possible (the main exception will be updated assets onto the DLS, which would be needed for any multiplayer sessions that are included).
Regards