Didn't we hear that same sad excuse about T4? Which he WAS going to take personal control over?
And now T5... 10-11 years in development (depending on just who you believe...) BUT, rushed to print prematurely. Why? $$$...over a quarter of a million USD in the kickstarter pot?
And, before all you apologists try to ream me out, Marc claimed he could do everything for around $25,000 LESS THAN ONE TENTH of what he finally took in. So, economics surely isn't the reason T5 turned out so poorly done.
Could it be that:
And he dropped the ball. Again?
And please, before a knee jerk, ad hominem, attack, let's hear YOUR logic for why T5 came out so poorly.
It's pretty easy.....
1. Marc has a vision for where he wants Traveller to go. We are all welcome to come along for the ride, but he isn't really interested in anyone else's input. That isn't unique to him. From what I have seen, it is endemic to game designers from his era. The proof of this is all of the "yeah, we told Marc about this, but...." posts. This product was designed for gear heads and for those folks that view Traveller as a lifestyle, as opposed to a game. (Why else would you have 35+ years of civilian ship plans that only have twin beds?)
2. The Sewing Circle - Having "true believers" working play testing and "proof reading" is problematic because they understand how systems are "supposed to work".
The proper way to test is to hand a section over to someone who doesn't know the particulars about the product. They will follow the instructions precisely as written, which is when you will find which unstated assumptions need to be written and what doesn't actually work. Once you figure out something isn't working, you run into problem 1.
As far as the "proof reading" of the content, because they know the material, they see what they think is there as opposed to what is actually on the page. The brain takes shortcuts - there has been a lot of documentation on this over the past 20 years or so.
3. This doesn't actually address the fact that proofing a document is really hard. You have to read it line by line, and the amateurs working T5 simply didn't do that. I was having the same issue with re-typesetting MT with the current errata. My solution was to remove them from the process - they simply could not provide actionable feedback.
At the end of the day, T5 is a half-baked product. As a whole, it is a horribly over designed, much like Starfleet Battles. And in all seriousness, who has time to learn it?
Every group will find 100 pages that they simply can't live without, but it will be a different 100 pages for every group.