Reply to thread

Message: <blockquote data-quote="buzz" data-source="post: 3685024" data-attributes="member: 6777">There are a couple of things I don't understand.First, how does Mongoose manage to nab all of these licensed properties?Second, I'm not sure I see what the "fragmenting" problem is, much less that it needs solving. I mean, sure, there are whole bunch of rulesets available for Traveller right now, both new and old. So? It seems to me that the real selling point of Traveller is not the mechanics; it's the setting IP. So, how is creating yet another iteration of the CT ruleset, and letting a perfectly good d20 implementation lapse, all while continuing the existence of GURPS Traveller (thank goodness) going to make any difference?I'm not a publisher, but if I were, getting OGL access to CT's mechanics (or a version thereof) would not be a big sell for me. What I'd want is access to the setting IP. Will the TLL license provide this? If not, what's the incentive to produce CT-based RPGs that are not Traveller?I dunno. In an ideal situation, what I'd like to see done is the production of some canonical Traveller "setting bible" and line of supplements. Then, the creation of a license that would allow companies a rigorous interface in which to mechanically support that setting material. If anything, I'd want to encourage publishers to 'port the Traveller setting to as many rulesets as consumer demand warrants.</blockquote>