Other assets being deleted while redownloading (reverting) assets to run a multiplayer session

That is what Phil is saying. Unlike a normal asset, the config.txt file of a route is populated with dependencies from the layout. You can change that number, but after a DBR, it will be back saying the 127 is missing, because that is what it sees in the layout.
 
That is what Phil is saying. Unlike a normal asset, the config.txt file of a route is populated with dependencies from the layout. You can change that number, but after a DBR, it will be back saying the 127 is missing, because that is what it sees in the layout.
That seems to be the prevailing thought but I have done similar editing to the config of other people's routes and never had them revert unless I clone the route and save them under my kuid. Saving definitely rewrites the config of the route as described.
 
It can't revert if the 127 asset is not installed. You must make sure that if the 127 asset is installed, you delete it. The only way 127 can be reinstalled is if it is in a DLC route.
 
I done some testing, I already deleted the 127 version and changed it to 1 in the Hanwa line config file as it should had been. I also did both DBR and EDR, good news the config file did not revert with the 127 version because I deleted all backups from my user data folder

I decided to load up other multiplayer sessions, including one I created and having to redownload everything is frustrating as it is, but it had to be done as I wanted to load up the multiplayer sessions, then I discovered <kuid2:71619:37004:9> vineygard - 23 lines now, again leading to the Hanwa line, changed to what it should be <kuid2:71619:37004:1> vineygard - 23 lines in the Hanwa line config file

I am not blaming the author of the Hanwa line for this, I am thinking there could be a bug creating duplicated ghost versions of assets if packaged into a cdp file. Would that be possible??
 
Sometimes, a route builder may have an asset that they have modified for their own use. They then forget and put it on a route in a DLC package. Because the route is DLC, the incorrect asset version will also be in the package. This has happened in the past, where a DLS asset was up versioned for a DLC package.
 
Back
Top