Biggest complaint most content creators have is "moving goalposts". That cliche doesn't begin to describe what happens with Trainz. Trainz is more like trying to shoot basketballs at a hoop nailed to the back of a truck driven by a drunken gorilla weaving back and forth then making sudden left turns into driveways and crashing through fences.
I've been modding and creating addons for computer games for over 30 years, and I have a technical background - I can troubleshoot machines and circuits I've never seen before provided I have a known good example - one that is working correctly to compare the faulty one to.
Warning: Required tag 'full-throttle-speed' was missing and has been set to default.
Warning: Required tag 'throttle-notches' was missing and has been set to default.
That's just one of the many I've run across, got a new patch which changes the standard, zero documentation on what it means, where or how to add it in content manager, and no known good example to study to see how it's supposed to be done. Change in format for splines, no docs or announcement, just suddenly discovering that what always worked before no longer works and we're left to figure it out ourselves. Build number X.1 is no longer supported, you can only upload build number X.2 or higher now, but guess what? The bridge spline with more than 2 tracks will not work in X.2, have to wait for 6 months or a year for X.3 and hope that that build will recognize 3 track bridge splines.
What would be helpful to content creators;
1. Thorough testing of build X.2 to make sure everything works correctly before obsoleting X.1.
2. Advanced warning of obsolescence with documentation of the differences, including what the creator needs to do in order to get rid of all the error and warning flags for the new build.
3. Examples to go by - Have Zec or somebody clone a build X.1 loco/spline/whatever is affected and update to error free X.2, upload to the DLS so we can download and see what an error free X.2 build addon actually looks like. Absent some form of coherent documentation that would be the most helpful, worst trouble I had getting 2010 content to work in 12 was errors and warnings about something wrong or missing, with no explanation or example of what exactly the error checker WOULD consider to be okay. Ludicrous to have the error checker complaining about a missing or incorrect tag when there is NO EXISTING MODEL ANYPLACE ON EARTH that has the required tag! If you're going to change the programming of the error checker to add something, you MUST have tested to see that SOMETHING meets the new requirements? Then upload it, so we at least have SOMETHING to go by!
Most of us can live with changes provided they're moving in predictable directions and include at least some instructions on what we need to do, I haven't seen that in Trainz yet.