Correct key for the route did not found

Sandrilyon said:

The problem is not with assets with [bot] prefix. Forget about this. The topicstarter found wrong kuids that cause the issue with message "The route is payware..."

The real assets that destroy the map are used to protect the payware route of copying (not selling on Auran). So, if one of those assets is present on map, and the user doesn't have the key (also .cdp asset), you cannot play on the route and will get the message and session is ended.

Check out these assets below. Kuid with scenery type has a .gse file inside with "script" and "class" tag in config.txt. This .gse file refers to the authorization key. Inside of config.txt your will also find tag "privilege" with permit-listing=0, so you will never see this asses in editor, but after changing this tag to 1, you will able to place asset on your route. And this asset will brake your route.


This is the list of all kuids that have blocking script:

Code:

<kuid:568300:101274> ra2 12 22<kuid:833171:100450> SMV Murro
<kuid2:806431:145730:1> Znak 1850km
<kuid2:806431:145729:1> Znak 1850km2
<kuid:810247:10127> Kalitka1
<kuid2:806431:102799:1> wl_grass_yaloo
<kuid:810247:100136> Sound pole
<kuid:803640:25006> SM_12 old3
<kuid:882895:47445> RED_KTU
<kuid:424437:100012> PL_out_1m_y_s_a
<kuid:568300:100103> old_hall
<kuid2:806431:100905:1> gravel pbr wl
<kuid:348398:10025> Old shed 4
<kuid:708875:100147> ak dom 1et. 5.4
<kuid:803640:102387> LEP opora BP-110-1-2
<kuid:209691:10002> ktm_lib
<kuid:833171:100448> FMA Town house
<kuid:882895:25808> FMA Industrial modul08
<kuid:833171:100449> d_v_up_2 (no lods)
<kuid:568300:101376> d_dom_1et_61
<kuid:348398:6789> d_dom_1et_14
<kuid:209691:10001> Charbon
<kuid2:806431:600166:1> Bz_rock_wood
<kuid:708875:20319> ans9_1960
<kuid2:424437:113827:1> AC4 5300 NR-III-5 pz

So, 20 of these assets are renewed by uploading the new version of kuid without the script inside and tag listing-permit=0. Someone who dowloaded them need to renew to the newest version in order to get rid of the route blocking issue.

Click to expand...

BUGOR said:

I don't want to read all of the article, what's the problem with my bot-locos? They have never been replaced by another kind. These are simple locos which are traffic-only with a simple script to turn on lights, manage pants and different things which are useful for traffic locomotives. If we are talking about locomotives with prefix "BGR" put on DLS, of course. Everything else which are not on DLS are not legitimately and should be not in use. Unfortunately those assets were lost when re-install Trainz 2012 few years ago, but they have never been loaded on DLS.

Click to expand...

CitMusJoe said:

John, you are absolutely right in stating: " it is not a priori a bot ...", but I for myself tend to prefer the saver side, even with the related disadvantages. In my minds eye that's not panic, it is more a kind of carefulness. I really have had some bad experiences with similar issues, believe it or not.

My goal is to get clarity with this issue soon; for all of us.

So I eventually consider to comission my TRS19 installation for analysis by security experts.
As I fear it's too huge for N3V to solve it in time as they hold tons of assets on their DLS. I'm no SSO, so I can't help as volunteer with this.

As stated earlier: Hopefully N3V will post further statements for users how to deal with that.

Click to expand...

JCitron said:

I agree, Josef. Err on the safe side.

Sandrilyon has explained what's going on and Bugor's content appears safe.

As I said, it's not the content with "Bot" in the name, which is what has people in a panic.

Click to expand...

JCitron said:

And finally...

For those that want to check their content, here's list that you can use.

Here's the list in Kuid, format so users can search their content easily.

Code:

