Please help me find the kuids

Dougiee

New member
<kuid:840120:102793>
<kuid:840120:100336>
<kuid:840120:100339>
<kuid:840120:102787>
<kuid:840120:102788>
<kuid:840120:100699>
<kuid:840120:102790>
 
Based on all available indexed sources:


  • Author 840120 = JScout, a creator known for TTTE/Sodor‑themed assets.
  • Publicly indexed JScout assets include bogeys, hornsounds, scenery, facepacks, texture groups, and traincars.
  • The highest JScout KUIDs publicly listed are in the 100xxx range, such as 100167, 100299, 100721, 100722, 100939.
  • No 102xxx‑series assets from JScout appear in any catalog, forum dependency list, or archival mirror.

This strongly suggests one of the following:


Possible explanations​


  1. Private / unreleased asset
    Many JScout items were never publicly released or were shared only in closed groups.
  2. Part of a pack that was removed
    Several TTTE/Sodor creators have taken down older packs due to redistribution issues.
  3. Typo or mis‑read KUID
    A common issue when scanning config.txt files or CMP error logs.
  4. Obsolete or replaced dependency
    Some creators reused internal KUID blocks for testing assets that never shipped.



What you can do next​


If you want, I can:


  • Check the route or rolling stock that references this KUID and infer what type of asset it should be (mesh, scenery, face, bogey, etc.).
  • Try to locate alternate versions or replacement KUIDs from the same creator.
  • Decode the config.txt dependency chain to see if the missing asset is actually redundant.
 
Based on all available indexed sources:


  • Author 840120 = JScout, a creator known for TTTE/Sodor‑themed assets.
  • Publicly indexed JScout assets include bogeys, hornsounds, scenery, facepacks, texture groups, and traincars.
  • The highest JScout KUIDs publicly listed are in the 100xxx range, such as 100167, 100299, 100721, 100722, 100939.
  • No 102xxx‑series assets from JScout appear in any catalog, forum dependency list, or archival mirror.

This strongly suggests one of the following:


Possible explanations​


  1. Private / unreleased asset
    Many JScout items were never publicly released or were shared only in closed groups.
  2. Part of a pack that was removed
    Several TTTE/Sodor creators have taken down older packs due to redistribution issues.
  3. Typo or mis‑read KUID
    A common issue when scanning config.txt files or CMP error logs.
  4. Obsolete or replaced dependency
    Some creators reused internal KUID blocks for testing assets that never shipped.



What you can do next​


If you want, I can:


  • Check the route or rolling stock that references this KUID and infer what type of asset it should be (mesh, scenery, face, bogey, etc.).
  • Try to locate alternate versions or replacement KUIDs from the same creator.
  • Decode the config.txt dependency chain to see if the missing asset is actually redundant.
Please! I need, I canThank you
 
Back
Top