Some of the jobs in jobs.xml aren't used. They tend to be called specifically.. whereas decision_tree_jobs.xml is a kind of mini-list that is typically called in groupings. A lot of the instances that I've seen that call the decision_tree are stuff like "run the entire civilian tree". It is indeed a bit confusing though. Especially if you start looking through the other job xml files haha. There's a LOT of stuff crammed in little corners, and which ones are actually used is a tough to figure out. To make it even weirder you have the workshop edb files that have 'standing order' options that don't correspond to any job and cause errors in the console.txt... but changing that doesn't fix it. The public house is the prime example. The mine throws errors all the time too, but that job *does* actually exist. The REALLY baffling part is that both the public house and mine seem to function just fine, so what job they're actually using is beyond me... I'm starting to think their unique functionality is hardcoded.