i agree with BNSF50, his content doesn't have any errors at all, the build number shouldn't matter as long as the content is error free. changing the build number in TRS12 is kind of stupid because the program should have been designed to work with all content that is error free. like i said before BNSF50's content was not faulty as i did not open it in the CMP editor, i saw no reason to change anything, all i did was right click the item and ran the check error and fault program which runs a validation program,once that was done everything checked out good. no mods made to anything and they still retain the original build number.
there were a couple of build 2.5 that still show up in TRS12 that have the build error but my route is being made in 2009 and i was testing it in 2012 only to find potential problems that may arise latter on.
as a matter of fact changing a build number can actually screw up otherwise error free content, it's actually better to have the original creator post an updated version which would solve the problem for low build numbers . i want to thank BNSF50 and a few others who pointed that out to me on another issue and i am glad they did because without their insight i would have made a lot of trouble for myself, so with their advice i was able to avoid a lot of headaches.
the only content out there that really should be fixed is those that creators fail to include all of the files in their content, like when you find references to dependencies that don't exist due to the fact that they are custom content dependencies not included but still referenced in the upload to the DLS or hosting website.