<kuid:568300:101274>,<kuid2:806431:145730:1>,<kuid2:806431:145729:1>,<kuid:810247:10127>,<kuid2:806431:102799:1>,<kuid:810247:100136>,<kuid:803640:25006>,<kuid:882895:47445>,<kuid:424437:100012>,<kuid:568300:100103>,<kuid2:806431:100905:1>,<kuid:348398:10025>,<kuid:708875:100147>,<kuid:803640:102387>,<kuid:209691:10002>,<kuid:833171:100448>,<kuid:882895:25808>,<kuid:833171:100449>,<kuid:568300:101376>,<kuid:348398:6789>,<kuid:209691:10001>,<kuid2:806431:600166:1>,<kuid:708875:20319>,<kuid2:424437:113827:1>

Copy and paste this list into the KUID search filter on installed assets. If you have any of these, update them or delete them.

Click to expand...

JCitron said:

And finally...

For those that want to check their content, here's list that you can use.

Here's the list in Kuid, format so users can search their content easily.

Code:

<kuid:568300:101274>,<kuid2:806431:145730:1>,<kuid2:806431:145729:1>,<kuid:810247:10127>,<kuid2:806431:102799:1>,<kuid:810247:100136>,<kuid:803640:25006>,<kuid:882895:47445>,<kuid:424437:100012>,<kuid:568300:100103>,<kuid2:806431:100905:1>,<kuid:348398:10025>,<kuid:708875:100147>,<kuid:803640:102387>,<kuid:209691:10002>,<kuid:833171:100448>,<kuid:882895:25808>,<kuid:833171:100449>,<kuid:568300:101376>,<kuid:348398:6789>,<kuid:209691:10001>,<kuid2:806431:600166:1>,<kuid:708875:20319>,<kuid2:424437:113827:1>

Copy and paste this list into the KUID search filter on installed assets. If you have any of these, update them or delete them.

Click to expand...

jordon412 said:

and I already checked and it doesn't have the object.gse file included in it.

Click to expand...

Sandrilyon said:

The problem is not with assets with [bot] prefix. Forget about this. The topicstarter found wrong kuids that cause the issue with message "The route is payware..."

The real assets that destroy the map are used to protect the payware route of copying (not selling on Auran). So, if one of those assets is present on map, and the user doesn't have the key (also .cdp asset), you cannot play on the route and will get the message and session is ended.

Check out these assets below. Kuid with scenery type has a .gse file inside with "script" and "class" tag in config.txt. This .gse file refers to the authorization key. Inside of config.txt your will also find tag "privilege" with permit-listing=0, so you will never see this asses in editor, but after changing this tag to 1, you will able to place asset on your route. And this asset will brake your route.

This is the list of all kuids that have blocking script:

Code:

<kuid:568300:101274> ra2 12 22<kuid:833171:100450> SMV Murro
<kuid2:806431:145730:1> Znak 1850km
<kuid2:806431:145729:1> Znak 1850km2
<kuid:810247:10127> Kalitka1
<kuid2:806431:102799:1> wl_grass_yaloo
<kuid:810247:100136> Sound pole
<kuid:803640:25006> SM_12 old3
<kuid:882895:47445> RED_KTU
<kuid:424437:100012> PL_out_1m_y_s_a
<kuid:568300:100103> old_hall
<kuid2:806431:100905:1> gravel pbr wl
<kuid:348398:10025> Old shed 4
<kuid:708875:100147> ak dom 1et. 5.4
<kuid:803640:102387> LEP opora BP-110-1-2
<kuid:209691:10002> ktm_lib
<kuid:833171:100448> FMA Town house
<kuid:882895:25808> FMA Industrial modul08
<kuid:833171:100449> d_v_up_2 (no lods)
<kuid:568300:101376> d_dom_1et_61
<kuid:348398:6789> d_dom_1et_14
<kuid:209691:10001> Charbon
<kuid2:806431:600166:1> Bz_rock_wood
<kuid:708875:20319> ans9_1960
<kuid2:424437:113827:1> AC4 5300 NR-III-5 pz

So, 20 of these assets are renewed by uploading the new version of kuid without the script inside and tag listing-permit=0. Someone who dowloaded them need to renew to the newest version in order to get rid of the route blocking issue.

Click to expand...