Hello davido234.

I had (and still have) the same issue with standard types.xml provided by Mass and others.

I changed the sequence the types.xml-files are loaded via the cfgeconomycore.xml, which reduced the "error" messages dramatically, but still leaves some errors in "wrong type names".

So, what I did next: I decrypted the pbo of SNAFU for an example, and searched for the keyword of the type which shows an error. (Using the Extractpbo version 2.26)

And: All these items do not exist in the pbos!
Result: The types.xml are listing items, which do not exist in the pbos!

My solution: I removed the items from the types.xml files, which obviously do not exist in the different pbos. Result: No more errors!

My recommendatio for you: Check the class names in your workshop. The class names are the names of the items.
You can compare your config.cpp structure with one of mine at https://github.com/GarageMan/example_config.cpp/blob/main/starting_gear_dovecote.cpp.

.:. lutz