@Triplis I haven't found all of that necessary -- one reason I haven't rewritten the versioning history info in the TDesc Browser to completely parse the version history of all tdesc versions. It's not that it would be that difficult to do though, if someone wanted to code that in to it - it could be rewritten to track the history for each version of the tdesc files and note what has changed since the previous tdesc version (currently it just looks at the version history and highlights nodes that have changed since some uncertain point in the past). Just that, for me at least, that effort hasn't seemed worth the rewards from doing so. Partially because:
One thing that can be quite helpful is to run the Sims Log Enabler with the option set in the script to log everything starting at game load. It will produce a Tuning.log file chock full of all the errors in tuning files that do not throw exceptions, but are logged. For example:
Incorrectly matched tuning types found in tuning for put_down_tuning in Instance: 18211831855231043257 (graycurse:pasta_object), Types.OBJECT. Expected 'L', got 'T'
ATTRS 3: dict_items()
That's not entirely automated, of course - you have to run the game and see what errors get tossed in there, but it is very helpful in tracking down what isn't tuned properly but isn't actually throwing an exception. (Or in the above example case, what mods you should probably get around to downloading the latest version of...)
