Hi All
Recently we have made a lot of changes to how DLC packs, including builtin content, are packaged.
The first is that DLC packs will automatically detect if content is from the DLS or not. This includes asset updates (ie if an updated asset is non DLS, then it gets seen as a non DLS asset).
If a non DLS asset is submitted along with a DLC pack, then the DLC pack won't be processed till the creator of that non DLS asset authorises through the TCCP website.
If the creator of the asset authorises, then that is up to them. Generally it would be preferred that the updates be placed onto the DLS, but we cannot force a creator to do this.
For builtin content, we use essentially the same system to build the content packs now, so unless something extreme occurs we shouldn't see this issue. We do aim these days for any updates that may be required to be placed onto the DLS, in part because it actually simplifies building the DLS package (it can just pull the asset from the DLS).
In regards to updates to DLS assets that have previously ended up in DLC packs or the builtin content set, I have pointed out a few times that if the assets are reported to us through the helpdesk then we can organize to get these up to the DLS. Generally it happens within 2-3 days of the report, depending on how busy I am at the time
I'm not saying this is infallible, we are talking about both people, and man made computer programs here. Hence why, if it does occur, simply contacting us should get it resolved within a few days now.
In regards to updates in general, these are normally done where an asset is faulty or not working. We avoid this as much as possible, but sometimes we do find we need to repair an asset internally. Unfortunately when dealing with content that is to be builtin in Trainz, faulty dependencies need to be fixed as quickly as possible, and waiting for a creator may not always work well.
For localisation, the asset may be given a new revision number to ensure that the version with the localization is used; again these days if any changes like this are made then we do try to ensure that it is updated onto the DLS. However with TRS19 we have avoided localizing most builtin content, and only localized interfaces in Trainz itself, and as such this issue should become far far less common than previous versions.
EDIT: I missed one
If an update has been made to your asset by us, and it has broken something, please let me know. At worst, I can try to find out why it was done; at best we may be able to assist with resolving it. Especially since the update would have been made in relation to something here, so it would likely need us to look into it again anyway
Regards